Multiple copies of the Windows Installer update package (.msp) file are created when you run an Office 2000 update

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:

256986 (http://support.microsoft.com/kb/256986/EN-US/ ) Description of the Microsoft Windows Registry

SYMPTOMS

When you install any Office 2000 update, you see multiple copies of the Windows...

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.

CAUSE

You installed multiple Office 2000 products and ran the update after you instal...

You installed multiple Office 2000 products and ran the update after you installed each Office 2000 product.

WORKAROUND

WARNING: If you use Registry Editor incorrectly, you may cause serious problems...

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:

1. Using Windows Explorer, open the \Windows\Installer folder.
   
   NOTE: You may need to customize your folder options, so that you can view all files. Please refer to your Windows documentation for more information.
2. Make a note of all files in the folder with an .msp file extension.
3. Click Start, and then click Run.
4. In the Open box, type Regedit and then click OK.
5. In the left pane of the Registry Editor, click My Computer to select it.
6. Click Find on the Edit menu.
7. Type the first .msp file name in the Find What box, and then click Find Next.
8. If you receive the message "Finished searching through the registry", the .msp file is orphaned and can be deleted. Make a note so that it can be deleted.
   
   If the Registry Editor finds a LocalPackage name with the .msp file extension in the Data column, the .msp file is referenced and should not be deleted.
9. Repeat steps 5 through 8 for each .msp file that you noted from step 2.
10. For each .msp file that you noted for deletion, right-click the .msp file in Windows Explorer, and then click Delete on the shortcut menu. Click Yes to confirm the deletion.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that ar...

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

When you update your installation of Office 2000 with the SR-1/1a Update or any...

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.

REFERENCES

For additional information about the .msp file, click the following article num...

For additional information about the .msp file, click the following article number to view the article in the Microsoft Knowledge Base:

256896 (http://support.microsoft.com/kb/256896/ ) OFF2000: Error Message: The Feature You Are Trying to Use Is on a Network Resource That Is Unavailable

---

APPLIES TO

• Microsoft Office 2000 Service Pack 1

Keywords:

kbtshoot kbsetup kbprb kbupdate KB274533

Veritas BUE 9.1 error - Directory not found. Can not backup directory \\XXXXX. The directory is invalid

After moving a directory from one volume to another, I started getting this error saying that there was an invalid directory in my BackupExec 9.1 remote selections even though when looking at the selections, there was no such directory selected. It turns out that there is a bug in ver. 9 and 10 of Backup Exec for Windows and the note below shows the steps to fix it.

Got this from http://seer.support.veritas.com/docs/207001.htm

---

Exact Error Message
Directory not found. Can not backup directory <\directory> and its subdirectories.
The job failed with the following error: The directory is invalid

Details:

Job Completion Status

Completed status: Failed

Final error code: a000fe09 HEX

Final error description: The directory is invalid

Final error category: Resource Errors

This error will occur when running a scheduled job which contains a reference to one or more directories which have been removed from the target drive.

To resolve this error, do the following:

1. From the Job Definitions tab, right-click on the backup job which produced the error, and then select Properties

2. Click the Selections tab

3. Under Display options, select Text version

4. Locate and remove all references to the directory producing the error

5. In the Selection list name, select Excludes (Figure 1)

Figure 1

6. Locate any references to the directory producing the error and remove it only if it does not have the "/EXCLUDE" at the end of the statement (Figure 1)

7. Save the Job Definition

In Backup Exec (tm) 9.x and 10.0 for Windows Servers, an alert is displayed including the error message (Figure 2) which is reported in the job log:

The job failed with the following error: The directory is invalid.

Figure 2

To resolve this issue, do the following:

1. From the Job Setup tab, right-click on the backup job for which the error occurred

2. Select Properties

3. Select the Selections option

4. Under the View format option, select Text

5. Locate and delete all references to the directory which produced the error (Figure 3)

Figure 3