Backburner No Plugin Available to Handle Job

[olly]

Just installed Service Pack 5 for Max 2014 and now Backburner is misbehaving.

We now have two max 2014 plugins listed and half our farm is in one pool and half in the other! See the screengrab below:



The problem is backburner only wants to use servers in the top pool and servers in the bottom generate the "No Plugin Available to Handle Job" error. Any ideas on how to fix this?

Cheers,
Olly

[DanielBrew]

We had this. You need to install SP5 on the render farm as well.

[olly]

You need to install SP5 on the render farm as well.

Yes I thought the could be the cause but I did install it on all nodes.

Anyone else seen this?

I thought I could hack which servers are in which pool but can't find where this plugin list is defined. Can someone point me in the right direction?

[Morne]

I had this about a month ago, it was the slaves that couldnt get a vray license for some reason
That's why it said "no plugin"

It was weird since if you run a local backburner job on each, then it works fine.
Somehow it sorted itself out and started working again after couple of hours...

[zoranm]

I had the same problem last week. They updated massfx and that stuffs up backburner servers. You'll need to install SP5 on all serversZoran

[cgrant3d]

We had the same issue - ended up removing SP5 and going back to SP3 so we could get work done.

That evening a solution was posted on the Area. http://forums.autodesk.com/t5/3ds-Ma...l/td-p/4941516

[olly]

Look like sp5 was the culprit.

I installed it to all pc's remotely via the command line and after further investigation the install failed on half the farm. After installing correctly the node jumps back into the main pool.

As an aside does anyone know why max service packs take so long (about 1 hour) to install on a machine? And causes max to be so much slower to open! Seem ridiculous, unless is it peculiar to our network?

[zoranm]

Someone posted a command line script to execute installation in a matter of minutes. Just do a search on this forum. Zoran

[olly]

Yes that is how I deploy service packs - I meant the actual time the msp takes to install is about an hour on each pc. Of course the installs all run concurrently but it seems way to slow. Here is a snippet of the bat file I push via psexec:

start /wait cmd /C msiexec /update "\\server\service packs\3dsMaxDesign2014_SP5.msp" /quiet /passive

Is anyone else experiencing this when installing service pack 5 or is it just us?