XADM: Event IDs 8217, 8206, and 8230 Appear Repeatedly in the Application Event Log

On your Exchange 2000 computer, one or more events that are similar to the following events repeatedly appear in the application event log of Event Viewer:

Event Type: Error
Event Source: EXCDO
Event Category: General
Event ID: 8217
Date: date
Time: time
User: N/A
Computer: Servername
Description: The processing of the recurring appointment with the subject "Updated: 2:30...Meeting" in mailbox: username failed with error code 0x8000ffff. This appointment will not be visible in the Web client or other non-MAPI client.

Event Type: Error
Event Source: EXCDO
Event Category: General
Event ID: 8206
Date: date
Time: time
User: N/A
Computer: Servername
Description: Calendaring agent failed with error code 0x8004010f while saving appointment.
Data:
0000: 48 72 53 61 76 69 6e 67 HrSaving
0008: 41 70 70 74 3a 3a 48 72 Appt::Hr
0010: 43 68 65 63 6b 50 61 74 CheckPat
0018: 74 65 72 6e 20 66 61 69 tern fai
0020: 6c 65 64 2e 20 4d 61 69 led. Mai
0028: 6c 62 6f 78 3a 72 61 6e lbox:

Event Type: Warning
Event Source: EXCDO
Event Category: General
Event ID: 8230
Date: date
Time: time
User: N/A
Computer: Servername
Description: 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.

Additionally, when recipients who are running Microsoft Outlook create appointments, they may not be able to view the appointments by using Outlook Web Access (OWA).

This problem occurs because of an unsuccessful Multipurpose Internet Mail Extensions (MIME) conversion in the Exchange Server Imail component, and occurs when the appointment to be converted has a blank e-mail address. IMAIL does not correctly test for blank e-mail address information when it converts the appointment.

Cumulative Rollup Information

To resolve this problem, obtain the September 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Component: Imail

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.