Error Codes 440–459
Last updated on
440
The licence name of the protected software is not currently being served by DinkeyServer.
If a dongle is connected to the dongle server while DinkeyServer is running, you must restart DinkeyServer for it to detect and serve the dongle.
441
DinkeyServer is busy.
DinkeyServer adds incoming requests to a queue, but for very large numbers of requests in a short time span, the queue can become full and this error is returned. Wait a while for DinkeyServer to process the queued requests, and then try again.
442
The hidden .DO NOT DELETE.dat file on a Dinkey FD Lite could not be accessed.
Use DinkeyChange to restore the file. You need administrator (root on Linux) privileges to perform this action. See DinkeyChange in the SDK user manual for details.
443
DinkeyServer auto-detection is being overridden but there is an error in the configuration file.
Refer to Network Dongles > DinkeyServer Auto-detection in the SDK user manual for the correct format. If you are using a hostname instead of an IP address, this error can indicate that the hostname cannot be resolved.
444
The flash disk part of a Dinkey FD dongle has not been mounted by Linux.
Configure Linux to automatically mount the disk when the dongle is connected to the computer.
445
The operation is not supported by the dongle.
For example, attempting to use the protection API to read or write the data area of a Lite dongle.
446
A R/W algorithm is required for this operation, but there is no R/W algorithm in the dongle.
The API library was locked with the Encrypt data passed to API and Take data encryption parameters from the R/W algorithm options selected. These options apply an additional layer of encryption when passing data to/from the API, for example when reading or writing the dongle data area. This functionality requires a R/W algorithm to be stored in the dongle.
447
The program has already started a network user.
A process may only start one network user. This return code indicates a coding error, i.e. more than one call to DDProtCheck() with the START_NET_USER flag. Update your code to address this.
448
DDGetNetUserList() does not have a connection to DinkeyServer.
Protected software must call DDProtCheck() first to establish the connection to DinkeyServer. If your software is locked to both local and network dongles, you should also check that the dongle found by DDProtCheck() is a network dongle before calling DDGetNetUserList(). Use the model field of the DRIS to do this.
449
The specified licence is not currently being served by DinkeyServer.
The licence_name passed to DDGetNetUserList() was not found in the dongle.
450
Windows failed to load hid.dll.
This DLL is required to communicate with Dinkey Pro and Dinkey FD dongles on Windows. The extended error code is the Windows system error code indicating the cause of the failure.
451
Windows failed to load setupapi.dll.
This DLL is required to communicate with Dinkey Pro and Dinkey FD dongles on Windows. The extended error code is the Windows system error code indicating the cause of the failure.
452–457
These error codes indicate low-level errors enumerating USB HID devices.
Use the More Help menu to contact our support team.
458
A USB HID device behaved in an unexpected way.
Old versions of Dinkey Pro returned this error even if the USB HID device was not a Dinkey Pro or Dinkey FD dongle. Make sure that you are using the latest version.
459
The dongle returned invalid data.
If the error occurs every time the dongle is accessed, this suggests that the dongle memory has been corrupted. For Dinkey FD Lite, use DinkeyChange to restore the dongle. See DinkeyChange in the SDK user manual for details. For all other dongle models, if the dongle is under warranty you can return it to Microcosm or to your distributor for replacement.
If the error occurs intermittently, check that the computer's motherboard and USB adapter drivers are up-to-date. Also check the dongle and USB port for signs of damage or a loose connection.