Windows Installer-related event IDs are logged in the Application log when you start an Office program (911682)


The information in this article applies to:

  • Microsoft Office Professional Edition 2003
  • Microsoft Office Standard Edition 2003
  • Microsoft Office Students and Teachers Edition 2003
  • Microsoft Office Small Business Edition 2003
  • Microsoft Office Basic Edition 2003
  • Microsoft Office XP Professional
  • Microsoft Office XP Small Business
  • Microsoft Office XP Standard
  • Microsoft Office XP Students and Teachers
  • Microsoft Office 2000 Premium
  • Microsoft Office 2000 Professional
  • Microsoft Office 2000 Standard
  • Microsoft Office 2000 Small Business
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

SYMPTOMS

When you use a limited user account to start one of Microsoft Office programs that are listed in the "Applies to" section, one or more of the following Microsoft Windows Installer related event IDs are logged in the Application log:
Event ID: 1001
Event Source: MsiInstaller
Description:
Detection of product '{90280409-6000-11D3-8CFE-0050048383C9}', feature 'WORDFILES' 
failed during request for component '{8E46FEFA-D973-6294-B305-E968CEDFFCB9}'Event ID: 1015
Event Source: MsiInstaller
Description:
Failed to connect to server. Error: 0x80004001Event ID: 1004
Event Source: MsiInstaller
Description:
Detection of product '{90120409-6000-11D3-8CFE-0050048383C9}', feature 
'ProductFiles', component '{66CD2C91-2A15-4DA4-BBD2-5EC1075F3C0E}' failed. The 
resource 'HKEY_CLASSES_ROOT\.pip\' does not exist.Event ID: 1000
Event Source: MsiInstaller 
Description:
No installer is running when launching the applications.

RESOLUTION

To resolve this issue, use one of the following methods, depending on the event ID that is logged in the Application log.

Event ID 1015

You receive Event ID 1015 only if you use a Terminal Server session to start the Office program. Therefore, you have to perform this procedure on the Terminal Server console.
  1. Start a Terminal Server client session, and then log on as a user.
  2. Click Start, click Run, type msiexec /unreg in the Open box, and then click OK.
  3. Click Start, click Run, type msiexec /regserver in the Open box, and then click OK.

Event ID 1004, event ID 1001, and event ID 1000

To resolve the issues that are related to event ID 1004, to event ID 1001, and to event ID 1000, follow these steps.

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.

Note You can perform this procedure on a Terminal Server console or on the local computer, depending on the location on which the Office program is installed
  1. Start a Terminal Server client session, and then log on as a user.

    Note If you have installed the Office product on the local computer, go to step 2.
  2. Click Start, click Run, type regedit in the Open box, and then click OK.
  3. In the left pane, locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer
  4. On the Edit menu, click Permissions.
  5. In the permissions for Installer dialog box, click Administrators in the Group or user names list, and then make sure that the Full Control permission is set for the Administrators group. If this permission is not set, click to select the Full Control check box under Allow.
  6. Click OK.
  7. Repeat steps 5 through 6 for the SYSTEM group.
  8. Repeat steps 5 through 6 for the Everyone group. Verify that only the Read permission is set for the Everyone group. If this permission is not set, click to select the Read check box under Allow.
  9. Repeat steps 4 through 8 for the following registry subkeys:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Compo
    • HKEY_CLASSES_ROOT
    • HKEY_CLASSES_ROOT\.pip
    • HKEY_CLASSES_ROOT\Installer
    • HKEY_CLASSES_ROOT\Installer\Components
    • HKEY_CURRENT_USER\Software\Classes
  10. Clear the Application log, start the Office program, and then see whether you receive the event IDs that are mentioned in the "Symptoms" section.
If you still receive event ID 1004, delete the UsrClass.dat and UsrClass.dat.log files for every user on the terminal server or on the local computer. To do this, follow these steps:
  1. Click Start, point to Programs, point to Accessories, and then click Windows Explorer.
  2. In the left pane, locate and then click the following folder:

    Drive:\Documents and Settings\USERNAME\Local Settings\Application Data\Microsoft\Windows

    NoteDrive represents the drive letter for the hard disk drive partition on which Windows is installed.

    This Windows folder is in a hidden folder. To view the Windows folder, you must configure the folder settings to display hidden files and folders. If you cannot locate the Windows folder, verify that the folder settings on the computer are configured to display hidden files and folders. To do this, follow these steps:
    1. On the Tools menu, click Folder Options.
    2. In the Folder Options dialog box, click the View tab.
    3. Under Hidden files and folders, click Show hidden files and folders, and then click OK.
    4. Verify that the Windows folder is now available.
  3. In the right pane, right-click UsrClass.dat, and then click Delete.
  4. Click Yes when you are prompted to confirm the file deletion.
  5. Repeat steps 3 and 4 for the UsrClass.dat.log file.
  6. Start the Office program, and then verify that the event IDs that are mentioned in the "Symptoms" section are not logged in Application log.
Modification Type:MinorLast Reviewed:6/26/2006
Keywords:kbtshoot KB911682 kbAudEndUser kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.