"The operation failed. An object could not be found" error message when you add an attachment to a recurring meeting in Outlook 2002

If an Outlook 2002 user updates a single occurrence of a recurring meeting and adds an attachment, some attendees may receive the following error message when they try to accept the updated meeting request.

Service Pack Information

This problem is corrected in Microsoft Office XP Service Pack 3.

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

Hotfix Information

A 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 this specific problem.

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, submit a request to 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: Note 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.
You must install Office XP Service Pack 2 (SP2) before you install this hotfix.

The global version of this hotfix has the file attributes (or later) 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 tool in Control Panel.

After the hotfix is installed, the following files will have the listed attributes or later:

Scenarios

Important Under certain circumstances, Windows Installer 2.0 is required before you can apply the Office XP Post-SP2 Client-Side Hotfix. The following scenarios will help determine if this applies to you.

1. You used one of the following methods to deploy Office XP:
   1. You used an administrative installation point. For more information, see "Creating an Administrative Installation Point" at the following Microsoft Web site:
      http://www.microsoft.com/office/ork/xp/one/depb01.htm (http://www.microsoft.com/office/ork/xp/one/depb01.htm)
   2. You assigned or published Office with IntelliMirror. For more information, see "Assigning or Publishing Office" at the following Microsoft Web site:
      http://www.microsoft.com/office/ork/xp/one/depb09.htm (http://www.microsoft.com/office/ork/xp/one/depb09.htm)
   If you used either of these methods, you may have a problem deploying a hotfix that was released after Office XP SP2 if all the following conditions are true:
   1. The organization is using Windows Installer 1.1 (see below)
      
      -and-
   2. The organization deployed Office XP Service Pack 1 (SP1) by using a client patch. For more information, see "Updating Office by Using Client Updates" at the following Microsoft Web site:
      http://www.microsoft.com/office/ork/xp/journ/Cliupdt.htm (http://www.microsoft.com/office/ork/xp/journ/Cliupdt.htm)
      -and-
   3. The organization deployed Office XP SP2 by using a client patch. For more information, see "Updating Office by Using Client Updates" at the following Microsoft Web site:
      http://www.microsoft.com/office/ork/xp/journ/Cliupdt.htm (http://www.microsoft.com/office/ork/xp/journ/Cliupdt.htm)
2. If you deployed Office XP by using a CD image, you may have a problem deploying a hotfix released after Office XP SP2 if all the following conditions are true:
   1. The organization is using Windows Installer 1.1.
      
      -and-
   2. The organization deployed Office XP SP1 by using a client patch.
      
      -and-
   3. The organization deployed Office XP SP2 by using a client patch.

Note 1: If you have updated your administrative installation point for Office XP with the administrative version of either Office XP SP1 or Office XP SP2, you are unlikely to have a problem when you deploy the hotfix. For more information, see "Administrative Updates" at the following Microsoft Web site: Note 2: If you are using Windows Installer 2.0, you are unlikely to have a problem when you deploy the hotfix.

Suggested Steps

If any of the scenarios that were described earlier applies to you, you must deploy Windows Installer 2.0 on all the computers that need the hotfix. You can obtain Windows Installer 2.0 in the following ways:

1. By default, Windows Installer 2.0 is included in Microsoft Windows XP. If you have deployed Windows XP in your organization, you are unlikely to have a problem when you deploy the hotfix.
2. Windows Installer 2.0 is included in Microsoft Windows 2000 Service Pack 3 (SP3). If you have deployed Windows 2000 SP3, you are unlikely to have a problem when you deploy the hotfix.
3. Windows Installer 2.0 is available as a redistributable from the Microsoft Download Center at the following Microsoft Web sites:
   1. Windows Installer Redistributable for Microsoft Windows 95, 98, and Me:
      http://www.microsoft.com/downloads/details.aspx?FamilyID=cebbacd8-c094-4255-b702-de3bb768148f%20&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=cebbacd8-c094-4255-b702-de3bb768148f%20&displaylang=en)
   2. Windows Installer Redistributable for Microsoft Windows NT 4.0 and 2000:
      http://www.microsoft.com/downloads/details.aspx?familyid=4B6140F9-2D36-4977-8FA1-6F8A0F5DCA8F (http://www.microsoft.com/downloads/details.aspx?familyid=4B6140F9-2D36-4977-8FA1-6F8A0F5DCA8F)

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. This problem was first corrected in Office XP Service Pack 3.