Article ID: 151669
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange Server 4.0 Standard Edition
- Microsoft Exchange Server 5.0 Standard Edition
This article was previously published under Q151669
SYMPTOMS
The Microsoft Mail Connector interchange (MSMI) stops processing mail. This can be evidenced by the following symptoms:
A backlog builds in the message transfer agent's (MTA's) MSMI queue.
P1 files build up in Exchsrvr\Connect\Msmcon\Maildata\P1.
In Performance Monitor, observe the thread object"% processor time" counter for all MT.EXE threads. All threads above number 3 except one (typically number 6 on a singleCPU computer) will show no processor utilization (threads 0 through 3 typically show no processor utilization except during startup, shutdown, or thread and data refresh).
The following MSMI event messages are repeatedly logged in pairs:
CAUSE
The MSMI's outbound processing thread(s) have raised a handled exception while "owning" a thread synchronization object (mutex) that other threads are waiting for. While the exception is handled, the mutex is not properly released, resulting in "blocked" execution of the other threads.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 4.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Keywords: kbbug kbfix kbusage KB151669
