Article ID: 827119 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
You may find that both local and remote message delivery stops in a mixed site or in an environment that has both Microsoft Exchange Server 5.5 and Microsoft Exchange 2000 Server. No error is logged in the event log.
This problem may occur if you turn on message tracking and Windows Management Instrumentation (WMI) notification on the Exchange 2000 computer. Message tracking is performed by the Exchange 2000 system attendant (Mad.exe). The system attendant receives remote procedure calls (RPC) from the Exchange 2000 Message Transfer Agent (MTA) and from the Exchange 2000 information store process. The system attendant waits for a response from WMI. The problem is caused by a deadlock in WMI; because the system attendant never receives a response from WMI, the system attendant stops responding.
To resolve this problem, obtain the August 2004 Exchange 2000 Server Post-Service Pack 3 update rollup.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
870540Component: System Attendant
(http://support.microsoft.com/kb/870540/ )Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3 update rollup
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Note Because of file dependencies, this hotfix requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
Date Time Version Size File name ------------------------------------------------------------- 29-Oct-2003 04:05 6.0.6528.0 4,370,432 Adcadmin.dll 29-Oct-2003 04:06 6.0.6528.0 69,632 Ccmproxy.dll 29-Oct-2003 04:06 6.0.6528.0 2,109,440 Cdoexm.dll 29-Oct-2003 04:05 6.0.6528.0 8,470,528 Exadmin.dll 29-Oct-2003 04:05 6.0.6528.0 3,850,240 Excluadm.dll 29-Oct-2003 04:06 6.0.6528.0 1,867,776 Exmgmt.exe 29-Oct-2003 03:52 6.0.6528.0 720,896 Exsp.dll 29-Oct-2003 04:06 6.0.6528.0 1,347,584 Exwmi.dll 29-Oct-2003 04:06 6.0.6528.0 73,728 Inproxy.dll 29-Oct-2003 04:06 6.0.6528.0 2,969,600 Mad.exe 29-Oct-2003 04:06 6.0.6528.0 811,008 Madmsg.dll 29-Oct-2003 04:05 6.0.6528.0 4,698,112 Maildsmx.dll 29-Oct-2003 04:06 6.0.6528.0 77,824 Pcproxy.dll 29-Oct-2003 04:06 6.0.6528.0 94,208 X400prox.dll
(http://support.microsoft.com/kb/301378/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about how to troubleshoot Exchange 2000 monitoring and status issues, click the following article number to view the article in the Microsoft Knowledge Base:
310315For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/310315/ )Troubleshooting Exchange 2000 Monitoring and Status
(http://support.microsoft.com/kb/824684/ )Description of the Standard Terminology That Is Used to Describe Microsoft Software Updates