Article ID: 296936 - Last Review: November 21, 2006 - Revision: 3.0 The Licensing Service (Llssrv.exe) changes from started to starting and does not respond to SCMThis article was previously published under Q296936 SYMPTOMS
When you view the services that are running on the Windows 2000 domain controller that hosts the PDC emulator, the Licensing service (Llssrv.exe) may appear to be starting. If you then try to stop the service, the
request may not work and Service Control Manager (SCM) may be unable to stop the service. The only way to stop the service is to reboot into Safe mode, disable the service, and start Windows again. When this behavior occurs, you may also receive the following error message:
Could not start the License Logging Service on local computer. The service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists, see your system administrator.
CAUSE
This problem can occur when Llssrv.exe goes into this mode during replication with other domain controllers. The service is set to start and the code goes through a series of checks before the service starts again. One of these checks fails to return an answer to Llssrv.exe which is waiting for the answer, and the service stops responding to the SCM.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
260910
(http://support.microsoft.com/kb/260910/
)
How to obtain the latest Windows 2000 service pack
The English version of this fix should have the following file attributes or later:Date Time Version Size File name ------------------------------------------------------------ 8/6/2001 03:00p 5.0.2195.3831 48,912 Llsrpc.dll 8/1/2001 11:54a 5.0.2195.4014 82,704 Llssrv.exe 8/6/2001 03:00p 5.0.2195.3881 940,816 Ole32.dll 8/6/2001 03:00p 5.0.2195.3865 427,792 Rpcrt4.dll 8/6/2001 03:00p 5.0.2195.3881 185,104 Rpcss.dll STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3. | Article Translations
|
Back to the top
