Author Topic: Maya 2009 Job Submission Problems  (Read 2485 times)

sz

  • Jr. Member
  • **
  • Posts: 7
Maya 2009 Job Submission Problems
« on: December 18, 2008, 03:24:39 PM »
Hi

Setting up a new installation of Qube! Maya Submission from Gui works great with 2008 Ext 2. But with 2009 I get the following errors.....

ERROR: exception caught in maya::UniversalMayaRenderJob=HASH(0x8538e0)->run()
ERROR: lost pipe to maya-- has it crashed? at /Applications/pfx/jobtypes/maya/MelProcessor.pm line 579.

I can submit jobs from within maya 2009 using the plugin. But the jobs cant be resubmitted/modified from within the gui.

Any one else using maya 2009 and having issues.

Using OS X 10.5.6 and Latest Qube.

Thanks sz

shinya

  • Administrator
  • *****
  • Posts: 225
Re: Maya 2009 Job Submission Problems
« Reply #1 on: December 18, 2008, 11:34:44 PM »
Hi sz,

What version of the Maya jobtype are you using?

Just to clarify, your maya 2009 jobs submitted from the in-app plugin
submits and runs fine, yes?

We'll need to look at your joblogs more closely to troubleshoot this issue--
please send the joblogs from one of the jobs that failed (the simpler the
job, better), to our support <at> pipelinefx.com email.  Instructions are
included below.  Please be descriptive in your Subject line, and please
also mention this forum thread.

Thanks!

-shinya.

----
In order to address your problem more completely, please send us the job log directory for the job in question.

You can locate the directory by logging into your Supervisor, and looking for the job log folder in the following location (depending upon your Supervisor platform):

Windows
\Program Files\pfx\qube\logs\job

Linux, OS X
/var/spool/qube/job

In that folder, you will find a numbered directory that corresponds to the number of thousands in the job ID. (ID < 1000 = 0) Search in one of these folders for the one that corresponds to the correct job ID.

Zip up the entire job ID folder and reply to this email message with the zipped file.

If the zipped job ID folder turns out to be larger than 2MB, don't send it, but let us know and we will help you address the problem in an alternative fashion.