V-Ray process exits when trying to swarm render

V-Ray V-Ray for SketchUp Issues
, , , ,
1

I am working to upgrade our systems from Sketchup 2022 and Vray5 to Sketchup 2024 and Vray7 and I am trying to get Swarm 2 to work but am having issues with the render node cancelling shortly after it starts rendering.

I have granted the node access through the firewall but it keeps failing with the following message:
[ERROR - app] V-Ray 7.00.05 58864bd0 process exited with 11

The full log output from the cmd line shows how this behavior is happening repeatedly:

[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - mesg] Request to ensure V-Ray AppSDK 7.00.05 58864bd0…
[INFO - mesg] V-Ray AppSDK 7.00.05 58864bd0 exists (ready=True)
[INFO - mesg] Request to start V-Ray AppSDK 7.00.05 58864bd0…
[INFO - app] Starting V-Ray AppSDK 7.00.05 58864bd0 from C:\Users\Admin\AppData\Local\Temp\VRay\3452 (first detect version)
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - mesg] Request to start V-Ray AppSDK 7.00.05 58864bd0…
[WARN - app] V-Ray AppSDK 7.00.05 58864bd0 may not be started during V-Ray AppSDK 7.00.05 58864bd0 started at 2025-04-28 18:25:46.0049144 UTC
[ERROR - app] V-Ray 7.00.05 58864bd0 process exited with 11
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - mesg] Request to ensure V-Ray AppSDK 7.00.05 58864bd0…
[INFO - mesg] V-Ray AppSDK 7.00.05 58864bd0 exists (ready=True)
[INFO - mesg] Request to start V-Ray AppSDK 7.00.05 58864bd0…
[INFO - app] Starting V-Ray AppSDK 7.00.05 58864bd0 from C:\Users\Admin\AppData\Local\Temp\VRay\3452 (first detect version)
[INFO - mesg] Request to stop V-Ray server
[ERROR - app] V-Ray 7.00.05 58864bd0 process exited with 1
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - mesg] Request to ensure V-Ray AppSDK 7.00.05 58864bd0…
[INFO - mesg] V-Ray AppSDK 7.00.05 58864bd0 exists (ready=True)
[INFO - mesg] Request to start V-Ray AppSDK 7.00.05 58864bd0…
[INFO - app] Starting V-Ray AppSDK 7.00.05 58864bd0 from C:\Users\Admin\AppData\Local\Temp\VRay\3452 (first detect version)
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - mesg] Request to start V-Ray AppSDK 7.00.05 58864bd0…
[WARN - app] V-Ray AppSDK 7.00.05 58864bd0 may not be started during V-Ray AppSDK 7.00.05 58864bd0 started at 2025-04-28 18:27:01.2970989 UTC
[ERROR - app] V-Ray 7.00.05 58864bd0 process exited with 11
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - mesg] Request to ensure V-Ray AppSDK 7.00.05 58864bd0…
[INFO - mesg] V-Ray AppSDK 7.00.05 58864bd0 exists (ready=True)
[INFO - mesg] Request to start V-Ray AppSDK 7.00.05 58864bd0…
[INFO - app] Starting V-Ray AppSDK 7.00.05 58864bd0 from C:\Users\Admin\AppData\Local\Temp\VRay\3452 (first detect version)
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - mesg] Request to start V-Ray AppSDK 7.00.05 58864bd0…
[WARN - app] V-Ray AppSDK 7.00.05 58864bd0 may not be started during V-Ray AppSDK 7.00.05 58864bd0 started at 2025-04-28 18:27:26.4599048 UTC
[ERROR - app] V-Ray 7.00.05 58864bd0 process exited with 11
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - mesg] Request to ensure V-Ray AppSDK 7.00.05 58864bd0…
[INFO - mesg] V-Ray AppSDK 7.00.05 58864bd0 exists (ready=True)
[INFO - mesg] Request to start V-Ray AppSDK 7.00.05 58864bd0…
[INFO - app] Starting V-Ray AppSDK 7.00.05 58864bd0 from C:\Users\Admin\AppData\Local\Temp\VRay\3452 (first detect version)
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - mesg] Request to start V-Ray AppSDK 7.00.05 58864bd0…
[WARN - app] V-Ray AppSDK 7.00.05 58864bd0 may not be started during V-Ray AppSDK 7.00.05 58864bd0 started at 2025-04-28 18:27:51.5984624 UTC
[ERROR - app] V-Ray 7.00.05 58864bd0 process exited with 11
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - mesg] Request to ensure V-Ray AppSDK 7.00.05 58864bd0…
[INFO - mesg] V-Ray AppSDK 7.00.05 58864bd0 exists (ready=True)
[INFO - mesg] Request to start V-Ray AppSDK 7.00.05 58864bd0…
[INFO - app] Starting V-Ray AppSDK 7.00.05 58864bd0 from C:\Users\Admin\AppData\Local\Temp\VRay\3452 (first detect version)
[INFO - audit] 192.168.1.10[<>*]:2a6b9980-bde5-449d-b11d-971fb718e74b asked for all permissions
[INFO - mesg] Request to start V-Ray AppSDK 7.00.05 58864bd0…
[WARN - app] V-Ray AppSDK 7.00.05 58864bd0 may not be started during V-Ray AppSDK 7.00.05 58864bd0 started at 2025-04-28 18:28:16.6881169 UTC​

I have my render node PC configured as the Origin but ive tried with my main PC as the origin as well and noticed no difference in behavior.
The render works fine on my local PC and there doesnt seem to be any issues with licensing.

Any assistance would be greatly appreciated.

2

Here is the Vray Swarm log from a render I just tried a few seconds ago
swarm-vray-server.txt (65.4 KB)

3

Hi kevin_olsen,

Thank you for reporting this.
We are currently investigating a similar issue with Swarm. It might even be the same exact one.
I hope we’ll find a solution soon.

A good news is that in the next V-Ray update we will allow you to use a Classic Distributed Rendering approach.
It doesn’t rely on Swarm to manage the render nodes.
You’ll basically be able to start a V-Ray Standalone Server on the nodes and list their IPs on the computer rendering.
This workflow requires more manual work but could be more predictable.

I’ll keep you posted,
Konstantin

4

Thanks for the quick response @konstantin_chaos , I’m glad to hear the more manual option is going to be available since that sounds a bit more like how I have my configuration set up.
Hoping for an update soon!

Thank you,
Kevin

5

Hi @kevin_olsen ​,

V-Ray 7.1 for SketchUp was released on Monday.
It includes both a new version of Swarm and Classic DR.

Konstantin

6

Thank you @konstantin_chaos I am using that version right now and I love classic DR so far. However now ive been having some issues with Laubwerks plants not showing up so I am currently chasing that issue now.
Upgrading is so much fun haha :slight_smile:

7

I ended up having to move back down to 7.03 due to an issue with 7.10 being unable to display Laubwerks plants but now I am having this Swarm 2 issue again. Was there ever any indication as to what caused this type of behavior and how to potentially fix it on this version?

Thanks