OL2000: Unknown Error When Accepting a Meeting Request (280813)

SYMPTOMS

When you attempt to accept a meeting request, you may receive the following error message:

Unknown Error

This behavior occurs under the following conditions:

A custom meeting request form is being used.
The AutoPreview feature in Outlook in the Calendar folder is currently enabled, or was previously enabled.
The message body of the meeting request is empty.

CAUSE

This issue can occur because when a custom form is used, Outlook recognizes that it is working with a template, and loads all the properties from the original meeting request. Then Outlook dirties those properties in the new appointment that is generated. One of the properties that is dirtied is the PR_RTF_COMPRESSED property. When you accept a meeting request, Outlook generates the appointment item from the original meeting request. Because the PR_RTF_COMPRESSED property was previously marked dirty, the server expects more data to be written to the property. However, Outlook determines that nothing in the body has changed, and therefore only writes a header to the RTF stream. In addition, because the AutoPreview feature in the Calendar folder is enabled or was previously enabled, the server tries to promote the body to make the body available to Outlook. Because the body is incomplete, the server returns MAPI_E_CORRUPT_DATA.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Office 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

276367 OFF2000: How to Obtain the Latest Office 2000 Service Pack

The English version of this fix should have the following file attributes or later:

   Date      Time       Version          Size    File name   Platform
   -------------------------------------------------------------
   11/16/00 2:10 AM   9.00.0000.4715   5,324,850 Outllib.dll  x86

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Office 2000 Service Pack 3 (SP-3).