Microsoft KB Archive/938650

= A meeting update message or a meeting cancellation message from an Exchange 2003 user is not delivered to an Exchange 2007 user =

Article ID: 938650

Article Last Modified on 10/25/2007

-

APPLIES TO


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

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
Consider the following scenario. A Microsoft Exchange Server 2003 organization and a Microsoft Exchange Server 2007 organization exchange communications by using SMTP. An Exchange 2003 user organizes a meeting and then sends a meeting request to an Exchange 2007 user. Additionally, the Exchange 2007 user accepts the meeting request. Then, the meeting organizer uses Microsoft Office Outlook to send a meeting update message or a meeting cancellation message to the Exchange 2007 user.

In this scenario, the meeting update message or the meeting cancellation message is not delivered to the Exchange 2007 user. Instead, the meeting update message or the meeting cancellation message goes into the SMTP retry queue. If an administrator tries to open the message in the Exchange System Manager console, the administrator may receive the following error message:

Unable to open for delivery

Additionally, if the diagnostics logging of the MSExchangeTransport component is set to maximum, the following warning is logged: Event Type: Warning

Event Source: MSExchangeTransport

Event Category: Exchange Store Driver

Event ID: 327

Description:

The following call : EcGetMime to the store failed. Error code : -2147467259. MDB :. FID :. MID :. File :.



CAUSE
When an Exchange 2007 user accepts a meeting request from an Exchange 2003 user, the X-MICROSOFT-CDO-ATTENDEE-CRITICAL-CHANGE attribute is missed. In the Outlook client, if the X-MICROSOFT-CDO-ATTENDEE- CRITICAL-CHANGE attribute is missing, the PR_RECIPIENT_TRACKSTATUS_TIME property is set to &quot;1/1/1601 00:00:00 AM.&quot; When the Exchange 2003 user tries to send an update of the meeting request or a cancellation of the meeting request, the value of the PR_RECIPIENT_TRACKSTATUS_TIME property cannot be successfully converted from the MAPI format to the MIME format by using the VariantTimeToSystemTime function.



RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

After you install the hotfix, you must create the FixRecipientTrackStatusTime register entry to enable the hotfix. To do this, follow these steps:  Click Start, click Run, type Regedit, and then click OK. Locate the following registry subkey:

 On the Edit menu, point to New, and then click DWORD Value. In the details pane, type FixRecipientTrackStatusTime for the new value, and then press ENTER. Right-click FixRecipientTrackStatusTime, and then click Modify. In the Edit DWORD Value dialog box, click Decimal under Base.</li> In the Value data box, type 1, and then click OK.</li> Exit Registry Editor.</li></ol>

Hotfix information
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

Prerequisites
Microsoft Exchange Server 2003 Service Pack 2 (SP2) must be installed before you apply this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

836993 How to obtain the latest service packs for Exchange Server 2003

Restart requirement
You do not have to restart the computer after you apply this hotfix. However, the following services are automatically restarted when you apply this hotfix:
 * The Microsoft Exchange System Attendant service
 * The Internet Information Services (IIS) Admin Service and all dependent services

Hotfix replacement information
This hotfix does not replace a previously released 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.

<div class="status_section">

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

Keywords: kbexchcoexistmigration kbexchtransport kbexpertiseinter kbqfe kbhotfixserver KB938650

-

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

© Microsoft Corporation. All rights reserved.