Q12587 : No CDEGS Protection key detected

I get a "No CDEGS Protection key detected" message when I start a SES software program. What must be done to correct this so that the program can be used?


The reason that this message shows up is that either your CDEGS software protection key is not connected or no driver was installed or the wrong type of driver was installed.

First, identify which key you have. The name of the key is printed on it. If you are not sure, then please consult the images below:

  1. Local Key (Stand-alone)

     (Scribe Key) (Hasp Key)
  2. Network Key (Client-server)

    (NetHASP USB Key)   (NetHASP Parallel Key)

Make sure the key is securely connected to port LPT1 (i.e. the parallel port of your PC), or to a USB port if your key is a USB key.

    If you have a network key, please install the NetHASP License manager on the computer the NetHasp key is connected to. Use the setup file lmsetup.exe from the "Tools\NetHASP\Server\win32" folder in the SES Software CD to install it.

    Then, please use SESLicenseManager to configure your key.

    1. To open SES License Manager, click Start, point to All Programs, point to SES Software, point to System, and then click SESLicenseManager.
    2. On the File menu, click Check License, or click the Check button on the toolbar. The SES Key Diagnostics Wizard appears.
    3. Select the type of software protection key you will be using, and then follow the instructions in the SES Key Diagnostics Wizard.


    1. If the Install Key Driver button is visible (meaning that the device driver of the current selected protection key is not installed), you need to click this button to install the driver. A local protection key will not work properly (if at all) without the correct key device driver installed in the system.
    2. In larger networks, clients may be unable to find the license manager through the normal broadcast method. To solve this, client machines can be configured by running the SESNetKey utility from the "Start | All Programs | SES Software | System" menu to help them locate the License Manager on the network.
    3. The NetHASP License manager uses TCP and UDP ports 475 for communications - so please ensure that these ports are open or that the program itself is allowed through the firewall.

    No Related Articles Available.

    No Attachments Available.

    No Related Links Available.

    No user comments available for this article.

    • Created on 01/19/2007
    • Last Modified on 01/19/2007
    • Last Modified by Administrator.
    • Article has been viewed 114819 times.