The new location is http://ccatemplic.creo.com/cfldatabasewebgen. Links on the CFL site are being updated and users are being redirected to the new location. Note: This site is not available outside the firewall.

Go to the troubleshooting item.

A feature license must be compatible with the device's CR version.
Go to the troubleshooting item.

A new version (3.1.71) of the Service Dongle Manager is available. Microsoft .NET Framework 1.1 and 2.0 must also be installed for the full licensing mechanism to work.

Go to the Downloads page for installers and more information.

To order a USB customer dongle, you must request part number 518-01599A not 632-00197.
Go to Ordering a customer dongle for more information.

Customer dongles are black with blue marking and serial numbers start with C. Service dongles are black with teal marking and serial numbers start with S. Part numbers for both dongles have not changed. Dongle photos show all versions of the dongles.

Microsoft .NET Framework may be corrupted after installing .NET Framework 2.0.
Go to the troubleshooting item.

Microsoft Windows Environmental Variables may be set incorrectly.
Go to the troubleshooting item.

If .NET Framework is damaged, the Service Dongle Manager software will not run.
Go to the troubleshooting item.

If these problems occur after you install Creo Feature Licensing on a customer workstation, see the troubleshooting item. You may have to replace the Digi ClassicBoard serial card on the workstation.

If the service dongle is plugged in when you run the Service Shell Host Configuration wizard, the TCP/IP Configuration wizard automatically starts. This can destroy the network configuration on Magnus 400 Quantum devices. To configure MCE board connectivity only for these devices, run the Host Configuration wizard without the service dongle.

This troubleshooting item has been updated with instructions for installing driver version 7.3.2. Version 5.41 and 5.42 can cause applications such as Prinergy, Prinergy Evo, and Print Console, which use the Sentinel driver to communicate with the dongle, to consume large amounts of CPU time and the server locks up. For details and the solution to this problem, see Sentinel driver conflict with dongle causes Dell servers to lock up.

The version 7.3.2 driver and installation instructions are also available on the Downloads page.

In some systems, a newly-installed dongle will use Sentinel driver version 5.41 instead of version 5.42, which is the version configured in the baseline image. This causes applications such as Prinergy, Prinergy Evo, and Print Console, which use the Sentinel driver to communicate with the dongle, to consume large amounts of CPU time and the server locks up. For details and the solution to this problem, see Sentinel driver conflict with dongle causes Dell PE830, 840, 2900, 2950 servers to lock up.

In some systems, a newly-installed dongle will use Sentinel driver version 5.41 instead of version 5.42, which is the version configured in the baseline image. This causes applications such as Prinergy, Prinergy Evo, and Print Console, which use the Sentinel driver to communicate with the dongle, to consume large amounts of CPU time and the server locks up. For details and the solution to this problem, see Sentinel driver conflict with dongle causes Dell PE830, 840, 2900, 2950 servers to lock up.