Error Codes 600–699
Last updated on
This article documents the most common error codes in the range 600–699. If you encounter an error code that is not documented here, use the More Help menu to contact our support team.
602
DinkeyAdd could not find the API library code in the input file.
When you add protection using the API protection method, DinkeyAdd modifies the runtime protection API code. The file that you specify as the input pathname on the Programs tab must be a file that contains the API code.
If you statically link the API library (.obj or .o file), the input pathname must be the name of the executable that links the library. If you use a dynamic API library or plugin (.dll, .dylib, .so, etc), the input pathname must be the name of the API library file, not the executable that calls it.
619
Program giving error: DinkeyAdd
Description: The file you are trying to protect does not have a recognised format. The Shell Method currently supports executable files, DLLs and PDFs.
Solution - use the API Method instead of the Shell Method of protection. You will need to modify your source code to do this. Please look at the sample code for your language. It is important that you read the README for the sample is it contains important information.
649
This error indicates a problem opening the specified input file for the Shell Method. The extended error indicates the reason why the file cannot be opened.
If you are protecting a PDF file, or if you are protecting a file with API & Shell and you are also getting the extended error code 32, then this can be caused by an anti-virus program interfering with DinkeyAdd. If you upgrade to version 7.1.1.1 or later then this problem is fixed.
671
DinkeyAdd could not create the Shell-protected output file.
The most common cause of this error is that you do not have sufficient access rights to create the output file. Ensure that the Output Pathname you specified is a folder you can write to, such as your desktop or Documents folder.
672
Error writing the protected output file when using the Shell Method of protection. The extended error will give the reason the file cannot be written.
There is one case of a known bug: if you are shell-protecting a 32-bit Linux binary file with the 64-bit Linux DinkeyAdd, then this error can occur on some occasions, with the extended error 14 (bad address). In this case the solution is to upgrade the Dinkey Pro SDK to version 8.0 or higher.
698
You cannot Shell-protect the .NET file because it contains native code.
The Shell Method of protection can protect pure .NET assemblies or traditional native binaries, however it does not work with a mixture of .NET assemblies and native code in the same file.
One solution is separate the native code into a separate DLL. Then you can Shell-protect both files.
Another solution is to use the API Method of protection instead of the Shell method.