Error Codes 500–599
Last updated on
This article documents the most common error codes in the range 500–599. If you encounter an error code that is not documented here, use the More Help menu to contact our support team.
503
An operation in secure code timed out.
There are many reasons why an operation can time out: the extended error code will give more information.
504
Failed to create a mutex.
Dinkey Pro/FD dongles can only be accessed by one thread at a time. The mutex that enforces this constraint could not be created.
If your protected software is a Universal Windows Platform app (previously known as a Windows Store app or Metro-style app) this error can occur when the software is locked to a local dongle (Lite or Plus models). Only network dongles are supported by this type of app.
On Linux, older versions of Dinkey Pro can give this error due to an incompatibility with a Linux security feature. Make sure that you are using the latest version.
505
The operation timed out waiting to communicate with the dongle.
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.
507
The protected software cannot open a required file.
For Shell-protected .NET assemblies, the file that cannot be opened is the <assemblyname>.dp32.dll or <assemblyname>.dp64.dll file created by DinkeyAdd when adding protection.
For protected software that uses the calling program feature, the file that cannot be opened is the calling program.
The extended error code is a system error code indicating why the operating system cannot open the file.
544
<assemblyname>.dp32.dll or <assemblyname>.dp64.dll contains an unexpected value.
This error often indicates that your protected software is trying to use an outdated version of one of these assemblies. When you modify your assembly and create a new locked copy of it using DinkeyAdd, new, corresponding <assemblyname>.dp32.dll and/or <assemblyname>.dp64.dll assemblies are also created. You must distribute these alongside the new version of your Shell-protected assembly.
554
Cannot open a socket for network communication.
The extended error code is a system error code indicating why the operating system cannot open the socket.
560
This error means that the protected application on the client has not received a reply from DinkeyServer.
The extended error code is a socket error which could indicate the problem.
This could be happening because a firewall is blocking communication on the client or the server.
Alternatively it can be caused by a program such as an anti-virus blocking network communication on the client or the server.
Obtaining the DinkeyServer log file can be useful. In particular it is helpful to know if DinkeyServer is logging an error at the same time as the protected program on the client is giving an error.
NB If the extended error code is 556 then it means a socket handle has closed by an external program. Please check firewalls or anti-virus programs.
564
This error means that the protected application on the client has not received a reply from DinkeyServer.
The extended error code is a socket error which could indicate the problem.
This could be happening because a firewall is blocking communication on the client or the server.
Alternatively it can be caused by a program such as an anti-virus blocking network communication on the client or the server.
Obtaining the DinkeyServer log file can be useful. In particular it is helpful to know if DinkeyServer is logging an error at the same time as the protected program on the client is giving an error.
578
This error occurs when we cannot determine which drive letter is associated with the Dinkey FD dongle attached to your machine.
You can get this error if you are running under a virtual OS. In this case the client OS often does not preserve the USB device hierarchy, so we cannot detect which flash disk belongs to which dongle.
If you use the API Method and you do not need to know the flash disk drive letter / mount path then you can set the DONT_RETURN_FD_DRIVE flag, so that our code does not try to find out the flash drive and hence does not give error 578.
If you use the Shell Method of protection then this is done automatically for you since version 7.3.0.1.
Alternatively, it may be that the flash disk part of the dongle is not detected and a drive letter has not been assigned by the OS. You can check that by looking using a file explorer. In this case there may be a problem with the dongle - please contact Microcosm.
580
If you are receiving error 580 using a Dinkey FD Net dongle then you can fix this problem by upgrading to SDK version 6.2.3 or higher. The fix is in DinkeyServer.
585
Some customers have received the error 585/10038 using a network dongle, only with 64-bit protected software and only when using the Shell Method or linking our static object module.
This problem has been fixed with version 6.2.3 build 4 or higher (10/02/2014).
586
This error is specific to Net dongles.
This error indicates that there is a problem trying to communicate between the client and the server. The extended error code will tell you more information as to why the connection failed.
One possibility is that a firewall is blocking communication between the client and the server.
594
This error can occur if you are using Linux and have not run the inst script.
598
An error occurred trying to detect the flash drive part of a Dinkey FD on macOS (Mac OS X). This error can occur under the following circumstances:
1) The flash disk has been ejected (by clicking the Eject button in Finder for example) but the Dinkey FD dongle is still attached to the Mac.
2) This can occur in OS X 10.11 El Capitan (or newer) due to a bug introduced in El Capitan. In this case you should update your Dinkey Pro/FD SDK to version 7.1.1 or higher and use that SDK to produce a new locked copy of your protected software. It is not necessary to reprogram any dongles.