This article was previously published under Q181410
This article has been archived. It is offered "as is" and will no longer be updated.
The Microsoft Exchange Server Information Store service stopsresponding with 90 to 100 percent CPU time. Client computers may also stopresponding. If this problem occurs, the information store may also stop running when the service tries to quit.
Performance Monitor shows a single thread of the information store that appears to be continuously runningnear 100 percent CPU usage.
This problem occurs because the information store tried to decode a corrupt message from itscompressed RTF form into an Exchange Server message body form. The current decodelogic does not handle compressed RTF corruption of this form and enteredinto a tight loop.
Microsoft has confirmed this to be a problem in Microsoft Exchange Serverversions 5.0.
A supported fix is now available, but has not been fully regression-testedand should be applied only to systems experiencing this specific problem.Unless you are severely impacted by this specific problem, Microsoftrecommends that you wait for the next Service Pack that contains this fix.Contact Microsoft Technical Support for more information.
This fix has been posted to the following Internet location:
Microsoft has confirmed this to be a problem in Microsoft Exchange Serverversion 5.5. This problem has been corrected in the latest U.S. ServicePack for Microsoft Exchange Server version 5.5. For information onobtaining the Service Pack, query on the following word in the MicrosoftKnowledge Base (without the spaces):
S E R V P A C K
To view this in the Windows NT Performance Monitor (Perfmon.exe), followthese steps:
On the Edit menu, click Add To Chart.
In the Object list, click Thread.
In the Counter list, click %Processor Time.
In the Instance list, click all values that contain "store."
You can now use Perfmon.exe to view the thread running at high CPU usage.