Error Codes 2100–2199
Last updated on
This article documents the most common error codes in the range 2100–2199. If you encounter an error code that is not documented here, use the More Help menu to contact our support team.
2100
DinkeyAdd Module Error
Trying to save a DAPF file to a version that is too old (minimum version is 6).
2101
DinkeyAdd Module Error
Trying to save to an old DAPF file version which will cause features that are currently set to be lost (can overwrite if you set the flag FLAGS_LOSE_FEATURES in the call to WriteDAPF).
2102
DinkeyAdd Module Error
DAPF handle passed is NULL. Either it has not been allocated properly or already freed.
2103
DAPF file is in an incorrect format (view error message for more information).
2104
SWKEY_INFO pointer passed is NULL.
2105
SWKEY_INFO structure is too small. Possibly not initialised 'size' field correctly.
2106
The model element in the SWKEY_INFO structure is invalid.
2107
The expiry date element in the SWKEY_INFO structure is invalid.
2109
The expiry date element in the SWKEY_INFO structure is in the past.
2110
DinkeyPro Module Error
The expiry date element in the SWKEY_INFO structure is more than 14 days in the future.
2111
DinkeyPro Module Error
One of the input filenames in the DRIS supplied is empty.
2112
DinkeyPro Module Error
One of the output filenames in the DRIS supplied is empty.
2113
Shell-protecting a Windows program is not supported on macOS and Linux.
2114
Protecting PDF files is not supported on macOS and Linux.
2116
DinkeyAdd Module Error
The output file already exists (call the same API with the FLAGS_OVERWRITE_OUTPUT flag if you want to overwrite this).
2117
DinkeyAdd Module Error
The file_num parameter has an invalid value. It should be the 0-based index of the program in the list that you want to protect or -1 if you want to protect all files in the list.
We made a fix in v7.2.0.2 so that if you are only programming dongles (and not adding protection to any files) then we ignore this parameter. For example, this error could be caused inadvertently if you are using DinkeyAdd or DinkeyAddCmd and use a DAPF file which has no programs to protect and then choose to "Program dongle only".
2119
DinkeyAdd Module Error
The dongle number specified when creating a Software Key is outside the range specified in the DAPF file.
2120
DinkeyAdd Module Error
A licence expiry date in the DAPF file expires before the expiry date of the Software Key (call the CreateSoftwareKey API again with the FLAGS_EXPIRY_DONTCARE flag if you want to carry on regardless).
2121
DinkeyAdd Module Error
The action parameter is invalid.
2123
Adding Shell protection is not supported by DinkeyAdd on this platform.
See Protection Method > The Shell Method in the SDK user manual for full details of supported platforms and file formats.
2125
You are trying to protect a PDF file but the DinkeyAdd.pdf.dat file is not found. It should be in the same directory as the DinkeyAdd module you are calling.
2128
This is an error code from the DinkeyAdd module indicating that the "max days from installation" for a Demo Software Key Template is invalid. This should a number in the range 0-60.
In v7.4.0 there was a bug in the DinkeyAdd.exe GUI so that if the max days value was less than 10 then you would always get this error. This bug was fixed in v7.4.0.2 (build 2).