Article ID: 891005
Article Last Modified on 10/25/2007
APPLIES TO
- Microsoft Exchange Server 2003 Enterprise Edition
- Microsoft Exchange Server 2003 Standard Edition
SYMPTOMS
When you use Quest Exchange Migration Wizard or Quest Migration Manager to synchronize information from a computer that is running Microsoft Exchange Server 2003, the Microsoft Exchange Information Store service unexpectedly quits. In this scenario, you may experience one or both of the following symptoms:
The following event is logged in the Application log:
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date:date
Time:time
Type: Error
User: N/A
Computer:computername
Description: The Microsoft Exchange Information Store service terminated unexpectedly. It has done this 1 time(s).- If you try to move the particular folder where you experience this problem to another location by using the Exchange Tasks Wizard, you receive the following error message:
For the Microsoft Exchange 2000 Server version of this hotfix, see the following Microsoft Knowledge Base article:
892208 The Microsoft Exchange Information Store service unexpectedly quits when you synchronize information from a computer that is running Microsoft Exchange 2000 Server
CAUSE
This problem occurs if the following conditions are true:
- You run a program that uses the IExchangeExportChanges::Synchronize method to retrieve hierarchy changes from a mailbox or from a public folder in Exchange 2003.
Note Quest Exchange Migration Wizard and Quest Migration Manager use this method. The IExchangeExportChanges::Synchronize method is an open interface that we recommend for incremental change synchronization.
- The mailbox or public folder contains a folder that is missing some MAPI properties.
This problem may occur in a scenario where a folder is copied to a public folder and then replicated to another Exchange computer. When this folder is replicated, only some of the rules that it contains are replicated to the other Exchange computer. Because this folder is missing certain MAPI properties, the Microsoft Exchange Information Store service does not process the folder correctly. Therefore, when you try to programmatically obtain hierarchy changes from the mailbox or from the public folder where this folder is stored, the Microsoft Exchange Information Store service quits.
Note You may also experience this problem with other programs that use the IExchangeExportChanges::Synchronize method to synchronize data with Exchange 2003.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
This hotfix requires Exchange Server 2003 Service Pack 1 (SP1). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
836993 How to obtain the latest service packs for Exchange Server 2003
Restart requirement
You do not have to restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The 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 item in Control Panel.
Date Time Version Size File name ----------------------------------------------------------- 13-Jan-2005 03:44 6.5.7232.68 295,936 Isinteg.exe 13-Jan-2005 03:57 6.5.7232.68 3,261,952 Mdbmsg.dll 08-Oct-2004 02:12 3,304 Redir.asp 13-Jan-2005 04:31 6.5.7232.68 5,166,080 Store.exe
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information about the naming schema for Exchange Server software updates, click the following article number to view the article in the Microsoft Knowledge Base:
817903 New naming schema for Exchange Server software update packages
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Additional query words: XADM sync crash migrate mig migwiz
Keywords: kbqfe kbhotfixserver kbfix kbbug KB891005
