Article ID: 970103 - View products that this article applies to.
On a computer that is running Exchange Server 2003, the Store.exe process causes high CPU usage when a specific message is synchronized with ActiveSync. Therefore, all users who host on the Exchange server cannot access their mailboxes.
Hotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange Server 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Because of file dependencies, this hotfix requires Microsoft Exchange Server 2003 Service Pack 2 to be installed on the server.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/836993/ )How to obtain the latest service packs for Exchange Server 2003
Restart requirementYou do not have to restart the computer after you apply this hotfix. However, the following services are restarted automatically when you apply this hotfix:
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) 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.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 970103 - Last Review: July 21, 2009 - Revision: 1.0