Access Violation in sbTableGetDSName Causes Global Catalog to Crash

This article was previously published under Q253868
This article has been archived. It is offered "as is" and will no longer be updated.
A Windows 2000 Global Catalog server may stop responding (crash) with the following call stack:
ChildEBP RetAddr  Args to Child013cebb4 757a3c47 000a0043 00000000 015121dc NTDSA!sbTableGetDSName+0x1b4013cebd4 75795315 08e15bf8 08e1e0f0 00000004 NTDSA!IntExtDist+0x7a013cec3c 757a44d6 08e15bf8 00000002 00000040 NTDSA!dbGetMultipleAttsLinkHelp+0xc9013cf4a8 757a3ecb 08e15bf8 00000031 08e175f4 NTDSA!DBGetMultipleAtts+0x2d9013cf5e4 7581581c 08e175f4 00000000 013cf668 NTDSA!GetEntInf+0x68e013cf6d8 75815a93 08e10650 0fccdb70 013cf8ac NTDSA!GetSrowSet+0x308013cf70c 75819a89 08e10650 00000000 000035b4 NTDSA!ABGetProps_local+0x47013cf8e0 77d45178 016ce090 00000000 0fccdb70 NTDSA!NspiGetProps+0x174013cf908 77da1586 7581981f 013cfab4 00000005 RPCRT4!Invoke+0x30013cfd10 77da1937 00000000 00000000 013cfdfc RPCRT4!NdrStubCall2+0x63d013cfd2c 77d453e2 013cfdfc 00115140 013cfdfc RPCRT4!NdrServerCall2+0x17013cfd64 77d452ef 75795c19 013cfdfc 013cfe40 RPCRT4!DispatchToStubInC+0x84013cfdbc 77d45215 00000009 00000000 013cfe40 RPCRT4!RPC_INTERFACE__DispatchToStubWorker+0x100013cfddc 77d4fa80 013cfdfc 00000000 013cfe40 RPCRT4!RPC_INTERFACE__DispatchToStub+0x5e013cfe44 77d4f9d7 00000000 0fccdb58 0fc3ee48 RPCRT4!OSF_SCALL__DispatchHelper+0xa4013cfe58 77d4f779 00000000 00000009 00000001 RPCRT4!OSF_SCALL__DispatchRPCCall+0x115013cfe90 77d4f4d8 0fccdb40 00000003 00000009 RPCRT4!OSF_SCALL__ProcessReceivedPDU+0x43013cfeb0 77d4f0bc 0fccdb40 00000070 00015f90 RPCRT4!OSF_SCALL__BeginRpcCall+0xd0013cff10 77d4f033 00000000 0fccdb40 00000070 RPCRT4!OSF_SCONNECTION__ProcessReceiveComplete+0x235013cff20 77d5bb62 00089ec0 0000000c 00000000 RPCRT4!ProcessConnectionServerReceivedEvent+0x1b					
This behavior is caused by an empty LegacyExchangeDN property that was passed to the Global Catalog during a lookup for an object.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Windows 2000 now adds checks to ensure that it does not crash in this instance.

NOTE: To view the version, right-click the file in Windows Explorer, click Properties on the menu that appears, and then click the Version tab.

The following files are available for download from the MicrosoftDownload Center:
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
Microsoft has confirmed that this is a problem in Microsoft Windows 2000. This problem was first corrected in Windows 2000 Service Pack 1.
For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Article ID: 253868 - Last Review: 10/20/2013 17:19:47 - Revision: 3.7

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbdownload kbbug kbfix kbgraphxlinkcritical kbqfe kbwin2000sp1fix KB253868