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 cannot find the API library code in the specified 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
DinkeyAdd does not support protecting the specified file.
For the Shell protection method, see Protection Method > The Shell Method in the SDK user manual for information about which types of file can be Shell-protected.
For the API method, this error can occur when locking a macOS universal binary that contains code for a platform that DinkeyAdd does not support. Check that you are using the latest version of the SDK and make sure that you are DinkeyAdd and API libraries taken from the same SDK.
637
DinkeyAdd could not create the output file while adding protection.
The extended error code is an operating system error code indicating why the file could not be created. The most common cause 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.
638
DinkeyAdd could not write to the output file while adding protection.
The extended error code is an operating system error code indicating why the file could not be written.
649
DinkeyAdd could not open the input file while adding protection.
The extended error code is an operating system error code indicating why the file could not be opened.
671
DinkeyAdd could not create the output file while adding Shell protection to a native binary.
The extended error code is an operating system error code indicating why the file could not be created. The most common cause 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
DinkeyAdd could not write to the output file while adding Shell protection to a native binary.
The extended error code is an operating system error code indicating why the file could not be written.
698
DinkeyAdd does not support protecting the specified file.
Mixed assemblies containing both native and managed code are not supported by the Shell protection method. Restructure your native and managed code into separate files, or use the API protection method.