Article ID: 909109
Article Last Modified on 4/24/2007
APPLIES TO
- Microsoft Office Outlook 2003
Important This article contains information about how to modify the registry. Make sure to 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
SUMMARY
If 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.
WORKAROUND
If 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.
RESOLUTION
How to obtain the hotfix
This 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 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.
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 your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To enable this hotfix, follow these steps:
- Quit Outlook 2003.
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click to select the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Options\Calendar
- After you select the key that is specified in step 3, point to New on the Edit menu, and then click DWORD Value.
- Type ForceMtgForwardResponse, and then press ENTER.
- Right-click ForceMtgForwardResponse, and then click Modify.
- In the Value data box, type 1, and then click OK.
- On the File menu, click Exit to quit Registry Editor.
MORE INFORMATION
The following scenarios document known issues with the hotfix that is described in this article. These scenarios use the following notation to represent the users:
- UserO is the meeting organizer who sends the meeting request.
- UserR is the user who receives the meeting request from the meeting organizer and then forwards the meeting request.
- UserF is the user who receives the forwarded meeting request.
Scenario 1: UserF is not prompted to send a response if the meeting request does not use the "Request Response" option
If 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:
- UserO creates a meeting request that does not use the Request Response option. Then, UserO sends the meeting request to UserR.
- UserR forwards the meeting request to UserF.
- UserF accepts the forwarded meeting request.
Scenario 2: The meeting is accepted if UserF clicks the "Edit the response before sending" option and then closes the message
If 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:
- UserO sends a meeting request to UserR.
- UserR forwards the meeting request to UserF.
- UserF accepts the forwarded meeting request. Then, UserF clicks the Edit the response before sending option in the meeting request. A new message appears in which UserF can respond to the meeting request.
- UserF closes the new message and does not send the response.
Scenario 3: UserR must send a response after forwarding the meeting request
UserR 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:
- UserO sends a meeting request to UserR.
- UserR forwards the meeting request to UserF.
- UserR accepts the meeting request.
Scenario 4: The "Don't send a response" option is still available if UserF forwards the meeting request by using the Outlook Object Model
If 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:
- UserO sends a meeting request to UserR.
UserR forwards the meeting request to UserF by using the OOM. For example, UserR uses the following code to forward the meeting request:
Sub FwdMtg() Dim olApp As New Outlook.Application Dim olInbox As Outlook.MAPIFolder Dim olMtg As Outlook.MeetingItem Dim olMtgFwd As Outlook.MeetingItem Set olInbox = olApp.GetNamespace("MAPI").GetDefaultFolder(olFolderInbox) Set olMtg = olInbox.Items(1) Set olMtgFwd = olMtg.Forward olMtgFwd.Recipients.Add ("UserF") ‘change user to recipient who receives the fwd item 'olMtgFwd.Display olMtgFwd.Send End Sub- UserF accepts the meeting request.
Scenario 5: The "Don't send a response" option is still available if UserR forwards the meeting request by using Outlook Web Access
If 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:
- UserO sends a meeting request to UserR.
- UserR logs on to Outlook Web Access, and then forwards the meeting request to UserF.
- UserF accepts the meeting request.
Keywords: kbcalendar kbqfe kbbug kbfix kbpubtypekc KB909109
