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


The information in this article applies to:

  • Microsoft Exchange 2000 Server

SYMPTOMS

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).

CAUSE

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.

RESOLUTION

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:

824282 September 2003 Exchange 2000 Server Post-Service Pack 3 Rollup

Hotfix Information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Exchange 2000 Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
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. 
  Date         Time   Version            Size    File name
   --------------------------------------------------------------
   19-Jun-2003  00:18  6.0.6477.0      3,915,776  Cdoex.dll        
   19-Jun-2003  00:13  6.0.6477.0        851,968  Davex.dll        
   19-Jun-2003  00:13  6.0.6477.0         53,248  Davexpc.dll      
   19-Jun-2003  00:10  6.0.6477.0        577,536  Dsaccess.dll     
   18-Jun-2003  23:18  6.0.6477.0        184,320  Dscmsg.dll       
   19-Jun-2003  00:19  6.0.6477.0      3,575,808  Excdo.dll
   19-Jun-2003  00:10  6.0.6477.0        258,048  Exmime.dll
   19-Jun-2003  00:13  6.0.6477.0        143,360  Exodbesh.dll
   19-Jun-2003  00:13  6.0.6477.0         57,344  Exodbpc.dll
   19-Jun-2003  00:13  6.0.6477.0        200,704  Exodbprx.dll
   19-Jun-2003  00:13  6.0.6477.0      2,174,976  Exoledb.dll      
   19-Jun-2003  00:07  6.0.6477.0         81,920  Exosal.dll       
   19-Jun-2003  00:13  6.0.6477.0        307,200  Exprox.dll       
   18-Jun-2003  23:21  6.0.6477.0        143,360  Exschema.exe          
   18-Jun-2003  23:23  6.0.6477.0        671,744  Exwform.dll      
   18-Jun-2003  23:10  6.0.6477.0         49,152  Mdbevent.dll     
   18-Jun-2003  23:31  6.0.6477.0      2,285,568  Mdbmsg.dll       
   18-Jun-2003  23:12  6.0.6477.0         32,768  Mdbrole.dll      
   19-Jun-2003  00:11  6.0.6477.0         24,576  Mdbtask.dll      
   19-Jun-2003  00:09  6.0.6477.0      4,648,960  Store.exe
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:

301378 How to Obtain the Latest Exchange 2000 Server Service Pack

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Modification Type:MinorLast Reviewed:10/3/2005
Keywords:kbHotfixServer kbQFE kbQFE kbfix kbExchange2000preSP4fix kbbug KB821293 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.