Fileserver: Event 213

[cdrexler 10]

hallo,

 

folgendes problem:

 

win2k server sp4 (up to date)

 

im fileserver tauchen nach 1-2 tagen nach einem reboot immer warnungen event 213 auf.

 

Event Type: Warning

Event Source: LicenseService

Event Category: None

Event ID: 213

Description:

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

 

wenn jetzt ein user eine grössere datei auf den server kompiert, geht die performance aller clients die ein mapping auf den fileserver haben in die knie.

 

der fileserver ist der einzige server, der warnungen solcher art ausspuckt.

alle anderen server laufen normal.

 

die angemeckerten dienste laufen aber auf dem DC

 

 

habe folgendes in der ms-kb gefunden... ist aber ein fix für win nt.

 

http://support.microsoft.com/default.aspx?scid=kb;en-us;247794

 

 

weiss jemand rat?

[wirtnix 10]

hier ein posting von eventid.net

 

(leider in englisch)

 

I received the following information from the Microsoft support team: "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".