Forum FAQ: Terminal Server License Server/Remote Desktop License Server Only Issuing Temporary Licenses and Event ID 17 Logged.

    General discussion

  • Symptom


    Your Terminal Server license server or Remote Desktop license server issues only temporary client access licenses (CALs). In the System log you see Event ID 17 logged when the Terminal Services Licensing/Remote Desktop Licensing service is restarted, or when the computer is restarted. The event continues to be logged even after you attempt to reactivate the license server.


    Event Type: Warning
    Event Source: TermServLicensing
    Event Category: None
    Event ID: 17
    Date: 3/17/2010
    Time: 3:14:13 AM
    User: N/A
    Computer: LS01
    One or more Terminal Server Licensing certificates on server LS01 are corrupt. Terminal Server Licensing will only issue temporary licenses until the server is reactivated. See Terminal Server Licensing help topic for more information.


    After you start receiving the Event ID 17, any interaction with the Microsoft Clearinghouse except for reactivation will result in the error below and the license server is deactivated. Deactivation will only occur on license servers connected to the internet that have the connection method set to Automatic. 


    Windows Server 2008 R2 Activate Server Wizard Error


    The RD License Manager encountered an internal error from the license server. Message Number: 0xc0110011


    Windows Server 2008 and Windows Server 2003 Activate Server Wizard Error


    The License Server Activation Wizard encountered an internal error from the license server
    Message Number: 0xc0110011

    Once the license server becomes deactivated, an Event ID 38 will also be logged:

    Event Type: Error
    Event Source: TermServLicensing
    Event Category: None
    Event ID: 38
    Date: 3/17/2010
    Time: 3:15:32 AM
    User: N/A
    Can't generate a license for client because of error 'Can't add certificate to store, error c0010020.'

    This issue affects Windows Server 2008 R2, Windows Server 2008, and Windows Server 2003 license servers that were activated using the Automatic connection method.




    The certificate that was issued by the Microsoft Clearinghouse to the licensing server expired on February 26, 2010. Certificate expiration is incorrectly interpreted as a corrupted certificate and the Event 17 is logged.


    When the license server is activated, Microsoft provides the license server with a limited-use digital certificate that validates server ownership and identity. Microsoft uses the X.509 industry standard certificate for this purpose. Using this certificate, a license server can make subsequent transactions with Microsoft.


    This certificate is written to the following registry locations:

    • HKEY_LOCAL_MACHINE\Software\Microsoft\TermServLicensing\Certificates
    • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermservLicensing\Parameters\Certificates.000
    • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermservLicensing\Parameters\Certificates.001 


    Attempting to activate the license server fails using the telephone or web connection method as the Web and Telephone methods wrongly assume that registry key will not be present, as the certificates are generated only if activation was done by automatic connection method.




    Use one of the following methods to resolve the issue. It is not necessary to reinstall the Terminal Server Licensing or Remote Desktop Licensing role to resolve this issue.


    Method 1 - License Server Connected to the Internet

    Reactivate the server ensuring that the Connection Method is Automatic. Reactivating using the Automatic connection method will resolve the issue as it removes all of the certificate keys.


    Method 2 - License Server Not Connected to the Internet

    1. Stop the Terminal Services Licensing\Remote Desktop Licensing service either from the Services snap-in or from the command line using net stop termservlicensing.
    2. Delete all of the following registry keys:

    3. Start the Terminal Services Licensing\Remote Desktop Licensing service from the Services snap-in or from the command line using net start termservlicensing.



    More Information


    Windows Server Division has published a blog to describe this issue. For more information, please refer to the following blog:



    Applies to

    • Windows 2000 Server
    • Windows Server 2003
    • Windows Server 2003 R2
    • Windows Server 2008
    • Windows Server 2008 R2
    Thursday, October 14, 2010 2:17 AM