Article ID: 274533 - View products that this article applies to.
This article was previously published under Q274533
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
When you install any Office 2000 update, you see multiple copies of the Windows Installer patch package file (.msp file) in the \Windows\Installer folder. One example of an Office 2000 update is the Microsoft Office 2000 Service Release 1a (SR-1a) Update.
You installed multiple Office 2000 products and ran the update after you installed each Office 2000 product.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To work around this problem, you can manually remove each orphaned .msp file, after you search for each file in the system registry and do not find the file. To do this, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
When you update your installation of Office 2000 with the SR-1/1a Update or any other Office 2000 patch, the update files (.msp) are copied to your hard disk drive. The .msp files in the \Windows\Installer folder are always used for any Windows Installer actions on your installation of Office 2000.
Each Office 2000 family product maintains its own information about its patches, including the cached .msp files. Microsoft Office only intends to keep one cached copy of a patch, no matter how many products use the patch, but Microsoft Office fails to use the existing cached .msp file when the patch is applied to a second product. At this point, the original cached .msp file is orphaned.
For additional information about the .msp file, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/256896/ )OFF2000: Error Message: The Feature You Are Trying to Use Is on a Network Resource That Is Unavailable
Article ID: 274533 - Last Review: January 27, 2005 - Revision: 1.2