• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1026
  • Last Modified:

event id 213 ?

I have recently upgraded my windows 2000 domain to windows 2003 and i have changed the domain name, after this issue and after i moved my clients from the old domain to the new one, i always recive the following error on somw windows 2000 clients:
Event Type:       Warning

Event Source:    LicenseService

Event Category: None

Event ID:           213

Date:                11/21/2006

Time:                2:24:47 AM

User:                N/A

Computer:         computer_name


Replication of license information failed because the License Logging Service on server \\domain_name could not be contacted.

2 Solutions
I would remove and add them back in again, since they may still be trying to contact the old license server.

Other option is to turn off the License Service ( I think ) locally.

Did you check the MS site and also see the MS site


and search the the Event ID 213

you changed the domain name.....you will need to reinstall the licence server i beleive
Set the service "License service" to start automatically and pushed the Start Button. On the Server where the event 213 appeared, I restart the "License service". After this, sometimes problem will go away.

Here is what Microsoft says in detail about this issue:

The event 213 you saw is recorded by the License Logging Service. 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. Because of original design constraints and evolving license terms and conditions, LLS cannot provide an accurate view of the total number of CALs. Sometimes, even though you have purchased an ample number of licenses, you may find that there are licensing events recorded in the Event Viewer stating that you are out of licenses. For the reason above, by default LLS is disabled in Windows Server 2003 and future products. In other words, the events reported by LLS are not accurate and you can safely disregard them. To prevent these events from being recorded, you can turn off the licensing service on all domain controllers. For more information about LLS, you can refer to the following Microsoft Knowledge Base articles: M824196 and M316631.
Therefore, you actually do not need to worry about these licensing events and they will not have any impact on your domain. If you still prefer enabling the LLS service, we can try resetting the license manager information to solve this issue. This derives from our previous experience and it will work in most cases. To do this, follow these steps:
1. Click Start -> Run, type "net stop licenseservice" (without the quotation marks) and press Enter to stop the License Logging service.
2. Delete or rename the following files on the Domain Controller:
- Cpl.cfg, which contains all of your purchase history and is located in %Systemroot%\System32.
- Llsuser.lls, which contains the user information on number of connections, located in %Systemroot%\System32\Lls.
- Llsmap.lls, which contains License group information, also located in %Systemroot%\System32\Lls.
3. Click Start -> Run, type "net start licenseservice" (without the quotation marks) and press Enter to restart the License Logging service.
4. Manually re-add the appropriate license information. See M185953 for more details on these steps".

Let me know if you need more information and I will get you more on this.  Hope it helps!


License logging service on APDC01
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now