This article was previously published under Q254230
This article has been archived. It is offered "as is" and will no longer be updated.
Under certain circumstances, when you are running Isinteg in Fix mode against an information store, appointments may become unusable for users. The appointments either are still there but become unusable because of randomly modified start and end times or they are deleted from the user's calendar. A typical command line which may cause this issue is the following one:
When you are running Isinteg against an information store in Fix mode, it can remove MAPI properties from the JET property tag arrays of appointments without further checking if these properties are still required for proper appointment access. As a result, the affected appointments become unusable because of randomly modified start and end times or they can even be deleted from the user's calendar.
Typically, these remove operations are logged in the Isinteg.pri or Isinteg.pub file in the following way:
Microsoft Exchange Information Store Integrity Checker v5.5.2448.8Copyright (c) 1986-1997 Microsoft Corp. All rights reserved.Started: 02/11/00 08:15:32Server name: garfield.pss.microsoft,deStore path: C:\exchsrvr\MDBDATA\PRIV.EDBStore size: 3153920 bytesOutput log: d:\isinteg\isinteg-priv.logCheck mode: check and fixOptions: -pri -fix -detailed -verbose -l d:\isinteg\isinteg-priv.log -test message No reference count testsStarting test 1 of 1, 'Message'Warning: Message 13 (Inid=00BB-000000000349): Prop count does not match between ptagMsgPropTagArray(67B20102) and JET columnsWarning: Prop 806A0040 is in ptagArray but not in a JET column.Fix: Message 13 (Inid=00BB-000000000349): Fixed the ptagMsgPropTagArray(67B20102) with correct props.Warning: Message 14 (Inid=00BB-00000000054D): Prop count does not match between ptagMsgPropTagArray(67B20102) and JET columnsWarning: Prop 806A0040 is in ptagArray but not in a JET column.Fix: Message 14 (Inid=00BB-00000000054D): Fixed the ptagMsgPropTagArray(67B20102) with correct props.Warning: Message 15 (Inid=00BB-000000000551): Prop count does not match between ptagMsgPropTagArray(67B20102) and JET columnsWarning: Prop 806A0040 is in ptagArray but not in a JET column.Fix: Message 15 (Inid=00BB-000000000551): Fixed the ptagMsgPropTagArray(67B20102) with correct props.Finished Message, number of rows = 16. Time: 0h:1m:20s, number of warnings = 6, number of fixes = 3. . . . . SUMMARY . . . . .Total number of tests : 1Total number of warnings : 6Total number of errors : 0Total number of fixes : 3Total time : 0h:1m:20s
In this scenario, the named property, 806A0040, where 806A represents the property's ID while 0040 represents the property's type (which is PT_SYSTIME here), is removed from the affected appointments. The ID 806A may differ for other stores because it's a named property. In terms of MAPI, named properties may be uniquely referenced either by a name or by an ID. This issue causes Isinteg to delete every appointment's named property that maps to the ID 33293, which is the ID that maps to the appointment's start time.
To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
191014 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
The following files are available for download from the MicrosoftDownload Center:
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5 SP2 and 5.5 SP3. This problem was first corrected in Exchange Server 5.5 Service Pack 4.
To work properly, the Isinteg fix also requires a store fix with a build number of 5.5.2651.85 or later.
Note When you start this version of the information store, the information store databases are automatically upgraded to a new format. After the databases have been upgraded, you can restore an earlier version of the Store.exe file on the server, but only if it is version 5.5.2651.32 or later. If you restore a Store.exe file earlier than version 5.5.2651.32 after the database has been upgraded, you are no longer able to start the information store. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
244976 XADM: Event ID 1197 and 1005 When Starting the Information Store
To go to a previous build of the Store.exe file:
Stop the information store.
Replace the current build of the Store.exe file with a build prior to 5.5.2651.32.
Restore from an online backup of a database before you install the hotfix on server.
Restart the services and allow transaction logs to be replayed against the older database.