My current setup is that i have one workstation with a vray dongle which has 1 3dsmax interface license and 6 render node licenses.
I also have a secondary workstation which has another dongle which has 1 3dsmax interface license and 1 render node license.
The problem i sometimes get is that when i render from my main workstation, the second workstation fails to contribute - and i am sure this is because the licensing system thinks that there is not a spare license on the network (but there is). I have two workstations and 5 render nodes (& i have a total of two interface licenses & 7 render node licenses). I have had this working OK in the past, but recently not so much. What is more strange to me now is that, when i am distributed rendering from my main workstation (but the main workstation is not contributing to the rendering) using all available nodes (including the secondary workstation) the license server on primary workstation says 5 out of six nodes are in use (6 machines are being used for the distributed render). When i look at the secondary workstation & check the license server, it says that no nodes are being utilised (i.e. it says 1 free render node). So, the license server is telling me 5 nodes are being used when 6 are actually being used.
Currently, if i try & render with all 7 machines, it is very likely that the secondary workstation will not participate. However, if i exclude the primary workstation from the render, then the secondary workstation will indeed participate (as noted above where i described what the license server is telling me).
Is there a way to check what is going on & make sure i can use 7 machines to participate ? (all of the machines have had 3dsMax SP3 removed & i am running Vray 31002). I have in the past had all 7 working together.
Have you tried putting both dongles in 1 machine?
I would try that first. Then there is no confusion as to what machine is looking for what dongle
What is the configuration of the License Server of the slave and workstation machines?
Since you have two dongles you have to use the IP address of both machines in the License Server as a Primary and Alternative Server.
Alternative Server will be used if all the licenses from the Primary Server are currently engaged.
I have both dongles on the same machine now - and it works but not reliably. For example, last night i was doing some rendering and all machines are active as they should be. In the morning when i come in to start another rendering I can see that one of the machines is not being allowed to render (it gives you the “render host is not responding” message. So i checked the license server and lo & behold it is only reading one dongle. So - last night it was seeing both dongles and this morning it is only seeing one. I tried using the wibukey to rescan for dongles and it tells me there are two attached dongles - but still i am only getting one in the license server readout.
This can be problem with WIBU drivers or with usb ports. Are you using usb 3.0 ?
Please make sure that the latest WiBu driver and the latest V-Ray license server are installed on the machine:
Even if you already had the latest version it is a good idea to reinstall them.
The latest Wibu Driver is 6.30b and it can be downloaded from the link bellow:
The latest V-Ray license server from here:
http://www.chaosgroup.com/en/2/downloads.html?s=v-ray-license-server
When you are re-installing the WiBu driver please follow the steps bellow:
To clean up your WibuKey installation please do the following:
1. Unplug all WibuBoxes - plug off the dongle from the PC.
2. Uninstall the WibuKey driver using “Programs and Features” in the Control Panel.
3. Open the folder [%systemroot%\inf] in Windows explorer.
4. Search within all “oem*.inf” files for the search term “WIBU” and delete them (if any). Delete all corresponding .pnf files (e.g. you found oem345.inf, delete oem345.pnf) and the inf file itself. and wibukeyPCMCIA.inf
5. Open the folder [%systemroot%\system32\drivers] and there search and delete all Wibukey*.sys files.
6. Open Registry from Windows Start and in the Search type “regedit”. Then find and delete the following registry keys:
“HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services” – if a folder „WIBUKEY” and/or „WibuKey2" (or “WibuKey2_64” on a 64bit OS) exists, delete it.
“HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS” – delete this key if it exists
6. Restart the computer.
Now you are ready to make a clean installation of WibuKey:
1. After reboot reinstall the WibuKey driver (please download the latest driver form the official WIBU Systems site, under “WibuKey for Users” section here http://www.wibu.com/downloads-user-software.html ). Ensure to have administrative rights. Don’t plug in any WibuBox (dongle)!
2. After installation has finished plug in the dongle.
3. The “New Hardware found” dialog will appear and install the new hardware automatically.
If the same issue appears even after re-installation please contact us at support@chaosgroup.com along a link to this thread.
WHen you say “Search within all “oem*.inf” files for the search term “WIBU” and delete them (if any)” do you mean i need to individually open up every such file (I found 102 of them) and search for the text “WIBU” and then delete that text & save the “oem*.inf” file ? Or do you mean i should delete any “oem*.inf” file that contains the text “WIBU” ? Also, i presume i should go for the 64bit version since my OS is 64bit…
It would be better to search for files containing “WIBU” in the filename instead of “oem*.inf” and then delete those files.
