Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
An inconsistency was detected in <username>@<domain>.com: /Calendar/Appointment.EML. 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.
|English: Request a translation of the event description in plain English.|
I had this problem on Exchange 2007 sp1 rollup 2. The issue was a bad appointment with one user. Deleted and recreated the appointment and the 8230 errors stopped.
See ME896105 for a hotfix applicable to Microsoft Exchange 2000.
See ME556073 and ME947014 for additional information about this event.
From a newsgroup post: "This problem is an unfortunate result of scanning the M: drive using file-level Antivirus software. The problem is really that items are changed when they are scanned. Because of that, the Information Store and/or Outlook client cannot read them properly anymore. There were two hotfixes that MS came out with to enable databases that were scanned like this to be seen again through Outlook properly:
1. Install Exchange 2000 SP2.
2. Install Outlook patch on your clients - Outlook 2000 and 2002.
Related articles are ME302456, ME302849, and ME302852".
As per MSEX2K3DB: "This warning event is logged when a problem with a Calendar item is detected. This indicates that Exchange detected data corruption and is trying to rebuild the calendaring data for Web client viewing.
The most common cause of calendar item corruption is scanning the Exchange Installable File System (IFS) drive with file system-based antivirus software. By default, the Exchange IFS drive is drive M. Corruption can also occur when you try to back up drive M". Read MSEX2K3DB for further information on the problem.
See ME821293 for additional information on this event.
ME310440 shows you how to solve this problem.
|Private comment: Subscribers only. See example of private comment|
|Links: ME302456, ME302849, ME302852, ME310440, ME556073, ME821293, ME896105, ME947014, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated