XFOR: Corrupted Message Causes CCMC to Stop Inbound Traffic and Engage 90 Percent of CPUID: Q234745
|
A corrupted Lotus cc:Mail message (.ccm) file may cause the Microsoft Exchange Connector for Lotus cc:Mail to use up to 90 percent of the CPU and subsequently stop the processing of all inbound mail messages.
The 'Contents:' field is mandatory in a cc:Mail message. If the cc:Mail message is missing this field because of corruption in the body, the cc:Mail Connector loops indefinitely.
A supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack
that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support Services
phone numbers and information on support costs, please go to the following
address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later:
File name | Version |
---|---|
Ccmc.exe | 2623.0 |
Ccmsg.dll | 2623.0 |
Q154871 Determining If You Are Eligible for No-Charge Technical Support
You can remove the corrupted cc:Mail message by stopping the Microsoft Exchange cc:Mail Connector service, and then deleting the stuck message in the Exchsrvr\Ccmcdata\Export folder.
Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5.
Additional query words: ccmail, stuck message, high CPU, 100%
Keywords : exc55
Version : winnt:5.5
Platform : winnt
Issue type : kbbug
Last Reviewed: July 1, 1999