Author Topic: Hardware render  (Read 3668 times)

uppi

  • Full Member
  • ***
  • Posts: 10
Hardware render
« on: December 15, 2011, 02:58:08 PM »
Hi All,


Fist time I am trying to render MAYA hardware (AVI format) and in particular worker have QuickTime & MAYA working fine

This is for me urgent, and help me how to go with this.

Below mentioned error I am getting.



Starting "C:\Program Files\Autodesk\Maya2011\bin\mayabatch.exe"
// Maya exited with status 210
ERROR: exit status: 211
requesting work for: xxxx

=================  qube! - retry/requeue on Dec 14, 2011 11:00:38  ===================

requesting work for: xxxxx
got work: xxxxx - running

Starting "C:\Program Files\Autodesk\Maya2011\bin\mayabatch.exe"
// Maya exited with status 1
ERROR: exit status: 1



thanks in advance
uppi.

dmeyer

  • Sr. Member
  • ****
  • Posts: 40
Re: Hardware render
« Reply #1 on: December 20, 2011, 02:19:07 PM »
Does rendering to .iff work on this machine?

uppi

  • Full Member
  • ***
  • Posts: 10
Re: Hardware render
« Reply #2 on: December 20, 2011, 04:22:38 PM »
Hi,

Hardware render i tried .iff & AVI framet all so its not rendering .


uppi

BrianK

  • Hero Member
  • *****
  • Posts: 107
Re: Hardware render
« Reply #3 on: December 28, 2011, 05:54:38 PM »
Maya's error code 211 is related to problems getting to the project file(s).  This means there's either a permissions issue or a drive mapping issue (which is also a permissions issue at the end of the day).

Are you running Qube in proxy mode?  If so, who is the proxy user?  How are your permissions managed - are you using active directory or just open permissions on a file share?  Is the proxy user in your AD?  does the proxy user have the ability to mount the drives by letter?

possible solutions:
1. Ensure the proxy user can read the directory in question
2. If drive maps require a password (keep in mind, the proxy account will NOT get group policy info as it never actually logs in), set up a drive map for the proxy user in your central qbwrk.conf or in each worker's local qb.conf
3. Use UNC paths to get around the drive mapping issue.
3. Try by running in Desktop User mode rather than proxy mode & ensure that the logged in user has access to read/write to the appropriate directories. 
4. Use more permissive file sharing like NFS or Samba with open permissions.