Distributed Render with Max 2017 Phoenix not working

[Syclone1]

Glad you got it running

That solved it.



Syclone1, Thank you! Your tip reminded me that I needed to go into the properties dialog of the VraySpawner Service and set the Log On to my local admin account, but also set the Recovery to restart the service after the first two failures.
Now all slaves in the farm are running with registered services and are handling the water sim fast. They restart automatically after machine restarts without having to go into each one to launch the spawner application.

Edit: Now also a backburner job is processing the water sim with DR working very well on all slaves. All is well.

[joelly3d]

I am having this same issue, permissions are all proper and not sure. No buckets but local work. Went through the render troubleshooting process too (https://docs.chaosgroup.com/display/...uted+Rendering). This is on latest Max2020 VRay Next (not nightly), Phoenix 4.

***UPDATE
After investigating further, I re-installed Phoenix and realized that the render slave option was just for VRay standalone, so I had to do a Full install on the render node to get it to work. I overlooked that it wasn't a Max Render Slave option. We've all been trained to blow through installs so fast that we can skip something so obvious. Figured I would share as others may encounter the same thing.

[olika]

joelly3d Oh boy!

thank you so much sharing this!
Saved my A**, was fiddling around for an hour or so and just to start to write a post in here and then i dscovered your post and that was it! sometimes... Thanks!