XADM: The System Attendant Silently Stops Running (313961)
The information in this article applies to:
- Microsoft Exchange 2000 Server
This article was previously published under Q313961 SYMPTOMS
On a highly stressed Exchange 2000 computer, the system attendant (Mad.exe) may silently stop running. No crash dump file is generated, and no event ID error message is logged in the event logs.
However, if a debugger is attached to Mad.exe, the process stops responding in the debugger with the following stack trace:
ChildEBP RetAddr Args to Child
0bcdedcc 78008fa5 e06d7363 00000001 00000003 KERNEL32!RaiseException+0x56
0bcdee0c 60ab691f 0bcdee20 60abac94 00000000 MSVCRT!_CxxThrowException+0x34
0bcdee5c 60ab6b58 0ab4e0e0 60ab8f0d 00000001 DSPROXY!std__vector<CNSPTarget,std__allocator<CNSPTarget> >___Xran+0x62
0bcdee64 60ab8f0d 00000001 0000098c 00000000 DSPROXY!std__vector<CNSPTarget,std__allocator<CNSPTarget> >__at+0x22
0bcdee98 60ab61c9 0000098c 00000000 00000002 DSPROXY!CNSPTargetList__ConnectTarget+0xa4
0bcdeef8 60ab41c5 00000c98 00000000 0000000f DSPROXY!_Worker__AddClient+0xe7
0bcdff80 7800a3c0 00000001 0000000f 0000000f DSPROXY!ListenBody+0x357
0bcdffb4 77e8758a 0ab52a60 0000000f 0000000f MSVCRT!_beginthreadex+0xca
0bcdffec 00000000 7800a361 0ab52a60 00000000 KERNEL32!BaseThreadStart+0x52
CAUSE
This problem may occur if a Named Service Provider Interface (NSPI) and an RFR client access DSPROXY at the same time, shortly after a domain controller that Exchange 2000 uses shuts down. The DSProxy may cause an unhandled exception that can silently stop the system attendant (Mad.exe).
RESOLUTIONTo resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix has the following file attributes or later:
Component: DSProxy
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.
| Modification Type: | Minor | Last Reviewed: | 6/5/2003 |
|---|
| Keywords: | kbbug kbExchange2000preSP3fix kbExchange2000sp3fix kbfix KB313961 |
|---|
|