Article ID: 938650 - View products that this article applies to.
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:
Additionally, if the diagnostics logging of the MSExchangeTransport component is set to maximum, the following warning is logged:
Unable to open for delivery
Event Type: Warning
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 2007 client, if the X-MICROSOFT-CDO-ATTENDEE- CRITICAL-CHANGE attribute is missing, the PR_RECIPIENT_TRACKSTATUS_TIME property is set to "1/1/1601 00:00:00 AM." 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.
After you install the hotfix, you must create the FixRecipientTrackStatusTime registery entry to enable the hotfix.To have us activate the hotfix for you , go to the "Fix it for me" section. If you prefer to activate the hotfix yourself, go to the "Let me fix it myself" section.
Fix it for meTo activate the hotfix automatically, which will set the
FixRecipientTrackStatusTimeregistry value to 1, click the Fix this problem link. Then, click Run in the File Download dialog box and follow the steps in this wizard.
Fix this problem
Collapse this imageExpand this image
Microsoft Fix it 50338
Collapse this imageExpand this image
Note this Fix it solution works for all languages. However, for some languages, the wizard text may be in English
Note if you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.
Let me fix it myselfImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
After you install the hotfix, you must create the FixRecipientTrackStatusTime register entry to enable the hotfix. To activate the hotfix yourself, follow these steps:
Hotfix informationA 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
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, contact 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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
Note This hotfix is also known to resolve the following error message that IMAP clients receive when the PR_RECIPIENT_TRACKSTATUS_TIME MAPI property is blank on the affected message:
Header download for the 'FOLDERNAME' folder did not complete. Could not download new messages from the IMAP server. Account: 'ACCOUNT', Server: 'SERVER', Protocol: IMAP, Server Response: 'The requested message could not be converted to an RFC-822 compatible format.', Port: 143, Secure(SSL): No, Error Number: 0x800CCCD2
PrerequisitesMicrosoft 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:
(http://support.microsoft.com/kb/836993/ )How to obtain the latest service packs for Exchange Server 2003
Restart requirementYou do not have to restart the computer after you apply this hotfix. However, the following services are automatically restarted when you apply this hotfix:
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
File informationThe 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.
Note After you install this hotfix, messages will be sent and received correctly. However, Outlook may incorrectly display the following text: This occurs because Exchange 2003 is forced to make a best-effort calculation on what the value for PR_RECIPIENT_TRACKSTATUS_TIME should be because Exchange 2007 does not propagate it back to Exchange 2003.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 938650 - Last Review: June 21, 2014 - Revision: 15.0