Tweet
At work our IT just updated to 3.40.04 on our server. It's after I render once or twice, the license gets locked up and gives me a 1002 error (cannot obtain license). I check the Status page for the server and it shows for interface licenses as "Interface licenses: Total = 2, Engaged = -1 and Free 3". I noticed I see it go to -1 or -2 for Engaged when the problem happens and it never frees up unless I restart the server. It'll show 127.0.0.1 for Sessions with "0" for GUI, Render and DR. Is this a known bug?
-
-
The issue should disappear if you restart the license server but it would be better to update V-Ray License Server to its latest version.
What version you are using right now?
Would it be possible to update and inform us if there is any improvement or it still gives that error? -
I did restart the server and as soon as I started to do test renders, it would lock up the licenses. I'll instruct them to make sure to update the license server itself. Thanks!Comment
-
Please let us now if the issue is still there even after the update.Comment
-
we had the same issue, the only workaround we found is to leave open the web page of your license server <ipOflicenseServer> :30304/getstatusComment
-
yeah we're still having the issue. I had them reinstall the vray license server, reinstall vray 2017, uninstall vray 2016.5. Right now IT is out this week doing remote work but we plan to keep troubleshooting when they get back. I still get -1 or -2 engaged licenses sometimes just by opening a new scene and hitting render or IPR. Other times, it may take a couple test renders before it locks up the licenses. Vray for Maya 2016.5 (previous 3.3x final version) worked fine. It was upgrading to 3.4 that caused these issues, which is the only ver which works with 2017. Is it possible some leftover files from the previous version are interfering, even after he uninstalled? maybe a .plist or something hidden somewhere?
I actually have left the web page open, mainly just to see when it's locked up and it hasn't helped stop the problem here.
Local workstation:
OSX 10.11.6
Mac Pro trashcan
Vray 2017 3.4.04
Maya 2017 (no update 1).
checking on OS version for Xserve (vray server).Last edited by pixelmonk; 26-09-2016, 07:17 AM.Comment
-
Let's try the following.
First remove/uninstall V-Ray for Maya, V-Ray License Server and Wibukey drivers.
Once everything has been removed please download and install the latest versions of Wibukey drivers from here:
https://www.wibu.com/downloads-user-software.html
And the latest version of V-Ray License server from here:
https://download.chaosgroup.com/?product=48
Once those are installed install the latest version of V-Ray again, you may download it from the link bellow if needed:
https://download.chaosgroup.com/?product=47&platform=48
Then run the same tests as before and if the issue occurs again please copy and send us the log file of the V-Ray License server from here:
servername:30304/getlog
And let us also know whether the license server and all the machines that accessing it are in the same subnet.
Looking forward to hearing from you.Comment
Comment