An inconsistency was detected in %2: %3. The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.

Details
Product: Exchange
Event ID: 8230
Source: EXCDO
Version: 6.5.7596.0
Message: An inconsistency was detected in %2: %3. The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.
   
Explanation

This Warning event is logged when a problem with a Calendar item is detected. This indicates that Microsoft® Exchange Server has detected data corruption and is trying to rebuild the calendar data for Web client viewing.

Calendar item corruption is usually caused when file system-based antivirus software scans the Exchange Installable File System (IFS) drive. By default, the Exchange IFS drive is drive M. Corruption can also occur when you try to back up drive M. The following articles in the Microsoft Knowledge Base may apply:

Other events in the Application log may give you more information about why this event was logged and where the corruption exists. The following events may help you discover the underlying cause of this error:

  • EXCDO Event 8199

  • EXCDO Event 8206

  • EXCDO Event 8206

  • EXCDO Event 8206

  • EXCDO Event 8207

  • EXCDO Event 8208

  • EXCDO Event 8217

  • EXCDO Event 8219

  • EXCDO Event 8241

  • EXCDO Event 8243

  • EXCDO Event 8255

  • EXCDO Event 8263

   
User Action

To resolve this error, try one or more of the following:

  • After Exchange rebuilds the data, verify whether Exchange was able to correctly display the calendar data on the Web client.

  • In Event Viewer, examine the Application log for relevant EXCDO source event messages. The descriptions of these related events may provide additional information about the underlying issue. For more information about the cause and resolution of these related events, click the “http://www.microsoft.com/contentredirect.asp” URL at the end of the description of each related event. Alternatively, you can search for more information about these related events at the Events and Errors Message Center Web site.

  • Make sure that a file system-based antivirus program running on the Exchange Server is not scanning the Exchange IFS drive (M drive). Additionally, make sure that any backup software that is used is not backing up the Exchange IFS drive. If the corruption cannot be isolated or corrected, restore the data from a backup. For more information, see the Microsoft Knowledge Base articles referenced earlier in this article.

Related:

Leave a Reply