Error Codes 900–949
Last updated on
This article documents the most common error codes in the range 900–949. If you encounter an error code that is not documented here, use the More Help menu to contact our support team.
917
Unable to create a mutex while accessing a software key.
Old versions of Dinkey Pro can return this error due to an incompatibility with a Linux kernel security feature. Make sure that you are using the latest version.
918
The operation timed out waiting to communicate with the software key.
This error can occur when a large number of different threads or processes attempt to access the dongle at the same time.
It can also indicate that another process has crashed or stopped responding while accessing the dongle, but the operating system is still blocking access for other processes. Forcibly terminate the unresponsive process, or restart the computer.
922
The software key has expired.
923
Detected a software key with an unexpected type (Pro or FD).
Create a new software key, making sure that the dongle type and model match those that were specified when the protected software was locked by DinkeyAdd.
924
Detected a software key with an unexpected model (Lite, Plus or Net).
Create a new software key, making sure that the dongle type and model match those that were specified when the protected software was locked by DinkeyAdd.
925
Non-demo software detected a demo software key.
Software keys created using the demo SDK have SDSN 10101. See this article to learn how to find your SDSN.
926
Demo software detected a non-demo software key.
Software keys created using the demo SDK have SDSN 10101. After your first order you should uninstall the demo SDK and re-protect your software using your personalised SDK. See this article for more information.
927
Detected a software key with an unexpected SDSN.
928
Detected a software key with an unexpected dongle serial number.
Create a new software key, making sure that the dongle number matches the number, or is within the range of numbers, specified when the protected software was locked by DinkeyAdd.
929
Detected a software key with an unexpected product code.
Create a new software key, making sure that the product code matches the one that was used when the protected software was locked by DinkeyAdd.
932
A machine ID for this computer cannot be created.
Use DinkeyChange on the affected computer to generate diagnostic information and send it to the Dinkey Pro support team for investigation.
933
The machine ID in the software key does not match the machine ID of the computer.
This error can occur when the computer's hardware and/or operating system has changed so significantly that it appears to be a different machine. It can also indicate that the software key file was copied from another computer, which itself may indicate an attempt to circumvent your software's copy protection.
937
The software key file is corrupt.
There was a bug in DinkeyServer versions prior to 7.6 that could cause this error. Update DinkeyServer to the latest version.
944
The machine ID in the dongle does not match the machine ID of the computer.
The most likely cause of this error is that the dongle has been moved to another computer. It can also occur when the computer's hardware and/or operating system has changed so significantly that it appears to be a different machine.
Update the dongle to reset its stored machine ID. Use DinkeyRemote to create an update with the Reset dongle so it can be locked to another computer option enabled on the Other Info tab.
948
The network dongle is already in use by another instance of DinkeyServer.
DinkeyServer will terminate itself after returning this error.
This error can also occur if any of the following happen while DinkeyServer is running:
- The dongle was removed from the computer and replaced with another network dongle for the same protected software.
- The dongle was removed from the computer and replaced with a software key.
- The dongle was reprogrammed using DinkeyAdd.
In all cases, restart DinkeyServer to resolve the issue.