Workstation is Windows 7 x64. i7 2700k + 16GB RAM
3 x Slaves are XP64, i7 2600k + 16GB Ram
All running Max 2009 x64 with ‘vray_adv_22002_max2009_x64’.
I’m having problems where if I send a DR job, the slaves are giving the following error:-
warning: Could not connect to host 192.168.0.151: No connection could be made because the target machine actively refused it
(IP of course is different for each slave)
This is driving me f-ing mad!
UAC turned off the workstation. Firewalls turned off everything. Tried running spawner manually rather than as a service but no luck. The thing is, it seems to work for a while, but then suddenly fails and I can’t seem to get them going again. Where should I be looking?
have you tried restarting your file server? Once in a bluemoon windows doesnt release previous connections and then you get max connections maxing out. Saw a patch for this somewhere on Microsoft’s site over December. Can’t remember if it was for server os or just xp.
Tricky did you ever find a solution for this? I just switched to a new workstation and now trying to use my old workstation for DR and am getting the same error. Got it working briefly the other day and thought it would be fine from then on but the problem is back. I’m using Windows 7 on both systems. DR used to work perfectly going the opposite way.
I had the same issue. Notes from ChaosGroup Read as follows:
First, make sure that the all of the nodes participating in the DR are accessing the V-ray license server.
To end this go to:
Start > All programs > Chaos Group > V-Ray ..> Licensing > Administration > Change V-Ray client license settings
and as a primary license server type the IP address of the machine having the dongle
You can check the licenses by typing http://ServerIP:30304/getstatus
where ServerIP is the IP address of the above mentioned computer.
if everything is OK with the licenses launch the DRspawner on every render server.
If you still experience the same problem please send us:
-vraylog file from the render client (the computer from which the rendering is started)
-vraylog and VRSpawner from the render servers that are participating in the DR
(those file could be found in %Temp%)
-----
Upon checking DRspawner log. I noticed it was calling max 2011, even though the spawner was 2013.
0: [2011/Jun/30|09:41:19] ========================== Starting new session ==========================
1: [2011/Jun/30|09:41:20] Got this module name: C:\Program Files\Autodesk\3ds Max 2011\vrayspawner2011.exe
2: [2011/Jun/30|09:41:20] Got this INI file name: C:\Program Files\Autodesk\3ds Max 2011\VRaySpawner.ini
3: [2011/Jun/30|09:41:20] *** ALERT! Could not open INI file: “C:\Program Files\Autodesk\3ds Max 2011\VRaySpawner.ini”. Using defaults.
4: [2011/Jun/30|09:41:20] --
5: [2011/Jun/30|09:41:20] Dumping current settings…
6: [2011/Jun/30|09:41:20] VRaySpawner temp dir: “C:\Program Files\Autodesk\3ds Max 2011\network”
7: [2011/Jun/30|09:41:20] Application name (MAX/VIZ): “C:\Program Files\Autodesk\3ds Max 2011\3dsmax.exe”
8: [2011/Jun/30|09:41:20] --
9: [2011/Jun/30|09:41:20] Process id is 3584 (0xe00)
10: [2011/Jun/30|09:41:20] Executing ““C:\Program Files\Autodesk\3ds Max 2011\3dsmax.exe” -server C:\Program Files\Autodesk\3ds Max 2011\network\vraydummy2011.max”
11: [2011/Jun/30|09:41:32] ========================== Ending session ==========================
Yes, even with both machines firewalls off entirely it fails, says connection refused. It looks more like the 2013 spawner is calling 2011 which is no longer installed, and it fails. Not sure how, probably a bad registry key. I am troublshooting this today. Will report back.
0: [2012/Jun/29|14:26:13] ========================== Starting new session ==========================
1: [2012/Jun/29|14:26:13] Got this module name: C:\Program Files\Autodesk\3ds Max 2013\vrayspawner2013.exe
2: [2012/Jun/29|14:26:13] Got this INI file name: C:\Program Files\Autodesk\3ds Max 2013\VRaySpawner.ini
3: [2012/Jun/29|14:26:13] *** ALERT! Could not open INI file: “C:\Program Files\Autodesk\3ds Max 2013\VRaySpawner.ini”. Using defaults.
4: [2012/Jun/29|14:26:13] --
5: [2012/Jun/29|14:26:13] Dumping current settings…
6: [2012/Jun/29|14:26:13] VRaySpawner temp dir: “C:\Users\DBRYAN~1.POW\AppData\Local\Temp”
7: [2012/Jun/29|14:26:13] Application name (MAX/VIZ): “C:\Program Files\Autodesk\3ds Max 2013\3dsmax.exe”
8: [2012/Jun/29|14:26:13] --
9: [2012/Jun/29|14:26:13] Process id is 7768 (0x1e58)
10: [2012/Jun/29|14:26:13] Executing "“C:\Program Files\Autodesk\3ds Max 2013\3dsmax.exe” -server C:\Users\DBRYAN~1.POW\AppData\Local\Temp\vraydummy2013.max "
It should be referencing this location: “C:\Users\dbryan.POWERCREATIVE\AppData\Local\Temp” but windows (or something) is referencing the wrong path.
Trying to find where to switch DBRYAN~1.POW with dbryan.POWERCREATIVE in the registry relative to this command.
Apparently there was some whack registry keys. I think this is because of our network setting and how it creates user folders. The problem stems from windows firewall. Even with firewall off, the machine was refusing my connection (impossible!). I manually went in and allowed incoming and outgoing exceptions in advanced firewall settings for port 20204. I do not remotely understand why this would be blocked, even if firewall is off, but manually allowing these corrects the problem.
Long story short: Create an incoming and outgoing firewall exception for port 20204 even if you do not use a firewall.
Thanks for replying Vlado, you gave me good hunting ground.
-Joel
I am having the same type of problem where it looks like the render is being sent to my slave computer but it errors and tells me it is actively being denied, also listing the render as completed in the error box. Then resends and fails over and over again.
I would like to try what you did. Where did you get that port number? Is that the same for every computer?
20204 port is used by V-Ray to transfer information between the client and the nodes machines when doing distributed rendering.
You just need to add an exception in your firewall settings for that port number 20204.
I would like to add that I too am experiencing this “actively denied” problem. 3dsmaxdesign 2012 (latest updates) and Vray 2.30.01 running on W7 64bit enterprise on all machines. Spawner originally running as a service, logged in with its own account for maximum permissions on the local machines and the domain here at work.
I have 4 slaves (2 HP bladeservers and 2 prior workstations also from HP). After upgrading to Vray 2x, and reinstalling windows and all software fresh, DR and to some extent Backburner doesn’t work. (This is not a complaint to Chaos, its more of a panicking cry for help) !!!
The really wierd thing is that one of the 2 identical Blade servers works fine, and they are identical in hardware and software. The rest just refuse. All machines have had the windows firewall disabled, and added the inbound and outbound rules for port 20204 TCP added.
Sometimes, (when the planets are aligned for a second) one of the machines might kick in if i quickly go into the firewall setting and enable and disable it, and run the spawner as an application, but even then, the render afterwards will get refused even if I have not changed any settings. The IT guys here at work don’t really seem to be able to help me, except for moving the machines out of the regular Active directory policy group they were in. But that still didn’t help.
I seriously need some assistance in finding out what is wrong, as I am the only one doing this kind of work, and there is nobody here to help me.
I know this is probably not a Vray only problem, as I can’t seem to get Backburner to render reliably either, but I was hoping someone here might be able to give some tips.
All the machines are controlled by remote desktop, including the blades. I don’t see how that affects anything though.
Logoff timeout? Not sure what you mean. Windows remote desktop times out after x amount of time like normal.
What is a green setup? The network cards in the Blades (in all the machines actually) are always on, if that is what you meant.
As logoff timeout I mean that in the domain policy there is rule to set a time after that not only the remote desktop time out but also a user time out (but I’m not sure because it was more than one year ago and our network guy did it…)
I’m not sure but this link seems related to “logoff timeout”
As “green” setup is that what you wrote…so… it’s ok.
EDIT: Now I remember how to test the logoff timeout quickly.
In your blade, run an application (what you want)…wait and after some minutes reconnect and check if your app is On…if not…it means that your session was killed.
If you have just tested it or you noted that any app is killed…you are already ok and I haven’t other ideas..
