Announcement

Collapse
No announcement yet.

License Server Crashing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • License Server Crashing

    Every Friday morning between 8-9am Easter Standard time our vray license server will crash and we will have to restart the machine it is on to get it working. This has been since upgrading to the latest version of the vray license server. We have checked the computer logs and it appears to be only the vrlservice that is affected.

  • #2
    Hi

    Just came here to say the same think with vray for sketchup. But it stop working after last windows 10 update.

    Comment


    • #3
      Originally posted by jandrewg View Post
      Every Friday morning between 8-9am Easter Standard time our vray license server will crash and we will have to restart the machine it is on to get it working. This has been since upgrading to the latest version of the vray license server. We have checked the computer logs and it appears to be only the vrlservice that is affected.
      Is there a task on the machine that is executed weekly at the time of crash on the machine? Backup, some optimization etc. that can stop some or all running services? Also - what's the OS version on the license server computer? Do the OS logs report some error related to VRLService?


      Originally posted by elfis View Post
      Just came here to say the same think with vray for sketchup. But it stop working after last windows 10 update.
      Please refer to https://forums.chaosgroup.com/forum/...ves-vrlservice

      Ivan Slavchev

      SysOps

      Chaos Group

      Comment


      • #4
        Thanks for the reply Ivan. The only thing we saw in the logs was that the service had stopped responding but no information past that. We never set any automated updates or anything but we checked anyways and there was nothing set. It is a vanilla install of windows 7 and we do have a dongle. We are going to do some upgrades shortly and I will be moving it to a machine running server 2016.

        Comment


        • #5
          You can check your dongle drivers version from Control Panel -> WibuKey->"About" tab. If it's older than 6.32 - reinstall the drivers. I'm attaching a small batch script to help with a clean install (if you use it - rename it from .txt to .bat), you can do that manually too with the procedure below:

          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 for all "oem*.inf" files for 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\Servi ces? ? 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

          7. Restart the computer.

          New drivers can be downloaded from https://www.wibu.com/downloads-user-...uKey_for_Users

          6.40 drivers work only with the latest license server versions, 6.32 will work with license server 3.x too.


          Also - set the log level to "Verbose" from http://127.0.0.1:30304/#/settings on the license server computer and if you get the same problem after that - you can send us the logs ( http://127.0.0.1:30304/logs/download ) at support@chaosgroup.com.

          Attached Files
          Ivan Slavchev

          SysOps

          Chaos Group

          Comment


          • #6
            I'll see if I can get this done tonight and see if it crashes tomorrow morning (Friday). If it doesn't I think it'll be in the clear. Thanks again Ivan.

            Comment

            Working...
            X