Backburner 2015 servers remains 'idle'

Backburner 2015 servers remains 'idle'

Anonymous
Not applicable
9,091 Views
30 Replies
Message 1 of 31

Backburner 2015 servers remains 'idle'

Anonymous
Not applicable

Dear reader,

 

I am facing a problem when processing renderjobs using BB 2015. This is the case:

 

I have enqueued several animation sequences. When I start the BB manager.exe and BB server.exe (both on the same computer), right after I submit the renderjobs, my server is active (green) and the first job in the queue starts rendering. However, when I reboot my system and start the BB manager and server again, the server remains idle. After a while the BB manager starts posting messages: 'ERR No task metadata found'. The BB server last message is about accepted registration of my system's ip address. The BB manager registered all the renderjobs, but the BB server does not receive a job. What is wrong?

 

A month ago it all worked well. I rendered several jobs with success. There where some changes to my system's software installation since then. I have installed:

  • Autodesk 3ds Max 2015 Extension 2 
  • Backburner 2015 Windows version for Max/3ds Max Design 2015
  • Autodesk 3ds Max 2015 Service Pack
  • Windows update including Microsoft .NET framework 4.5.2

And I uninstalled two older versions of 3ds Max (2012 and 2014).

 

My system runs Windows 7 Sp1 and I disabled all firewalls to allow free communication between the BB components.

 

Does anyone has an explanation / solution for this issue?

Accepted solutions (1)
9,092 Views
30 Replies
Replies (30)
Message 21 of 31

Anonymous
Not applicable

hi,

what have you changed from when it was working okay for you? a service pack for max? or backburner upgrade?

 

0 Likes
Message 22 of 31

jens.diemer
Collaborator
Collaborator

2016 SP3 install and a windows update install and a reboot...

 

I must test this more, but currently no time for reboots...

Jens

------------------------------------------------------------------------------------------------------------------
https://github.com/jedie/3dsmax_bugs | https://github.com/jedie/3dsmax_patches
0 Likes
Message 23 of 31

jens.diemer
Collaborator
Collaborator

Yes, it the bug is back!!!!

 

Is there any kind of automated tests? Does there exist any kind of manual tests?

Jens

------------------------------------------------------------------------------------------------------------------
https://github.com/jedie/3dsmax_bugs | https://github.com/jedie/3dsmax_patches
0 Likes
Message 24 of 31

jens.diemer
Collaborator
Collaborator

Reported again with CaseNo:11579587. Smiley Frustrated

Jens

------------------------------------------------------------------------------------------------------------------
https://github.com/jedie/3dsmax_bugs | https://github.com/jedie/3dsmax_patches
Message 25 of 31

Anonymous
Not applicable

Same problem here. 'No task metsdata found'.

Message 26 of 31

jens.diemer
Collaborator
Collaborator

Have get a mail from AD. They confirm the resurrection of MAXX-24290

 

"work-a-round:"

 

> re-submit your jobs after rebooting (with "Skip Existing Images" checked in the Render Setup menu.) 

 

Smiley Mad

Jens

------------------------------------------------------------------------------------------------------------------
https://github.com/jedie/3dsmax_bugs | https://github.com/jedie/3dsmax_patches
0 Likes
Message 27 of 31

jon.bell
Alumni
Alumni

Hello Jens,

 

As you mentioned, this is a recurrence of an earlier defect which was fixed in 3ds Max 2015, but it seems to be back. Our developers are aware of this issue and we have logged a new defect (MAXX-24290) in our database for it.

Right now, the current workaround is to delete and re-submit your jobs after rebooting (with "Skip Existing Images" checked in the Render Setup menu.) 

Alternatively, some users have reported success by reinstalling Backburner as a standalone program.

 

Please note that I'm monitoring this issue, and if I have any further information I'll let everyone know. Thank you for your patience on this.

 

Best regards,

 

Jon A. Bell

Autodesk Technical Support



Jon A. Bell
Senior Technical Support Specialist, 3ds Max
0 Likes
Message 28 of 31

jens.diemer
Collaborator
Collaborator
Accepted solution

jens.diemer schrieb:

Have get a mail from AD. They confirm the resurrection of MAXX-24290

 

"work-a-round:"

 

> re-submit your jobs after rebooting (with "Skip Existing Images" checked in the Render Setup menu.) 

 

Smiley Mad


It seems that this is now fixed in max 2017!

Jens

------------------------------------------------------------------------------------------------------------------
https://github.com/jedie/3dsmax_bugs | https://github.com/jedie/3dsmax_patches
Message 29 of 31

Anonymous
Not applicable

@Anonymous wrote:

I've just started running into this error. If I restart the Manager the jobs all report  'ERR no task metadata found'. I'm using Max 2014 but the errors started when I installed Max 2016.

 

Here's a fix that works for me:

 

Select the job in the queue Monitor.

Right click on it.

Select 'Edit Settings'

Edit one of the settings (I alter the frame range)

Click OK

 

This seems to re-write the metadata so that it's readable and the job will start properly.

 

I then repeat this process and alter the frame range back to what I want it to be.

 

 

You can check that it's worked by clicking on a queued job and see if you get the error.


 

 

This worked for me - thankyou!

 

FYI, I had previously toggled the "Skip Existing Frames" setting, and that did not work. Editing the frame range did the job.

Message 30 of 31

Anonymous
Not applicable

@Anonymous wrote:

I've just started running into this error. If I restart the Manager the jobs all report  'ERR no task metadata found'. I'm using Max 2014 but the errors started when I installed Max 2016.

 

Here's a fix that works for me:

 

Select the job in the queue Monitor.

Right click on it.

Select 'Edit Settings'

Edit one of the settings (I alter the frame range)

Click OK

 

This seems to re-write the metadata so that it's readable and the job will start properly.

 

I then repeat this process and alter the frame range back to what I want it to be.

 

 

You can check that it's worked by clicking on a queued job and see if you get the error.


Hi this just worked for us on 20+ jobs in our queue !

 

All we did was:

 

Selected the failed job in the queue Monitor.

Right clicked on it.

Selected 'Edit Settings'

Edited/added a job description

Clicked OK

 

Thank you !

 

(It didn't quite work on a few smaller jobs, so we just deleted and resubmitted those)

0 Likes
Message 31 of 31

Anonymous
Not applicable

@Anonymous wrote:

I've just started running into this error. If I restart the Manager the jobs all report  'ERR no task metadata found'. I'm using Max 2014 but the errors started when I installed Max 2016.

 

Here's a fix that works for me:

 

Select the job in the queue Monitor.

Right click on it.

Select 'Edit Settings'

Edit one of the settings (I alter the frame range)

Click OK

 

This seems to re-write the metadata so that it's readable and the job will start properly.

 

I then repeat this process and alter the frame range back to what I want it to be.

 

 

You can check that it's worked by clicking on a queued job and see if you get the error.


Sorry I dont quite know what happened with the above post.... (Admin to remove if possible ?)

 

Hi this just worked for us on 20+ jobs in our queue !

 

All we did was:

 

Selected the failed job in the queue Monitor

Right clicked on it

Selected 'Edit Settings'

Edited/added a job description

Clicked OK

 

That then made the job 'Active' again and the servers picked them back up again.

 

Thank you !

 

(It didn't quite work on a few smaller jobs, so we just deleted and resubmitted those)

0 Likes