Common Licensing Errors

Home › Knowledge Base › Licensing ›

Activation key not found in database

This error means that you have entered in an invalid activation key for your product. This error message will also appear if you try to register a floating license with X-Win32, rather than the license server Check that your activation key is typed correctly and retry.

No hostids available

StarNet Products require a valid hostid in order to activate properly. A hostid is usually the MAC address of your system. For information on finding your host id see Host Id

To resolve this issue, activate your network card on your system and ensure you have a valid MAC address.

Flash Users require a USB drive with a Serial Number. See Conforming USB Drive to check if your drive is a valid device.

Cannot connect to specified URL (-132)

This issue generally occurs for users who run X-Win32 from behind a network proxy.

Manually activate the license from http://license.starnet.com/activate

Uncounted license on Terminal Server is disabled (-46)

For security reasons, StarNet disables nodelocked license activations on Terminal Servers. However, this error will also occur if a user tries to run X-Win32 through RDP. For users who use RDP to run X-Win32, contact StarNet Support with your order number referencing this error to have a RDP enabled license extended to you.

Key already used

This error means that your key has already been activated a maximum number of times and you have no activations left. Please contact StarNet Sales for replacement options

Host license.starnet.com not found

This error occurs if you cannot connect to the activation server. This may occur if you are running your application behind a proxy, or you are on a closed network.

Go to a machine which does has internet access and Manually Activate the license from http://license.starnet.com/activate

Connection refused at server (-111)

This error typically occurs if X-Win32 can find the license server, but cannot connect to the live server port (default 5053).

  • Make sure the rlm license server is running on your system
  • Make sure your client is connecting to the proper port. The license server port is specified in the license.lic file. It should match the license server's port (default 5053)
  • Check your firewall configurations. The RLM server listens on 2 ports: the license server port (typically 5053) and the starnet ISV port (randomly assigned. See License Server Port for instructions to specify an ISV port number). Either of these ports may be blocked. Temporarily disable your license server firewall and attempt to reconnect. If the connection succeeds, then it is a firewall issue.

HELLO message for wrong server (-107)

You will receive this error message if you can correctly connect to the license server, but you do not have a valid license being served. The solution is to install a valid floating license on your license server and to verify the ISV is running correctly.

For information on installing a license, see Activating a Floating License

System clock has been set back (-40)

You receive this error if you have recently changed your clock settings. RLM looks for future-dated files in system directories that have a lot of file activity. If a system ran with a future date for a short time, the number of files with
the future date is minimal. Rebooting your system will usually fix the issue.

License Debugging Logs

X-Win32 has the ability to run diagnostics on the licensing code by setting an environment variable.

Debugging Logs for X-Win32

  1. Click on the Start Menu > Run... > cmd
  2. Run the command: set RLM_DIAGNOSTICS="C:\path\to\your\debug.log
    • Note, this needs to be the full path to the debug log.
    • The debug.log must be writable to the user
  3. cd to the X-Win32 directory
  4. Start xwin32 from the command line: xwin32.exe
  5. Wait for any licensing error messages to occur, then exit X-Win32

rlm diagnostics will be written to the debug.log

Debugging Logs for the license server

License server logs are written to the log file that was specified when the server was installed (typically rlm.log in the rlm directory).