Error Codes 700–799
Last updated on
This article documents the most common error codes in the range 700–799. If you encounter an error code that is not documented here, use the More Help menu to contact our support team.
718
DinkeyAdd cannot find the data area content file specified.
Note that relative paths are resolved relative to DinkeyAdd's current working directory (or the working directory of the process calling the DinkeyAdd API).
731
Unable to create a mutex.
This error can occur when there are a large number of threads in the same process attempting to access the dongle. If this error occurs often, consider restructuring your code.
739-749
A problem occurred during communication with a server on the internet.
Most internet connection problems are temporary. Wait a while and then try to perform the action again.
If the problem persists, check to see whether the operating system and other applications can access the internet. Also check the availability of Microcosm servers (www.microcosm.co.uk and www.microcosm.com) using ping and/or a web browser.
Error 745 can occur in a Shell-protected DLL when used with a temporary software key or demo software key. Software keys are not compatible with Shell-protected DLLs containing native code. Shell-protected .NET assemblies are compatible.
See related articles for more information about extended error codes related to internet connection problems, that can help you to diagnose the underlying cause.
758
DinkeyChange cannot open the DUCF file specified.
759
The DUCF file specified is invalid.
762–764
The update code is invalid.
If the update code is in a DUCF file, this error suggests that the file is corrupt or has been modified. If this error occurs with a short update code, check that the update code was entered correctly into DinkeyChange.
765
The matching dongle for this update code was not found.
Check the product code, dongle number and update number of the dongle that is to be updated, and create a new update code that matches these values.
766
The update number of the update code is higher than expected.
This error can occur if a previous update has not been applied to the dongle.
767
The update number of the update code is lower than expected.
This error can occur if the update has already been successfully applied to the dongle, and the dongle's update number has been incremented.
768
The update cannot be applied because the update code is not supported by DinkeyChange.
This error indicates that the update code was created using a version of DinkeyRemote that is newer than DinkeyChange. Update to the latest version of Dinkey Pro and distribute the latest DinkeyChange to users.
769
The update cannot be applied because it would exceed the maximum number of licences that can be stored in the dongle.
None of the changes contained in the update were applied.
770
DinkeyChange cannot add a new licence to the dongle because the licence already exists.
None of the changes contained in the update were applied.
771
The update cannot be applied because it would exceed the total amount of memory available in the dongle.
None of the changes contained in the update were applied.
772
The update cannot be applied because a licence was not found in the dongle.
None of the changes contained in the update were applied.
774
The update cannot be applied because it would exceed the maximum per-product network user limit supported by the dongle.
For example, an update cannot set the network user limit of a Dinkey Pro Net 5 to a value greater than 5.
None of the changes contained in the update were applied.
775
The update cannot be applied because the dongle is not a network dongle.
None of the changes contained in the update were applied.
777
The update cannot be applied because it would result in an invalid network user limit value.
None of the changes contained in the update were applied.
When changing the dongle from a per-licence network user limit to per-product, the update must also set a value for the per-product network user limit.
When adding a new licence to a dongle with a per-licence user limit, the update must specify a value for the new licence's network user limit.
778
The dongle does not support short update codes.
Recreate the update as a strongly encrypted update code in a DUCF file.
780
The update cannot be applied because the dongle uses per-licence network user limits.
This error can occur when applying an update code that includes a change to the per-product network user limit. This change is not valid for the dongle being updated. Create a new update code using DinkeyRemote. Specify the change to network users on the Licences tab, not the Other Info tab.
781
The update cannot be applied because the dongle use a per-product network user limit.
This error can occur when applying an update code that includes changes to one or more per-licence network user limits. These changes are not valid for the dongle being updated. Create a new update code using DinkeyRemote. Specify the change to network users on the Other Info tab, not the Licences tab.
782
The update cannot be applied because it would exceed the maximum network user limit supported by the dongle.
For example, an update cannot set the network user limit of a Dinkey Pro Net 5 to a value greater than 5.
None of the changes contained in the update were applied.This error can occur when updating a dongle that uses per-licence network user limits. The sum of the user limit values for all licences cannot exceed the total supported by the dongle.