EASYLABEL cannot get a valid license and will not run. What do I do?

Knowledge Base > Troubleshooting > EASYLABEL cannot get a valid license and will not run. What do I do?

in Troubleshooting

1. Is this a new installation?

YES Did you read and follow the Quick Start Guide that is provided?

Did you encounter any errors or problems during the installation process?

NO What has changed on the network?

2. Is the Multi-User WIBU-Key functioning properly? Please follow the steps in the WIBU-Key troubleshooter

3. What error message is being displayed?

The Network License Manager cannot be found on the network

Cause: The WIBU-Key Server machine is not running.
Solution: Be sure that the machine that has been designated as the WIBU-Key Server is running.

Cause: The WIBU-Key ‘Network Server’ application (WkSvW32.exe) is not running.
Solution: To be sure that the WIBU-Key ‘Network Server’ software is running, use the CRTL+ALT+DELETE key combination to open the Task Manager and look for “WkSvW32.exe”. If it is not start the WIBU-Key ‘Network Server’ application by selecting Start –> Programs –> WIBU-KEY –> Network Server from the Start menu. To start the WIBU-Key ‘Network Server’ as a service and then right click on the system tray icon and select “Start as service”. The WIBU-Key ‘Network Server’ application will then be restarted every time the computer is restarted. Or if you are using Windows 95b/98/ME for the WIBU-Key server, you can add a shortcut to the WIBU-Key ‘Network Server’ application to the ‘Start Up’ program folder (Start/Programs/Start Up)

Cause: The WIBU-Key Server is not being found and the action is timing out.
Solution: Add the WIBU-Key Server to the WkLAN Server Search list. To do this select Settings –> Control Panel from the start menu. Double-click on the WIBU-Key Icon in Control Panel and then select the Network Tab. Under the WkLAN Server Search List at the bottom, try to browse to your server. If this fails to find your server, you may have to enter the server’s Machine Name or Static IP Address in the lower entry and then click ADD to add it to your WkLAN Server Search List.

Cause: The WkLAN Server Search list has the wrong Machine Name or IP Address for the WIBU-Key Server
Solution: Verify that the Machine Name/IP Address set in the WkLAN Server Search list is the correct one for the WIBU-Key Server.

Cause: The Multi-User WIBU-Key is not plugged into the parallel port or USB port of the WIBU-Key Server machine.
Solution: Locate the teal colored WIBU-Key with a round ‘M’ label and plug it into the parallel or USB port of the WIBU-Key Server machine.

Cause: The Multi-User WIBU-Key was plugged into the parallel port or USB port of the WIBU-Key Server machine after the WIBU-Key ‘Network Server’ application (WkSvW32.exe) was started.
Solution: Stop and then restart the WIBU-Key ‘Network Server’ application (WkSvW32.exe). Alternatively, you can simply reboot the WIBU-Key Server machine.

Cause: The UDP packets used for communication between the Clients and the WIBU-Key Server are being blocked.
Solution: For ANY AND ALL firewalls in place between the Client and the WIBU-Key Server, make sure UDP Port 22347 remains open. Windows XP Service Pack 2 (SP2) includes a firewall and will block this port by default. If crossing a subnet, be sure that ANY AND ALL firewalls, bridges, switches and routers are configured to rebroadcast the UDP packets. This must be determined and configured by the network administrator. The port in question is UDP Port: 22347. Simply pinging the IP address is not enough to ensure that UDP packets can be passed on the port. A UDP test tool such as this one from http://www.simplecomtools.com/udptesttool.html should be used to verify that UDP packets can be sent and received by both the license server and the clients.

Cause: The WkLAN Port Address for the Clients and the WIBU-Key Server is not the same.
Solution: Select Settings –> Control Panel from the start menu. Double-click on the WIBU-Key Icon in Control Panel and then select the Network Tab. Verify that the value for WkLAN Port Address matches the value at the Server. If it does not, change the “User Specific” drop down to “Machine Specific” and enter the value the Server has listed (the default is 22347). This port should be left open if there is a firewall present such as the one included in Windows XP SP2.

Cause: The Client or WIBU-Key Server has one of the WIBU-Key Subsytems disabled so that the WIBU driver is not looking for the key locally and/or the Network.
Solution: Select Settings –> Control Panel from the start menu. Double-click on the WIBU-Key Icon in Control Panel and then select the Network Tab. There are 3 check boxes listed under ‘WIBU-KEY Subsystems’. The boxes marked “Local (Kernel)” and “WkLAN” should be checked.

Cause: When printing on the WIBU-Key Server PC to the same parallel port the WIBU-Key is on it may be possible for clients (or the server) to report that they have trouble getting a license. This is usually caused by a significant, ongoing data flow out of the port such as when printing using $all or alphanumeric incrementation.
Solution: It may be necessary in these cases to move the printer off the back of the WIBU-Key to another port. If this is not possible, a USB WIBU-Key should be used.

Cause: You are using a USB WIBU-Key on Vista 64 or XP 64 in a Virtual Machine.
Solution: None. This is currently not supported by the WIBU-Key driver.

The network license manager has failed, due to either the license server not running on the network, or a missing or faulty software key. In order to continue running EASYLABEL 5 Multi-User for up to 7 days, DO NOT close EASYLABEL 5 Multi-User or shut down your computer. You have 7 days to remedy the problem before EASYLABEL 5 Multi-User will shut down. Please inform your network administrator immediately.

Cause: The WIBU-Key Server machine has stopped running.
Solution: Be sure that the machine that has been designated as the WIBU-Key Server is running properly.

Cause: The WIBU-Key ‘Network Server’ (WkSvW32.exe) has stopped running.
Solution: To be sure that the WIBU-Key ‘Network Server’ software is running, use the CRTL+ALT+DELETE key combination to open the Task Manager and look for “WkSvW32.exe”. If it is not start the WIBU-Key ‘Network Server’ application by selecting Start –> Programs –> WIBU-KEY –> Network Server from the Start menu. To start the WIBU-Key ‘Network Server’ as a service and then right click on the system tray icon and select “Start as service”. The WIBU-Key ‘Network Server’ application will then be restarted every time the computer is restarted. Or if you are using Windows 95b/98/ME for the WIBU-Key server, you can add a shortcut to the WIBU-Key ‘Network Server’ application to the ‘Start Up’ program folder (Windows/Start Menu/Programs/StartUp)

The network license manager cannot be contacted, and your 7 days are now expired. EASYLABEL 5 Multi-User will now exit.

Cause: EASYLABEL 5 Multi-User has been unsuccessful in contacting the WIBU-Key Server for 7 days.
Solution: Resolve the problem with the WIBU-Key Server machine, WIBU-Key ‘Network Server’ application or the Multi-User WIBU-Key.

All of the available licenses are currently in use.

Cause: All of the available licenses are being used.
Solution: To make a license available, close a client out of EASYLABEL 5 Multi-User.

Cause: Not all available licenses are being used. If a client does not exit EASYLABEL 5 Multi-User properly, the license from that client does not get immediately handed back to the WIBU-Key Server so that another client can access it. You will need to wait approximately 5 minutes before the license will be automatically sent back to the WIBU-Key Server, making it available for use by another client.
Solution: In the future, exit EASYLABEL 5 Multi-User properly. This can be done by choosing File | Exit from the menu, clicking the “x” in the upper right corner or by clicking the EL icon in the upper left corner and choosing “Close”. Exiting the software properly allows the license to be handed back to the WIBU-Key Server immediately.

WK724 error when trying to start up the client software

Cause: This is NOT a WIBU-Key error. This problem occurs when the DNS address can not be resolved.
Solution: This can happen because the server IP address entered on that client is expired and has changed. Can also be that the WIBU-Key Server’s Domain Name has changed.

“Cluster not found ” error or “Invalid Key” when trying to start the client software but checking the Control Panel shows the key to be present.

Cause: This can be caused by having the wrong key for the version of software used.
Solution: Ensure that the key is programmed correctly for the version of the software used. All keys will have 2 lines. The first line will be programmed with a 250275 or a 2173 in the first box and a 123 in the second box.
The second line will be programmed as follows:
‘Not For Resale’ key are programmed with 1 and labeled R.
‘Print Only’ keys are programmed with 2 and labeled O
‘Terminal Server’ keys are programmed with 3 and labeled T
‘Silver’ keys are programmed with 4 and labeled S
‘Gold’ keys are programmed with 5 and labeled G
‘Platinum’ keys are programmed with 6 and labeled P
‘Multi-User’ keys are programmed with 7 and labeled M.

A Sporadic “WIBU-KEY error 7 is occurred” or “The accessed WIBU-BOX in not ready (timeout)(7).” or “The program needs WIBU-BOX with 250275:123.” or even a “Virus Check failed!” message despite correctly installed drivers and Parallel WIBU-Key.

Cause: Some notebooks and “newer” PCs don’t supply the LPT interface with enough power. This can cause a Timeout problem where the WIBU-Key driver can not access the WIBU-BOX within the expected time interval.
Solution: The time interval can be increased by using a DelayFactor. The Delay Factor can be changed by:
Open the Windows Control Panel.
Double-click on the WIBU-KEY Program group.
Select the ‘Setup’ tab.
Highlight the parallel port the key is attached to in the list on the left.
Enter a value for Delay Factor on the lower right.
Click Apply and then click OK.

NOTE: Start with smaller values of Delay Factor first (1-4). The larger you make the value for delay factor, the longer it will take for EASYLABEL to open

0