Spawner Starting, dropping, coming back and fails again in loop

[3LP]

Hi there,
I have got a scene here where I have got a lot of problem with.
I just can't spawn...

The dr are comming, starting and dropping in loop, so here is a print screen :


I'm struggling here. I already tried to merged my file several times to be sure that there is no legacy bug for some reason.

Thanks

Stan

[PIXELBOX_SRO]

yep, i have this too on one of the nodes

Vlado, any ideas what could be causing this?

[vlado]

If it is tied to a particular scene, then it would be best if you can get us the scene. I know that scenes with the HSDS modifier will cause this, but there may be something else in your case.

Best regards,
Vlado

[cadmonkey33]

we had a similar problem with one of our slaves. both the 2011 dr service and the 2012 dr service were running. disabling the 2011 dr service fixed the problem.

[greysheep5]

we had the same here with max 2010 and max 2012 vray spawner running which lead to the problem of dropping DR connections in max 2012. it seems unregistering the vray2010 spawner as a service has helped us too, good tip! wouldn´t have thought of this i guess...

best regards and thanks,

christoph.

[greysheep5]

well, the problem is not fully solved, it seem i rejoiced to soon. one of the render slaves keeps playing the "sending - not responding - resetting and sending - ...." game as 3LP describes above! any further tipps on the matter? the problem is with max 2012 and vray 2.0, the vrayspawner2010 service is deactivated (we only have 2010 and 2012 and skipped on the 2011 release).

best regards,

christoph.

[greysheep5]

vlado, any ideas what could cause the above mentioned troubles with render slaves with max 2012 and vray 2.0??? i keep getting them, only one of the slaves wants to play like they all should... all 4 pc´s are relatively new and very similar win7x64 machines btw.

best regards,

christoph.

[Bpositive]

Same problem here with max 2012 and vray 2.3.01 -Just can't get the spawner to work - so annoying....

[Bpositive]

Solved by completely removing windows firewall...!