Lsass.exe Stops Working Intermittently on a Domain Controller or Global Catalog (300621)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional SP2
This article was previously published under Q300621 SYMPTOMS
When Lsass.exe is running on a domain controller, Lsass.exe may generate an access violation. The server reboots automatically after the access violation. This problem may occur on a domain controller that is a global catalog and is also the target of the Recipient Update service from Microsoft Exchange 2000 Server. When this problem occurs, the following stack trace appears in the Dr. Watson log.
0d6df464 77d64034 1012cec8 757bb5da 0a991000 RPCRT4!RPC_UUID__ConvertToString+0x3
0d6df46c 757bb5da 0a991000 0d6df54c 00000002 RPCRT4!UuidToStringW+0x33
0d6df550 757bb815 0a9b9538 0a991010 00000000 NTDSA!CheckPermissions+0x69
0d6df598 7579da45 0a9b9538 0a990ff8 00000100 NTDSA!CheckPermissionsAnyClient+0x10f
0d6df680 7579dddf 0a9b9538 0a990ff8 00000100 NTDSA!IsAccessGrantedByObjectTypeList+0x74
0d6df6d0 757c01c8 0a9b9538 0a990ff8 1235ebe0 NTDSA!IsControlAccessGranted+0x8e
0d6df730 757c0524 0a9b4008 0a990b98 0000000d NTDSA!findBestGALInList+0x169
0d6df7c0 7580bf9e 00000000 00000000 0d6df8a4 NTDSA!HTGetGALAndTemplateDNT+0x1db
0d6df8b0 75809451 0a9b4008 00000000 00000003 NTDSA!ABBind_local+0x30c
0d6dfa78 77d445e0 1012b8b8 00000003 100decf4 NTDSA!NspiBind+0x269
0d6dfaa0 77da2579 758091e8 0d6dfab4 00000005 RPCRT4!_Invoke+0x30
0d6dfd10 77da29cc 00000000 00000000 0d6dfdfc RPCRT4!NdrStubCall2+0x63d
0d6dfd2c 77d448bc 0d6dfdfc 000f2bf0 0d6dfdfc RPCRT4!NdrServerCall2+0x17
0d6dfd64 77d447ec 758309d0 0d6dfdfc 0d6dfe40 RPCRT4!DispatchToStubInC+0x84
0d6dfdbc 77d446fe 00000000 00000000 0d6dfe40 RPCRT4!RPC_INTERFACE__DispatchToStubWorker+0x100
0d6dfddc 77d4c6ea 0d6dfdfc 00000000 0d6dfe40 RPCRT4!RPC_INTERFACE__DispatchToStub+0x5e
0d6dfe44 77d4c63d 00000000 100decf0 1012b8b8 RPCRT4!OSF_SCALL__DispatchHelper+0xa4
0d6dfe58 77d4c43e 00000000 00000000 00000001 RPCRT4!OSF_SCALL__DispatchRPCCall+0x115
0d6dfe90 77d4c199 100decd8 00000003 00000000 RPCRT4!OSF_SCALL__ProcessReceivedPDU+0x43
0d6dfeb0 77d4bd7d 100decd8 00000070 00015f90 RPCRT4!OSF_SCALL__BeginRpcCall+0xd0<BR/>
......
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
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
-----------------------------------------------------------------
6/4/2001 05:16p 5.0.2195.3680 501,520 Lsasrv.dll(56-bit)
6/11/2001 06:24p 5.0.2195.3692 355,088 Advapi32.dll
6/11/2001 06:20p 5.0.2195.3680 519,440 Instlsa5.dll
6/11/2001 06:24p 5.0.2195.3698 142,608 Kdcsvc.dll
6/7/2001 11:54a 5.0.2195.3703 209,008 Kerberos.dll
5/29/2001 09:26a 5.0.2195.3649 69,456 Ksecdd.sys
6/4/2001 05:16p 5.0.2195.3680 501,520 Lsasrv.dll
6/4/2001 05:16p 5.0.2195.3680 33,552 Lsass.exe
6/11/2001 06:24p 5.0.2195.3719 909,072 Ntdsa.dll
6/11/2001 06:24p 5.0.2195.3678 382,736 Samsrv.dll
5/29/2001 09:53a 5.0.2195.3649 128,784 Scecli.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.
| Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbDirServices kbfix kbWin2000PreSP3Fix kbWin2000sp3fix KB300621 |
|---|
|