A few things catch my eye:
1) There's a subtle difference in the variable names:
MAYA_PLUGIN_PATH -- variable set in both DOS and RUSH
MAYA_PLUG_IN_PATH -- variable maya is complaining about
Note the difference between these names "PLUGIN" vs. "PLUG_IN";
Possibly maya honors both, but in my experience, MAYA_PLUG_IN_PATH
is the correct variable name.
2) The plugin path is pointing to a file server:
MAYA_PLUGIN_PATH=//skserver/oscar/Maya_Custom/2008-x64/plugins
Since the problem seems user oriented, I can't help but wonder
if permissions are causing the trouble.
If you login as the same user rushd is running as (local Administrator),
can you then open a DOS window and run the render?
Does this user have permission to access the plugins directory,
eg. does this command work?
dir \\skserver\oscar\Maya_Custom\2008-x64\plugins\
If that command fails when logged in as Administrator,
but works when logged in as 'soft', the problem is likely
the server 'skserver' has a different Administrator password
than host 'snap', which means the local Administrator won't
have access permission to that server unless the passwords match up.
3) I notice the rushd service is running as "Administrator"
whereas your DOS tests are being run as "soft".
If you login to the window manager as Administrator,
are you able to replicate the same error rushd does?
Also, if the render runs OK for soft, then try running the
rushd service as "soft"; does the render then run normally?
|