Article ID: 909109 - Last Review: April 24, 2007 - Revision: 1.9 In Outlook 2003, a user does not receive meeting updates if the user clicked the "Don't send a response" option in response to a forwarded meeting requestOn This PageSUMMARYIf a Microsoft Office Outlook 2003 user who receives a meeting request that was forwarded by another Outlook 2003 user responds to the meeting request by clicking the Don't send a response option, the user does not receive any updates if the meeting organizer updates the meeting. This situation occurs because the original meeting is not updated with the new attendee information. This article describes an Outlook 2003 hotfix that resolves this issue by disabling the Don't send a response option in responses to forwarded meeting requests. To enable this hotfix after you install it, add the ForceMtgForwardResponse registry entry, and then set the registry entry to 1. After the hotfix is installed, a user who receives a meeting request that was forwarded by another user must respond to the meeting request. The Don't send a response option is unavailable. This hotfix must be installed on the computer of the user who forwards the meeting request and on the computer of the user who receives the forwarded meeting request. This article also discusses known issues with the hotfix. SYMPTOMS
Consider the following scenario. A Microsoft Office Outlook 2003 user receives a meeting request from a meeting organizer. Then, the user forwards the meeting request to another Outlook 2003 user. The recipient of the forwarded meeting request clicks the Don't send a response option when they reply to the forwarded meeting request. In this scenario, the meeting organizer does not know that the recipient of the forwarded meeting request was invited to the meeting. When the meeting organizer updates the meeting, the recipient of the forwarded meeting request does not receive any updates to the meeting because the recipient was not added to the original meeting request. WORKAROUNDIf you are the meeting organizer, update the original meeting request by adding the attendees that you want. Then, click Send Update to send the updated meeting request to all meeting attendees. RESOLUTIONHow to obtain the hotfixThis issue is fixed in the Outlook 2003 post-Service Pack 2 Hotfix Package that is dated November 7, 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:898457
(http://support.microsoft.com/kb/898457/
)
Description of the Outlook 2003 post-Service Pack 2 hotfix package: November 7, 2005 To enable this hotfix after you install it, add the ForceMtgForwardResponse registry entry to the following registry subkey, and then set the registry entry to 1: HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Options\Calendar When the ForceMtgForwardResponse registry entry is set to 1, the Don't send a response option in the meeting request appears dimmed and is unavailable. This procedure must be performed on the computer of the user who forwards the meeting request and on the computer of the user who receives the forwarded meeting request.Note When the ForceMtgForwardResponse registry entry is set to 0, the Don't send a response option in the meeting request is available. Important 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: 322756
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows To enable this hotfix, follow these steps:
MORE INFORMATIONThe following scenarios document known issues with the hotfix that is described in this article. These scenarios use the following notation to represent the users:
Scenario 1: UserF is not prompted to send a response if the meeting request does not use the "Request Response" optionIf the meeting request does not use the Request Response option, UserF is not prompted to send a response to the meeting request. The following is an example of when you may experience this issue:
Scenario 2: The meeting is accepted if UserF clicks the "Edit the response before sending" option and then closes the messageIf UserF clicks the Edit the response before sending option but does not send the message, the meeting is accepted. Additionally, the meeting appears in UserF's calendar in Outlook 2003. However, the meeting response is not sent to UserO. The following is an example of when you may experience this issue:
Scenario 3: UserR must send a response after forwarding the meeting requestUserR must send a response after forwarding a meeting request. The Don't send a response option appears dimmed and is unavailable. The following is an example of when you may experience this issue:
Scenario 4: The "Don't send a response" option is still available if UserF forwards the meeting request by using the Outlook Object ModelIf UserR forwards the meeting request by using the Outlook Object Model (OOM), the Don't send a response option is still available. The following is an example of when you may experience this issue:
Scenario 5: The "Don't send a response" option is still available if UserR forwards the meeting request by using Outlook Web AccessIf UserR forwards the meeting request by using Microsoft Office Outlook Web Access for Exchange Server 2003, the Don't send a response option is still available. The following is an example of when you may experience this issue:
| Article Translations
|
Back to the top
