Symptom: Your Terminal Services Licensing Server is no longer activated on or after February 26, 2010. If you try to re-activate the server, you are greeted with the following message:
“The License Server Activation Wizard encountered an internal error from the license server. Message Number: 0xc0110011”
You may also see the following events in the server’s log:
Event 17:
Event Type: Warning
Event Source: TermServLicensing
Event Category: None
Event ID: 17
Description:
One or more Terminal Server Licensing certificates on server computer name are corrupt. Terminal Server Licensing will only issue temporary licenses until the server is reactivated. See Terminal Server Licensing help topic for more information.
Event 38:
Event Type: Error
Event Source: TermServLicensing
Event Category: None
Event ID: 38
Description:
Can’t generate a license for client because of error ‘Can’t add certificate to store, error c0010020.
Problem: This is a known issue due to a certificate issued by the Microsoft clearing house expiring on February 26, 2010.
Solution:
- Stop the Terminal Server Licensing Service.
- Delete the following three registry keys: (you may want to export them to a folder to back them up first.)
- Start the Terminal Server Licensing Service.
- Go to the Terminal Server Licensing MMC console and refresh if necessary. Your licensing server will now show that it is activated again.
HKLM\Software\Microsoft\TermServLicensing\Certificates
HKLM\System\CurrentControlSet\services\TermservLicensing\
Parameters\Certificates.000
HKLM\System\CurrentControlSet\services\TermservLicensing\
Parameters\Certificates.001
-n
No comment yet
2 pings
Maria Medina says:
September 26, 2011 at 6:53 am (UTC -5)
Muchas Gracias, excelente solucion de gran ayuda.
techlauve.com - a knowledge base for IT professionals. » Terminal Server Does Not Accept Enough Client Connections says:
April 20, 2011 at 10:52 pm (UTC -5)
[…] growing and needed a few more client access licenses for their Windows 2003 Terminal Server. (see this post for an interesting issue that was encountered.) Once the CALs were installed and activated, all was […]