Backburner 2015 servers remains 'idle'

[Anonymous]

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?

[Hwagner]

i am having the same issues right now. just all of a sudden, it wont work any more "no metadata faound" error. i hope someone can come up with a solution.

[jens.diemer]

The same here for some Jobs:

• The job never starts
• In Manager: ERR No task metadata found
• I can't change anything in Monitor on this job

3dsmax 2015 with SP3 and backburner 2015.0.1.1688

Is this reported to AD? Is there a CaseNo ?

[jens.diemer]

Ah, i see that there is a new version of backburner here:

Backburner2015.0.2_1699_WIN.zip (zip - 9.47 Mb)

This newer version are on my slaves, but i forgott to update backburner on my main machine, after last windows install...

So i will update it and see if this will be happen again...

[jens.diemer]

It's the same with 2015.0.2 1699

EDIT: I reported this to AD. The Case ID is: 10627483

[Anonymous]

Hi,

All 10 of my Slaves are now sitting 'idle' after upgrading to 2015.0.2_1699 too !

Any update on this or do I downgrade back to 2015.0.1_1688 ?

Thanks

[jens.diemer]

---

craig.fews schrieb:

All 10 of my Slaves are now sitting 'idle' after upgrading to 2015.0.2_1699 too !

---

IMHO this is not directly related to the new Version!!!

I restarted my manager PC (new windows updates)... After reboot, all jobs are idle with: ERR No task metadata found

I looked into:

• %LOCALAPPDATA%\backburner\ServerJob\
• %LOCALAPPDATA%\backburner\Jobs\

Seems to me that all files are fine... I have test the .zip files, and i can open them with 7-zip...

So what's happens here?!?

[Anonymous]

---

jens.diemer wrote: 

IMHO this is not directly related to the new Version!!!

I restarted my manager PC (new windows updates)... After reboot, all jobs are idle with: ERR No task metadata found

I looked into:

• %LOCALAPPDATA%\backburner\ServerJob\
• %LOCALAPPDATA%\backburner\Jobs\

Seems to me that all files are fine... I have test the .zip files, and i can open them with 7-zip...

So what's happens here?!?

---

I agree.

I have just downgraded my Manager PC (a standalone PC to run just the Manager) and one of my Slaves. Still nothing. All 'idle'.

And when I select one of the queued jobs on the Monitor, I get the error: ERR No task metadata found showing on the Manager.

If it helps, all my Slaves are saying: INF Registration to 192.168.2.108 accepted.* Then nothing.

*192.168.2.108 = IP of Manager PC.

Presuming a Windows Update has broken something ? Again ?

[jens.diemer]

To fix this, i deleted all jobs and resubmit them all... But this is really annoying. Even more, because it seems tha all needed data files are there...

[Anonymous]

Yes that's exactly what we decided to do aswell ! Very frustrating, but at least we've solved it!

Until the next batch of Windows Updates that is... 

[Anonymous]

I have the same problem since today, unfortunatly deleting the jobs and adding them again doesn't help. I keep getting the same problem for some of the images 😞 Hope there will be a solution soon!

[jens.diemer]

Now i have the same error with backburner 2016 😞

[jens.diemer]

And happend again

For me it seems that this will allways happen, if the Manager would be restartet!!!

[garry]

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.

[Anonymous]

we have same problem here with bb2016 build 1727 ...

some servers do not get frames for a special job...another job gets served without problem.

tried to delete backburner.xml at the server, tried to remove-assign the server,tried to restarted server...stays idle

someone here at "area" said that backburner is the worst piece of software he ever worked with... i second this after 17 years of work with 3dsmax.

[Anonymous]

hi, I also had this problem, reported it to autodesk, and was told it was a know issue they are working on. It was particualy frusting as it never happened in previous versions. By tinkering around i found a solution that works (for me anyway, hopefuly it will be the same for you).

   Go into the backburner manager, click on edit, the general settings. I changed the 'direct access to jobn path'  location to a fixed location in my documents on my local c drive. It seems the previous location was more of local profile location on my local drive. I no longer have the no metadata error. Hopefuly this will work for you aswell.

[Anonymous]

I just want to add to this so AD keeps notice of this one. I had 7 jobs that Should have completed over the weekend. I must have restarted my computer, the manager, after submitting the first 3. Those thre the error for no task metadata found, then the others worked, so must have been submitted after restarting. 

I just added a frame to each and they are on their way now. So Thanks for putting this info here. This was the first search result, and the correct answer for my immediate needs.

[Anonymous]

I have a bit different problem.

I'm trying to set up network rendering beetwen two computers and I somehow cannot get it to work.

On both computers (desktop and laptop) I have same version of 3ds Max 2014

This is a simple connection beetwen two computers using one cable. Subnet mask 255.255.255.0 and two ip 192.168.0.1 and 0.2

Desktop is my main comp (192.168.0.1), where 3ds max is running. I start renders from here.

On both comps backburner server is running.

On both 'looking for a manager using 224.0.0.1:3234' message pops up and quickly after that they get connected: 'registration to 192.168.0.1 accepted'

Backburner Manager on Desktop says: 'succesful registration' from both IPs

Babckburer Monitor shows two computers connected with the 'idle' status, so far so good.

The problem starts when I click 'send render to network' in Max. A widow pops up where the subnet mask is given 255.255.255.0 and right next to it there's a 'connect' button. If I click this, the BB Manger is not found. If I choose to manualy type in Manager Ip adress (192.168.0.1) I get connected but my laptop is idle, and it's not rendering..Use all server option is ticked.

(I don't really know why the Manager cannot be found using standard subnet mask, should work this way, shouldn't it?)

Am I doing something wrong ?

There is no error poping up.

Thanks for any suggestions.

[Anonymous]

posting like this is called "hijacking" a thread. Please don't do it in the future. If you have a different problem, then post a different problem with that subject title. 

The problem your are getting is not uncommon though, and is usually related to the network settings. I'm not sure this system works at all using a patch cable. I'm not sure what that does to the "network." 

You could try running it through a network switch and see if that helps. You can likely do that through your router. Most wireless routers have at least a couple ports available. 

[jens.diemer]

The "No task metadata found" error has come back, now 😞

2016 with SP3

Can anyone confirm?