Dinkey & Dinkey Pro/FD Knowledge Base
| Browse By Category: | Look Up Error Number: | Search: |
Glossary | Contact Us |
Articles
 | Error 400 Program: all. Description: Could not allocate enough memory to proceed with this operation. If this error occurs then you must be very low ... |
| Error 401 Description: Could not detect any Dinkey Pro/FD dongles. If software is protected to both local (Lite or Plus) and network dongles, this err... |
| Error 402 Program: all. Description: Too many dongles attached. For example if you want to program a dongle with DinkeyAdd we insist on only one dong... |
| Error 403 Program: all. Description: The dongle detected is not of the expected type. e.g. Pro Lite, FD Plus etc... For runtime code you select which... |
| Error 404 Program: all. Description: The dongle detected is not of the expected model. For runtime code you select which model to protect your softwa... |
| Error 405 Program: all. Description: Trying to use a demo dongle with non-demo software. Relevant Version: all |
| Error 406 Description: Trying to use a non-demo dongle with demo software or software locked by the demo DinkeyAdd. Your SDK and dongles are personal ... |
| Error 407 Program: all. Description: The dongle detected belongs to another company (does not have the required SDSN). Relevant Version: all |
| Error 408 Problem: The detected dongle's serial number has an unexpected value. If the error occurs in DinkeyAdd: Check that the serial number of the... |
| Error 409 Program: all. Description: The dongle detected has not been programmed with DinkeyAdd. Relevant Version: all |
| Error 410 Description:The Product Code used to protect your software is not the same as the Product Code in the dongle detected. Note - you can use D... |
| Error 411 Program: Runtime, DinkeyChange Description: Runtime - the dongle detected does not contain the licence associated with the program you are... |
| Error 412 Program: all. Description: DRIS not passed correctly in the call to DDProtCheck. Solution: Please view our sample code for examples on how ... |
| Error 413 Problem: The protected software has not been locked to a dongle. Solution: Use DinkeyAdd to add protection. Ensure that you have selected e... |
| Error 414 Program: runtime. Description: The DRIS structure passed to DDProtCheck is too small. Solution:You must set the size field in the DRIS to ... |
| Error 415 Program: all. Description: The DRIS structure passed to DDProtCheck is too large. You are using a version of the DRIS file that is newer th... |
| Error 416 Program: all. Description: The Operating System detected is not supported. Dinkey Pro and Dinkey FD are not compatible with Windows 95 or W... |
| Error 417 Program: Runtime. Description: Bad parameter in DRIS structure: An invalid value for the function or flags fields. If reading/writing da... |
| Error 418 Program: runtime. Description: You have set at least 2 flag values in the DRIS that are contradictory. Relevant Version: all A bug existe... |
| Error 419 Program: Protected program Description: The computer clock has been tampered with (either put forwards or put backwards). Solution: The ... |
| Error 420 Program: runtime. Description: The execution counter has reached 0. Relevant Version: all |
| Error 421 Program: runtime. Description: There are not enough executions left to decrement by the specified amount. This error was returned and no ex... |
| Error 422 Program: runtime. Description: Expiry date reached. Relevant Version: all |
| Error 423 Program: runtime. Description: Too many network users – the limit for the number of simultaneous network users has been reached. Rel... |
| Error 424 Program: runtime. Description: Trying to read or write beyond the end of the dongle data area. Note that the dongle data area is set to the... |
| Error 425 Problem: Trying to read/write or encrypt/decrypt too much data. Solution: For speed reasons we limit this to 1024 bytes. If you want to rea... |
| Error 426 Program: runtime. Description: The user algorithm that you want to execute does not exist. i.e. the alg_number field in the DRIS specifies ... |
| Error 427 Program: runtime. Description: The algorithm that you specified with the variable values that you specified gives a ‘Divide by Zero&r... |
| Error 428 Program: all. Description: This feature has not been implemented yet. Relevant Version: all |
| Error 429 Description: The alt_licence_name field of the DRIS is not null-terminated. Solution: This error code indicates a bug in the code that call... |
| Error 430 Program: all. Description: Calling program is not valid for the protected DLL. Solution: Protect your DLL again specifiying the new program... |
| Error 431 Program: runtime. Description: A DLL that the Shell-protected program depends on does not exist on the user’s machine. Relevant Vers... |
| Error 432 Program: all. Description: The Dinkey FD Service needs to be installed as the user is running under Windows 2000 or XP with restricted acce... |
| Error 433 Program: Dinkey Web Description: Requesting encryption from php (or asp.net etc...) that is not supported by the DinkeyWeb runtime module. ... |
| Error 434 Program: Dinkey Web Solution: Upgrade Dinkey Web module (e.g. dpWeb.dll) to support newer php (or asp.net etc...) sample code. |
| Error 435 Description: DinkeyServer not detected on the network. Either DinkeyServer is not running or it is being blocked by a firewall. Failure to... |
| Error 436 Can no longer connect with DinkeyServer. It may have terminated or the network may be down. |
| Error 437 Your protected software uses a more recent version of the dongle SDK than DinkeyServer. You need to upgrade DinkeyServer to a more recent ... |
| Error 438 Error terminating a network user . This may occur because a network user has not been started from this process. |
| Error 439 No network dongles with the correct Product Code have been detected by DinkeyServer. If you have recently attached a dongle to the dongle ... |
| Error 440 A network dongle with the correct Product Code has been detected but the program running is not in the list of protected programs in the d... |
| Error 441 DinkeyServer is busy. If there are lots of requests to start a network user at the same time the server may be too busy to reply. If you r... |
| Error 442 Problem: There was a problem reading the hidden .DO NOT DELETE.dat file from the flash disk of a Dinkey FD Lite dongle. The most likely caus... |
| Error 443 You are specifying a <prodcode.ini> (or <prodcode.conf> for Linux) file to direct your protected program to find the location of... |
| Error 444 Linux-only error: The flash disk part of Dinkey FD has not been mounted by Linux. Change your Linux settings so that this happens when you... |
| Error 446 You have protected your software specifying API Data encryption with the r/w algorithm but there is not a r/w algorithm in the dongle. |
| Error 447 You have tried to start more than one network user for the same program within the same process. This is not allowed. |
| Error 448 Problem: The DDGetNetUserList() API function cannot locate DinkeyServer. Solution: DDGetNetUserList() cannot use auto-detection or an INI f... |
| Error 449 The licence specified in the call to the DDGetNetUserList API is not found in the network dongle detected. |
| Error 450 This error means that our code could not load the module hid.dll using LoadLibrary. This DLL is part of the OS so it will definitely be pres... |
| Error 451 Error 451 means that there was an error loading a critical Windows system DLL. In practice we have found that this occurs when there is a m... |
| Error 455 There was a bug which meant that this error may occur when using Dinkey FD Lite dongles under Windows for version 5.9.0 or earlier. The full... |
| Error 445 The function you are using in the DRIS is not supported by the dongle detected. e.g. trying to write data to a Lite dongle. |
| Error 458 Problem: A USB HID class device attached to the system does not respond in the correct way. If you have protected your software with the Di... |
| Error 459 Problem: There was an error reading from the dongle. If the error occurs every time the dongle is accessed: This suggests that the dongle m... |
| Error 460 Problem: There was an error reading from the dongle. If the error occurs every time the dongle is accessed: This suggests that the dongle m... |
| Error 461 Problem: There was an error reading from the dongle. If the error occurs intermittently: Ensure that your software is protected with the la... |
| Error 462 Problem: There was an error reading from the dongle. This error indicates that the dongle memory has become corrupted. Either re-program th... |
| Error 463 Problem: There was an error reading from the dongle. If the error occurs every time the dongle is accessed: This suggests that the dongle m... |
| Error 464 Problem: There was an error reading from the dongle data area. If the error occurs every time the dongle is accessed: This suggests that th... |
| Error 465 Problem: The OS has detected the dongle but there was an error communicating with the dongle. On Linux, this error can occur if the inst sc... |
| Error 466 Problem: There was an error reading from the dongle. Solution: Ensure that your software is protected with the latest version of the SDK. C... |
| Error 467 Problem: There was an error reading from the dongle. Solution: Ensure that your software is protected with the latest version of the SDK. C... |
| Error 468 Problem: There was an error reading from the dongle. Solution: Ensure that your software is protected with the latest version of the SDK. C... |
| Error 469 Problem: There was an error reading from the dongle. Solution: Ensure that your software is protected with the latest version of the SDK. C... |
| Error 470 Problem: There was an error reading from the dongle. Solution: Ensure that your software is protected with the latest version of the SDK. C... |
| Error 484 Problem: Unexpected value returned by encrypted communication with the dongle. Solution: Dinkey Pro/FD SDK version 7.1 contains code improv... |
| Error 486 Problem: There was an error communicating with the dongle. If the error occurs every time the dongle is accessed: This suggests that there ... |
| Error 487 Problem: There was an error communicating with the dongle. If the error occurs every time the dongle is accessed: This suggests that there ... |
| Error 488 This error relates to functionality that has been removed from Dinkey Pro/FD. Protect your software with the latest version of the SDK to... |
| Error 493 If you have protection a macOS application that was built with XCode 11 (or higher) then you receive this error when your protected program ... |
| Error 503 This error means that the action (e.g. a protection check) took too long to execute. There are many reasons why this error could occur. The ... |
| Error 504 Dinkey Pro/FD dongles can only be accessed by one thread or process at a time. This error number indicates a problem enforcing this constra... |
| Error 505 Error: the process was blocked by another process accessing the dongle for a considerable time. Solution This other process may have crashe... |
| Error 544 When you Shell-protected a .NET program, DinkeyAdd creates a Dll called XXX.dp32.dll or XXX.dp64.dll (where XXX is the name of your protecte... |
| Error 554 Error 554 is an error opening a socket for network communication. There are many different reasons for this error to occur and obtaining the... |
| Error 560 This error means that the protected application on the client has not received a reply from DinkeyServer. The extended error code is a sock... |
| Error 564 This error means that the protected application on the client has not received a reply from DinkeyServer. The extended error code is a sock... |
| 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 ge... |
| Error 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 f... |
| Error 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 M... |
| Error 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... |
| Error 594 This error can occur if you are using Linux and have not run the "inst" script. |
| Error 598 Problem: An error occurred trying to detect the flash drive part of a Dinkey FD on Mac OS X. This error can occur under the following circum... |
| Error 602 Applies to: DinkeyAdd Description: DinkeyAdd could not find the API library code in the input file. When you add protection using... |
| Error 619 Program giving error: DinkeyAdd Description: The file you are trying to protect does not have a recognised format. The Shell Method current... |
| Error 649 This error indicates a problem opening the specified input file for the Shell Method. The extended error indicates the reason why the file c... |
| Error 671 Description: DinkeyAdd could not create the Shell-protected output file. Solution: The most common cause of this error is that you do not h... |
| Error 672 Error 672 is an error writing the protected output file when using the Shell Method of protection. The extended error will give the reason t... |
| Error 698 You cannot Shell-protect the .NET file because it contains native code. The Shell Method of protection can protect pure .NET assemblies or ... |
| Error 718 This error can occur when adding protection with DinkeyAdd, and when checking a dongle with DinkeyWeb. The meaning of the error code is diff... |
| Error 730 This error can occur if you are using DinkeyWeb under Mac OS X Lion 10.7 (or higher) and using Safari (6.1 or higher). See the related arti... |
| Error 731 This error can occur if you have multiple threads in one process which are doing a protection check under Linux or Mac OS X. We fixed a pro... |
| Error 742 Description: There a problem connecting to the Internet. Solution: Most Internet connection problems are temporary, so the most common solu... |
| Error 743 Description: There a problem connecting to the Internet. Solution: Most Internet connection problems are temporary, so the most common solu... |
| Error 744 Description: There a problem connecting to the Internet. Solution: Most Internet connection problems are temporary, so the most common solu... |
| Error 745 Description: There a problem connecting to the Internet. Solution: Most Internet connection problems are temporary, so the most common solu... |
| Error 746 Description: There a problem connecting to the Internet. Solution: Most Internet connection problems are temporary, so the most common solu... |
| Error 758 Program: DinkeyChange Description: Cannot open the Dinkey Update Code file (DUCF). Versions: all |
| Error 759 Program: DinkeyChange Description: Not a valid Dinkey Update Code file. Versions: all |
| Error 762 Program: DinkeyChange Description: Not a valid Dinkey Update Code file. Versions: all |
| Error 764 Program: DinkeyChange Description: Invalid Code. If the Update Code has been entered manually then it has been entered incorrectly. If you ... |
| Error 765 Program: DinkeyChange Desciption: The Update Code is valid but does was not created for any of the dongles attached to the computer. This ... |
| Error 766 Program: DinkeyChange Description: The update number of the code is higher than expected. The most likely cause is that the customer has fa... |
| Error 767 Program: DinkeyChange Description: The Update Number is lower than expected. The most likely cause is that the customer has already updated... |
| Error 768 Program: DinkeyChange Description: The Update Code has been generated with a version of DinkeyRemote that is too new for the version of Din... |
| Error 769 Programs: DinkeyChange Description: The Update Code will result in too many licences stored in the dongle. Therefore none of the update has... |
| Error 770 Program: DinkeyChange Description: Trying to add a licence that already exists in the dongle. Therefore none of the update has been applied... |
| Error 771 Program: DinkeyChange Description: Not enough memory in the dongle to apply all the required changes requested. Therefore none of the updat... |
| Error 772 Program: DinkeyChange Description: Trying to change or delete a licence that does not exist in the dongle. Versions: all |
| Error 774 Program: DinkeyChange Description: Trying to modify ‘per product’ network users to exceed the maximum allowed for that dongle m... |
| Error 775 Program: DinkeyChange Description: The Update Code wants to modify network users but the target dongle is not a network dongle. Versions: ... |
| Error 777 Error 777 indicates that applying the update code would result in an invalid setting for the simultaneous network user limit. There are two ... |
| Error 778 Program: DinkeyChange Description: You are trying to apply a short update code to a dongle that only allows strongly encrypted update codes... |
| Error 780 Program: DinkeyChange Description: Trying to change the 'per product' network users setting in a dongle that uses 'per licence' network use... |
| Error 781 Program: DinkeyChange Description: Trying to change the 'per licence' network users setting in a dongle that uses 'per product' network use... |
| Error 782 Program: DinkeyChange Description: Trying to modify ‘per program’ network users to exceed the maximum allowed for that dongle m... |
| Error 813 Program: DinkeyChange Description: Adding so many executions to the current value the result value is too large to be stored. Versions: al... |
| Error 822 Program: DinkeyChange Description: Calling DinkeyChange.dll with an invalid mask value. Use one of the constants defined. Versions: all |
| Error 823 Program: DinkeyChange Description: Invalid filename specified for DCGetDiagnosticInfo call in DinkeyChange.dll Versions: all |
| Error 824 Program: DinkeyChange Description: The product code mask specified is too long to be a valid product code (8 characters max). Versions: al... |
| Error 842 The model value passed to DCDownloadDemoSoftwareKey is invalid. |
| Error 843 The Product Code must be specified for the DCDownloadDemoSoftwareKey function. |
| Error 844 The Product Code specified in the DCDownloadDemoSoftwareKey function must not contain spaces. |
| Error 846 DinkeyChange Error The update code that your customer is entering into DinkeyChange is changing the "last date used" to a date that is ahea... |
| Error 848 This error occurs if you are trying to force the OMSRuntime to check with the DinkeyOMS portal. The error means that OMSRuntime is not runn... |
| Error 876 DinkeyRemote Error The "last date used" value should be todays date or a date in the past (todays date is normally the best date to use). |
| Error 917 If you receive error 917/13 on a Linux system when downloading a Temporary or Demo Software Key then you should upgrade to DinkeyChange vers... |
| Error 918 This error will occur if another process has hung trying to access the Software Key. You should wait 1 minute to give the other process ti... |
| Error 922 Problem: A valid Software Key has been found, but it has expired. |
| Error 923 Problem: The Software Key that has been detected is for the wrong type of dongle (e.g. FD instead of Pro). Solution: Create a new Software ... |
| Error 924 Problem: The Software Key detected is for the wrong model of dongle (e.g. Dinkey Pro Lite but Dinkey Pro Plus expected). Solution: Create a... |
| Error 925 Problem: The Software Key detected was created with the demo Dinkey Pro/FD SDK. Once you receive your unique SDK with your SDSN then you sh... |
| Error 926 Problem: You are using the demo Dinkey Pro/FD SDK but detecting a Software Key (created with a non-demo SDK). Once you receive your unique ... |
| Error 927 Problem: The Software Key detected has the wrong SDSN. |
| Error 928 Problem: The Software Key detected has a dongle serial number that is not in the required range. Solution: Create a new Software Key, makin... |
| Error 929 Problem: The Software Key detected has the wrong Product Code. Solution: Create a new Software Key, making sure that the product code that ... |
| Error 932 We cannot obtain a Machine ID for this computer - please run DinkeyChange on this machine and generate diagnostic information and send it to... |
| Error 933 The Machine ID in the Software Key does not match the machine ID of the computer it is on. Either the computer has been significantly upgra... |
| Error 937 This error can occur if your protected software is detecting a Software Key which is corrupt. If you are getting this error running DinkeyS... |
| Error 944 The machine detected is different to the machine that the dongle was locked to. This is most likely because the dongle has been moved to a ... |
| Error 948 version 7.0.0 or newer This error indicates that we have detected multiple instances of DinkeyServer running on the same machine. In this c... |
| Error 952 The protected program giving this error was protected with the option to not allow any usb port sharing across the network (this setting is ... |
| Error 955 This error means that we cannot create a subprocess. This file will only be created if you enabled the extra anti-debug option of the Shell ... |
| Error 956 This error means that a subprocess we created cannot be written to disk. This file will only be written if you enabled the extra anti-debug ... |
| Error 957 This error means that a subprocess we created cannot run. This subprocess will only be run if you enabled the extra anti-debug option of the... |
| Error 958 This error means that an attempt has been made to debug the Shell-protected program. You cannot debug a Shell-protected program. Please run ... |
| Error 959 This error means that a subprocess created by a Shell-protected application is not responding. It has probably been blocked by an anti-virus... |
| Error 968 This error means that a file we created as part of the protection check, could not be opened. This file will only be used if you enabled the... |
| Error 973 You have marked this dongle as blocked using DinkeyOMS and therefore the customer is not allowed to use this dongle. If you have done this ... |
| Error 974 The dongle is using the DinkeyOMS blocking feature but has not connected to DinkeyOMS recently. This is a timeout error. Solution: the cust... |
| Error 1001 Program: Dinkey Web Description: Java is not installed correctly on the client machine or there is a problem calling the Java applet. Solu... |
| Error 1004 Program: Dinkey Web Description: Error performing server-side call. These errors are most likely to be caused by a firewall blocking the se... |
| Error 1005 Program: Dinkey Web Description: Error performing server-side call. These errors are most likely to be caused by a firewall blocking the se... |
| Error 1010 Program: Dinkey Web Description: M_Your_SDSN variable does not match the SDSN of the Dinkey Web module. One of these is probably the demo S... |
| Error 1011 Program: Dinkey Web Description: Could not find the protected Dinkey Web module (dpWeb.dll) on your website in the correct location. Solut... |
| Error 1109 This error indicates that you are trying to add protection to a .NET application using the Shell Method. However, we cannot load a DLL to ma... |
| Error 1129 Description: There a problem connecting to the Internet. Solution: Most Internet connection problems are temporary, so the most common solu... |
| Error 1130 Description: There a problem connecting to the Internet. Solution: Most Internet connection problems are temporary, so the most common solu... |
| Error 1131 Description: There a problem connecting to the Internet. Solution: Most Internet connection problems are temporary, so the most common solu... |
| Error 1132 Description: There a problem connecting to the Internet. Solution: Most Internet connection problems are temporary, so the most common solu... |
| Error 1207 This error will only occur if you are using the debug module. Note - we recommend you only use the debug modules for debugging your own code... |
| Error 1208 This error will only occur if you are using the debug module. Note - we recommend you only use the debug modules for debugging your own code... |
| Error 1212 This error will only occur if you are using the debug module. Note - we recommend you only use the debug modules for debugging your own code... |
| Error 1213 This error can only occur if you are using one of the debug modules. The only reported occurance of this problem is 1213/10 on Linux. In th... |
| Error 1214 This error means that a subprocess created by one of the runtime debug modules has not finished (timed-out). This could be caused by an ant... |
| Error 1229 This error can only occur in the debug module not the standard release module. The error code means that a sub-process that we have created... |
| Error 1330 An error occurred performing analysis of your .NET assembly. A likely cause of this error is that none of the required .NET frameworks ar... |
| Error 1442 An error occurred writing the output file when protecting a .NET application using the Shell Method. Before version 5.7.0, a bug in DinkeyA... |
| Error 1494 Problem: This error can occur when adding protection to a .NET program using the Shell Method. It occurs if you are using Visual Studio 2010... |
| Error 1535 This error can occur when adding Shell protection to a .NET assembly. The error means that we cannot create a temporary file and is most lik... |
| Error 1902 The maximum number of Temporary Software Keys for this machine ID and Product Code has been reached. |
| Error 1905 DinkeyChange error: There is no Temporary Software Key available to download (you need to create one for this machine ID using DinkeyAdd). |
| Error 1906 The Software Key has not been downloaded correctly. You should try to download it again before you can use it. |
| Error 1907 DinkeyChange error: The Temporary Software Key for this Machine ID has expired. |
| Error 1908 You are trying to Create a Temporary Software Key but it already exists for this Machine ID. You can specify the FLAGS_OVERWRITE_SWKEY to o... |
| Error 1909 This error indicates that the date and/or time is incorrect on a user's machine. (NB we allow an hour leeway). If the date and time looks c... |
| Error 1910 DinkeyChange error: The Temporary Software Key for this Machine ID has already been downloaded. |
| Error 1920 You are trying to Create a Demo Software Key Template but it already exists for this Product Code. You can specify the FLAGS_OVERWRITE_SWKE... |
| Error 1921 The "default" dongle model was specified but there is more than one model available in the Demo Software Key Template. You need to specify ... |
| Error 1922 The requested dongle model is not available in the Demo Software Key Template. |
| Error 1923 The Demo Software Key Template for this Product Code has been disabled. |
| Error 1924 You have run out of Demo Software Key activations. Therefore nobody can download a Demo Software Key from any of your templates. You need t... |
| Error 1932 A server-side error occurred in DinkeyOMS while attempting to apply the update code. The extended error is the DinkeyRemote error code. Plea... |
| Error 1938 This error is given by OMSRuntime when the operation could not be completed because there are no transactions left on the DinkeyOMS account.... |
| Error 2100 DinkeyAdd Module Error Trying to save a DAPF file to a version that is too old (minimum version is 6). |
| Error 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 overwrit... |
| Error 2102 DinkeyAdd Module Error DAPF handle passed is NULL. Either it has not been allocated properly or already freed. |
| Error 2103 DAPF file is in an incorrect format (view error message for more information). |
| Error 2104 SWKEY_INFO pointer passed is NULL. |
| Error 2105 SWKEY_INFO structure is too small. Possibly not initialised 'size' field correctly. |
| Error 2106 The model element in the SWKEY_INFO structure is invalid. |
| Error 2107 The expiry date element in the SWKEY_INFO structure is invalid. |
| Error 2109 The expiry date element in the SWKEY_INFO structure is in the past. |
| Error 2110 DinkeyPro Module Error The expiry date element in the SWKEY_INFO structure is more than 14 days in the future. |
| Error 2111 DinkeyPro Module Error One of the input filenames in the DRIS supplied is empty. |
| Error 2112 DinkeyPro Module Error One of the output filenames in the DRIS supplied is empty. |
| Error 2113 DinkeyPro Module Error You cannot Shell-protect a Windows program with DinkeyAdd running in Linux or Mac OS. |
| Error 2114 DinkeyAdd Module Error You cannot add protection to a PDF file under Mac or Linux. |
| Error 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... |
| Error 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... |
| Error 2119 DinkeyAdd Module Error The dongle number specified when creating a Software Key is outside the range specified in the DAPF file. |
| Error 2120 DinkeyAdd Module Error A licence expiry date in the DAPF file expires before the expiry date of the Software Key (call the CreateSoftwareKe... |
| Error 2121 DinkeyAdd Module Error The action parameter is invalid. |
| Error 2123 DinkeyAdd Module Error You cannot protect files using the Shell Method if DinkeyAdd is running on MacOS (Shell support for Linux was added ... |
| Error 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... |
| Error 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... |
| Error 2200 DinkeyAddCmd Error No DAPF file specified on the command line. This is a requirement for DinkeyAddCmd. |
| Error 2201 DinkeyAddCmd Error Option /d used but no filename has been specified. |
| Error 2202 DinkeyAddCmd Error Error creating/opening the file for the dongle number specified by the /d parameter. |
| Error 2204 DinkeyAddCmd Error Option /f used but no file number specified. |
| Error 2205 DinkeyAddCmd Error Option /a used but action valid is either invalid or not specified. |
| Error 2206 DinkeyAddCmd Error Options /a and /e cannot be used together. |
| Error 2207 DinkeyAddCmd Error Option /ei used but no filename specified. |
| Error 2208 DinkeyAddCmd Error Option /eo used but no filename specified. |
| Error 2209 DinkeyAddCmd Error Option /ei used and an input has been specified but no /eo output file has been specified. Either use no files or both i... |
| Error 2210 DinkeyAddCmd Error Option /eo used and an output has been specified but no /ei input file has been specified. Either use no files or both i... |
| Error 2301 DinkeyRemote Module Error Trying to save to an old DRPF file version which will cause features that are currently set to be lost (can overw... |
| Error 2302 DinkeyRemote Module Error DRPF handle passed is NULL. Either it has not been allocated properly or already freed. |
| Error 2303 DinkeyRemote Module Error DRPF file is in an incorrect format (view error message for more information). |
| Error 2306 DinkeyRemote Module Error Error writing to the DinkeyRemote logfile. |
| Error 2307 DinkeyRemote Module Error The update number parameter (or in the DRPF file) is invalid. |
| Error 2400 DinkeyRemoteCmd Error No DRPF file specified on the command line. This is a requirement for DinkeyRemoteCmd. |
| Error 2401 DinkeyRemoteCmd Error Option /d used but no dongle number specified. |
| Error 2402 DinkeyRemoteCmd Error Option /d used but dongle number is not a valid number. |
| Error 2403 DinkeyRemoteCmd Error Option /u used but no update number specified. |
| Error 2404 DinkeyRemoteCmd Error Option /u used but update number is not a valid number. |
| Error 2405 DinkeyRemoteCmd Error Option /o used but there is no ducf filename specified. |
| Error 3003 OMSRuntime error Problem: An update receipt file exists on disk but OMSRuntime cannot open/read the file correctly. OMSRuntime will try to... |
| Error 3020 This is an error installing OMSRuntime on to a Linux operating system. We cannot determine the system type. e.g. systemd or init.d etc... P... |
| Error 3048 OMSRuntime is trying to apply an update code sent from DinkeyOMS which affects the expiry date in the dongle. However, it has detected that ... |
| Error 3049 OMSRuntime error creating named-pipe used for communication. The extended error will give the Linux system error why this call is failing. |
| Error 3100 This error is a mismatch between the SDSN that you are using on the developer portal and the SDSN of the OMSDeveloper service that you runn... |
