Error Codes 460–479

Last updated on

460

The dongle returned invalid data.

If the error occurs every time the dongle is accessed, this suggests that the dongle memory has been corrupted. If the dongle is under warranty you can return it to Microcosm or to your distributor for replacement.

If the error occurs intermittently, check that the computer's motherboard and USB adapter drivers are up-to-date. Also check the dongle and USB port for signs of damage or a loose connection.

461

The dongle returned invalid data.

If the error occurs every time the dongle is accessed, this suggests that the dongle memory has been corrupted. For Dinkey FD Lite, use DinkeyChange to restore the dongle. See DinkeyChange in the SDK user manual for details. For Dinkey Pro Lite, if the dongle is under warranty you can return it to Microcosm or to your distributor for replacement. For all other dongle models, reprogram the dongle with DinkeyAdd.

If the error occurs intermittently, check that the computer's motherboard and USB adapter drivers are up-to-date. Also check the dongle and USB port for signs of damage or a loose connection.

462

The dongle returned an invalid list of licences.

This suggests that the dongle memory has been corrupted. Reprogram the dongle with DinkeyAdd, or use secure update codes to reset the list of licences in the dongle. First use an update code to remove all licences in the dongle, then use a second update code to recreate the licence(s).

463

The dongle returned invalid licence data.

This suggests that the dongle memory has been corrupted. Reprogram the dongle with DinkeyAdd.

464

The dongle returned invalid data from the data area.

This suggests that the dongle memory has been corrupted. Reprogram the dongle with DinkeyAdd, or use a secure update code to reset the data area. The update code must overwrite the whole data area.

465–471

The system cannot read from the dongle.

On Linux, these errors can occur if the inst script has not been run, or if an old version of inst was used.

These errors can also occur if a computer went to sleep or into hibernation and did not correctly restore power to the USB ports when it woke up. Disconnect and reconnect the dongle, or restart the computer.

In virtual environments, these errors can indicate that USB port virtualisation is not working correctly. See this article for more information about using Dinkey Pro in virtual machines and container environments.

472–479

The system cannot write to the dongle.

Use the More Help menu to contact our support team.