Article ID: 281258
Article Last Modified on 3/1/2007
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q281258
SYMPTOMS
After you specify a default Terminal Services license server, the following event is logged every six hours on a server that is running Terminal Services:
CAUSE
This event is logged every six hours if the normal Terminal Services Licensing discovery process does not succeed. However, this event does not mean that unlicensed clients are unable to connect because the server that is running Terminal Services cannot locate a license server. Even if you set a default Terminal Services license server, the event continues to be logged.
If you are able to verify by testing with a new client that Terminal Services licenses are being issued by this Terminal server, you can safely ignore the errors in the event log of the server because they simply indicate that the Terminal Services license server autodiscovery process failed to locate a license server. Microsoft recommends that you use the DefaultLicenseServer registry value to reduce any issues with the Terminal Server Licensing discovery process.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue does not occur in Microsoft Windows Server 2003.
MORE INFORMATION
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
239107 Establishing preferred Windows 2000 Terminal Services License Server
232520 Description of Terminal Services License Server discovery
279561 How to override the license server discovery process in Windows Server 2003 Terminal Services
Additional query words: DefaultLicenseServer
Keywords: kbprb kbtermserv KB281258
