Windows 2000 server cannot contact License Logging service

Domain Controller
Secondary Domain Controller
Windows 2000 Server
I have a Windows Server 2000 machine that is also the secondary domain controller in my domain. The primary domain controller is running Windows Sever 2003. The Windows 2000 server has the following error occurring every fifteen minutes in the event log: 'Replication of license information failed because the License Logging Service on server xxx.xxxxx.local could not be contacted.' followed by a few 'Security policies are propagated with warning. 0x4b8: An extended error has occurred.' errors. My question is two fold - the license logging service is running on my DC. Does it need to be? Everything I have read states that the license logging service is not needed. Second - why can't the secondary DC see it? If I turn off the logging service on the secondary DC will is stop? It should also be noted that the Windows 2000 server is also acting as a terminal server, so nothing that I do can have an affect on that.

Answer Wiki

Thanks. We'll let you know when a new response is added.

the License Logging Service is unreliable.

Unless you are running Windows 2003 SBS, you are fine to disable the service on all servers.

We have a Windows 2003 AD running Exchange 2003, SQL 200 and we have disabled LLS on all servers with absolutely no problems. In fact, there are fewer spurious errors in the server event logs, so our life has been made easier.

License Logging Service (LLS) is a tool that was originally designed to help customers manage licenses for Microsoft server products that are licensed in the Server Client Access License (CAL) model. LLS was introduced with Windows NT Server 3.51. By default, LLS is disabled in Windows Server 2003. Because of original design constraints and evolving license terms and conditions, LLS cannot provide an accurate view of the total number of CALs that are purchased as compared to the total number of CALs that are used on a single server or across the enterprise. The CALs that are reported by LLS may conflict with the interpretation of the End User License Agreement (EULA) and with Product Usage Rights (PUR). LLS will not be included in future versions of the Windows operating system.

For example, when you use the Licensing snap-in (Llsmgr.msc) to view the purchase history of product licenses, the Purchase History window may be blank or inaccurate. However, when you access the purchase history from another server computer, the purchase history may be correct. You can add new licenses, even on computers where the purchase history is inaccurate.

Note This article does not apply to Microsoft Windows Small Business Server 2003. Do not disable the License Logging Service on SBS 2003. If you disable the License Logging Service on SBS 2003, the server will restart every 60 minutes.

Discuss This Question:  

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: