Microsoft KB Archive/918279

= An event script that uses CDO version 1.21 does not run as expected in an Exchange Server 2003 environment =

Article ID: 918279

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition

-





SYMPTOMS
Consider the following scenario. You try to run an event script that uses Collaboration Data Objects (CDO) version 1.21. Additionally, you are trying to run this event script in a Microsoft Exchange Server 2003 environment in which one of the following conditions is true:  You are running Microsoft Exchange Server 2003 Service Pack 2 (SP2). You have installed the hotfix that is described in the following Microsoft Knowledge Base article:

894470 A meeting is removed from your Outlook Calendar after you accept the meeting and then delete the accepted meeting request



In this scenario, the script does not run in Exchange Server 2003 as expected. Additionally, the following event is logged to the Application log: Event Type: Error

Event Source: MSExchangeES

Event Category: General

Event ID: 11

Date:

Time:

Computer:

Description: A fatal error (0x8000ffff) occurred in an IExchangeEventSink while processing message [Subject = &quot;xxxx&quot;].

For more information, see Help and Support Center at http://support.microsoft.com.



RESOLUTION
A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

Hotfix information
This P1 may not contain all the files that you must have to fully update a product to the latest build. This P1 contains only the files that you must have to correct the issues that are listed in this article.

Prerequisites
The following list contains prerequisites for the hotfix:
 * You must have Microsoft Exchange Server 2003 Service Pack 2 (SP2) installed before you install the hotfix package.

Restart requirement
You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix is not replaced by any later hotfix.

File information
The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.



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



MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

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

817903 New naming schema for Exchange Server software update packages

Additional query words: XADM

Keywords: kbhotfixserver kbqfe kbfix kbbug kbpubtypekc KB918279

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.