Open Software Solutions

In a Microsoft Exchange Server 2007 Service Pack 1 (SP1) environment, an Exchange Server 2007 mailbox server randomly generates many transaction logs. Additionally, one of the following event errors is repeated in the Application event log for the same user:

Event ID : 8230
Raw Event ID : 8230
Category : General
Source : EXCDO
Type : Warning
Message : An inconsistency was detected in <someone’s address>: </calendar/xxx/xxx.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.

Event ID : 8264
Raw Event ID : 8264
Category : General
Source : EXCDO
Type : Warning
Message : The recurring appointment expansion in mailbox <someone’s address> has taken too long. The free/busy information for this calendar may be inaccurate. This may be the result of many very old recurring appointments. To correct this, please remove them or change their start date to a more recent date.

Back to the top

To resolve this problem, install Update Rollup 1 for Exchange Server 2007 Service Pack 1. For more information about Update Rollup 1 for Exchange Server 2007 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

To work around this problem, remove the looping message from the MAPIDelivery Retry queue. Additionally, delete the original calendar item that is described in event ID 8230.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

For more information about MAPIDelivery retry queue, visit the following Microsoft Web site:

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

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:

Back to the top