| Product: | IT Tools for ETS3, Elvis |
| Version: | 2.x |
| Booth: | 2010-10-06 |
Summary
Access to WibuKey on the network has been set up as described in kb000002.htm, but the licenses are not recognized.
Details
Please restart the Wibu service.
If the WibuKey has been unplugged and replugged in between:
The WibuKey Server is not dynamic, i.e. it does not automatically detect that a WibuBox has been plugged in afterwards and accordingly does not release the licenses over the network.
There are 2 ways to do this:
1. Right-click on the WibuKey server icon and select “Import new WibuBoxes” from the options. Then start the WibuKey NetworkMonitor (Start – Programs – WibuKey – NetworkMonitor) and click on the icon with the magnifying glass. The Network Monitor will now search the network for WibuKey servers. Your server should now appear on the left side of the list and all detected licenses in the right window (FirmCode, UserCode, number of maximum and free licenses).
2. Restart the WibuKey Server process via the Service Manager (stop – restart). Then start the WibuKey Network Monitor (Start – Programs – WibuKey – NetworkMonitor) and click on the icon with the magnifying glass. The Network Monitor will now search the network for WibuKey servers.
Your server should now appear on the left side of the list and all detected licenses in the right window.
If you get the error message “Server Mode Access to 2329: 40120 failed with error 34”, it could be because a license has been assigned locally on the computer on which the dongle is plugged (server). Error 34 indicates that the server machine is accessing the dongle and using a license.
When accessing the Wibukey on the network via WKLAN, it is only possible to access it either locally or via the clients.
