> We've set up a new computer running Windows Vista, and we're getting
> this weird error during submit:
>
> rush: 'rush -submit': render@vistabox: LogDir '//jobs/projects/test/foo.ma.log': The parameter is incorrect.
> -- submit failed --
The "parameter incorrect" is actually a Windows error message
(which you can search for on Google).
Unfortunately its not very descriptive, but it basically means
Windows is unable to access your file server for some reason,
similar to the way an authentication problem would prevent your
accessing the drive.
I'm afraid I can't cite specifics, but offhand it sounds like
some kind of incompatibility between your new Vista machine
and the file server.. either authentication, or some other issue.
I recommend using 'runas /user:YOURDOMAIN\render cmd'
which will create a DOS window in the same user context
that Rush is running as, and see if you can replicate the
error with 'dir \\jobs\projects\'
> Hmm, yes, we tried your 'runas' command, and indeed we get the same
> error with "dir \\jobs\projects\".
>
> What's odd is that if we login to the console as that same domain user,
> the "dir \\jobs\projects" command runs fine.
I can't answer to the apparent inconsistency between the window
manager login and Microsoft's 'runas' command, except to say
"that's weird" and "it shouldn't be". :/
I'll bounce this off the group to see if anyone knows what
this might be.. I've never heard of the problem in this context.
Google shows many hits for the error, but the reasons are all
over the map.
One search that sounds compelling is an article that mentions turning
off 'zone alarm' ("personal firewall" software) which may be getting
tripped up by the multiuser context that both Rush and "runas" create.
Such software could cut off the network file access in strange low-level
ways that could explain the obscure "parameter is incorrect" message.
Regardless, as a workaround, I'd suggest trying this:
1) Create a local user called 'render' on both the Vista machine
(even though you're using windows domains) and the file server.
Make sure the user has compatible permissions with your other
domain users.
2) Make sure the new account's password is:
a) ..set to _never expire_ (important!)
a) ..the same on both machines
b) ..is not a blank password (else authentication won't work)
3) Verify you can login as this local user and access the
file server. (runas test should work too)
4) Configure the Rush service to run as this user
This bypasses any 'windows domain' authentication weirdness.
> We just tried that workaround you recommended, and yes.. that does
> seem to solve the problem.
>
> I'll follow up if I figure out what's causing that error for our domain
> account. We at least have a way to replicate the problem outside of Rush
> with the 'runas' command. (Will also check if a virus/firewall is enabled)
|