Max2017 install broke DR on Max2016

[Streetwise]

I've been running Max2016 and 3.4 on my workstation and 5 nodes for sometime now. On my workstation, DR has been working great up until now. Last week, I installed Max2017 (but not BB) in order to see what it looked like as I'll probably migrate at some point. But now when I render a scene on my workstation (2016), DR does not work and only the workstation treads are present. What might have broke?

Thanks.

[Zdravko.Keremidchiev]

Do you get any errors in the V-Ray Message window? Can you send us a vraylog.txt file?

[alexander.kazandzhiev]

Normally you should render just once through BB before running DR, it's because Max should setup some directories for network rendering. I think you can do it with any BB just the 3ds Max must be the one you want to render with.

Best regards,
Alexander

[Streetwise]

What's odd is that everything was working great prior to the 2017 test installation. I've since tried sending a job to BB, and then DR, but it does the same thing. I'm also able to send a DR job off to BB which works great including all nodes, including my workstation (if I turn Spawner on). So it really baffles me as to why I can't use DR for a local render on the workstation. I've attached a log file.vraylog.zip

Normally you should render just once through BB before running DR, it's because Max should setup some directories for network rendering. I think you can do it with any BB just the 3ds Max must be the one you want to render with.

Best regards,
Alexander

[Zdravko.Keremidchiev]

Have you run V-Ray spawner with Run as administrator option? If not please try it.

[Streetwise]

Have you run V-Ray spawner with Run as administrator option? If not please try it.

Well that seems odd to have to run Spawner on the workstation, but I did what you said, and it fixed it! I turned spawner back off and tried it again -- no issues. DR is now working again! Thank you!