Article ID: 251409 - View products that this article applies to.
This article was previously published under Q251409
This article is a consolidation of the following previously available articles: 240202, 251409
In Microsoft Exchange Server 5.5 and in earlier versions of Exchange Server, you must run the isinteg -patch command after you restore a database from an offline backup. However, you do not have to run the isinteg -patch command in Exchange 2000 Server or in Exchange Server 2003. During startup, Exchange 2000 or Exchange 2003 validates a globally unique identifier (GUID) in the information store with an entry stored in Windows 2000 Active Directory. The Exchange 2000 or Exchange 2003 information store cannot be started if these two sets of GUIDs do not match. Mismatches can occur if the information store has been restored from an offline backup. When these GUIDs do not match, a "patch" is performed automatically by Store.exe when the information store starts up.
For the patch operation to complete successfully, the database must be set to allow being overwritten by a restore procedure. To enable this setting, click to select the This database can be overwritten by a restore check box in the database properties in Exchange System Manager.
CN=Database Name,CN=Storage Group Name,CN=InformationStore,CN=Server Name,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=Org Name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain Name,DC=comIf this check box is not selected (that is, if this value is stored as FALSE in Active Directory), and this information store requires a patch operation to start, this information store will not start, and the following event is written to the Event Viewer application log:
Event ID: 1087
Event ID: 9524
After Store.exe performs a patch against a database, clients logging on to that database may encounter a slight slowdown when loading the client for the first time since the patch was performed. When a patch is performed, it resets the per-user read/unread GUID on this store, and forces all clients to re-load their per-user read information from this database.
Article ID: 251409 - Last Review: October 25, 2007 - Revision: 3.4
Contact us for more help