Microsoft KB Archive/319624

= &quot;Windows Installer Service could not be accessed&quot; error message when installing application =

Article ID: 319624

Article Last Modified on 8/30/2005

-

APPLIES TO

 Microsoft Windows Installer 1.0, when used with:  Microsoft Windows NT 4.0 Service Pack 6

 Microsoft Windows 2000 Service Pack 1

 Microsoft Windows 2000 Service Pack 2

 Microsoft Windows 2000 Service Pack 3</li></ul> </li> Microsoft Windows Installer 1.1, when used with:  Microsoft Windows NT 4.0 Service Pack 6</li></ul>

 Microsoft Windows 2000 Service Pack 1</li></ul>

 Microsoft Windows 2000 Service Pack 2</li></ul>

 Microsoft Windows 2000 Service Pack 3</li></ul> </li> Microsoft Windows Installer 1.2, when used with:  Microsoft Windows NT 4.0 Service Pack 6</li></ul>

 Microsoft Windows 2000 Service Pack 1</li></ul>

 Microsoft Windows 2000 Service Pack 2</li></ul>

<ul> <li>Microsoft Windows 2000 Service Pack 3</li></ul> </li> <li>Microsoft Windows Installer 2.0, when used with: <ul> <li>Microsoft Windows NT 4.0 Service Pack 6</li></ul>

<ul> <li>Microsoft Windows 2000 Service Pack 1</li></ul>

<ul> <li>Microsoft Windows 2000 Service Pack 2</li></ul>

<ul> <li>Microsoft Windows 2000 Service Pack 3</li></ul> </li></ul>

-

<div class="notice_section">

This article was previously published under Q319624

<div class="symptoms_section">

SYMPTOMS
After you upgrade to Windows Installer version 2.0, the Windows Installer Service may not start, and you may receive the following error message:

The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or the Windows Installer is not correctly installed. Contact your support personnel for assistance.

Note This behavior does not occur in the following products:
 * Microsoft Windows XP
 * Microsoft Windows Millennium Edition
 * Microsoft Windows 98

<div class="cause_section">

CAUSE
This behavior can occur when either of the following conditions exist:
 * In the DCOM permissions, the default authentication level is set to None, and the default Impersonation level is set to Anonymous.
 * The system account does not have Full permissions on a folder or registry key that the Windows Installer is trying to access. This is NTFS-specific.

<div class="resolution_section">

RESOLUTION
Depending on the issue, use one or all of the following methods:
 * Method 1: Unregister and re-register Windows Installer.
 * Method 2: Verify the DCOM permissions.
 * Method 3: Give Full Control permission to the SYSTEM account.
 * Method 4: Verify the registry permissions.
 * Method 5: Fix the broken security key for the MsiServer service.

Before you begin: Verify that the service pack is installed
If you are using Windows 2000, make sure that SP 2 is installed.

If you are using Windows NT 4.0, make sure that SP 6 is installed.

If you do not install the appropriate service packs, the steps in the &quot;More Information&quot; section of this article may not work as expected.

<div class="moreinformation_section">

Method 1: Unregister and re-register the Windows Installer

 * 1) Click Start, click Run, type MSIEXEC /UNREGISTER, and then click OK. Even if you do this correctly, it may look like nothing occurs.
 * 2) Click Start, click Run, type MSIEXEC /REGSERVER, and then click OK. Even if you do this correctly, it may look like nothing occurs, or you may briefly see an hourglass. After you run this command, the operation is complete.
 * 3) Try your Windows Installer-based application again.

Method 2: Verify the DCOM permissions
This method involves changing the DCOM default impersonation level to Identify, removing the Msisip.dll file, and then reinstalling SP 3 for Windows 2000.

To do this, follow these steps: <ol> <li>Click Start, click Run, type dcomcnfg, and then click OK.</li> <li>On the Default Properties tab: <ol style="list-style-type: lower-alpha;"> <li>In the Default Authentication Level list, click Connect.</li> <li>In the Default Impersonation Level list, click Identify, and then click OK.</li></ol> </li> <li>Click Start, click Run, type explorer /select, %windir%\system32\msisip.dll, and then click OK.</li> <li>Rename the Msisip.dll file as Msisip.old .</li> <li>Reinstall Windows 2000 Service Pack 3.</li></ol>

Method 3: Give Full Control permission to the SYSTEM account

 * 1) Start Windows Explorer, right-click the computer's root hard drive, and then click Properties.
 * 2) Click the Security tab, and then click Add.
 * 3) In the Select Users, Computers, or Groups dialog box, click the SYSTEM account, click Add, and then click OK.
 * 4) Under Allow, click to select the Full Control check box, and then click OK.
 * 5) Click the TEMP folder and then verify that the SYSTEM account has full control.

Method 4: Verify the registry permissions
<ol> <li>Click Start, click Run, then type Regedt32 .</li> <li>For each of the registry hives, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Select the hive.</li> <li>For Windows XP, on the Edit menu, click Permissions.

For Windows 2000 and Windows NT 4, on the Security menu, click Permissions.</li></ol> </li> <li>Verify that the SYSTEM account has been added and that it has Full control. If it does not, add the SYSTEM account with Full control.</li></ol>

Method 5: Fix the broken security key for the MsiServer service
<ol> <li>Start the computer by using Windows 2000.</li> <li>Click Start, click Run, type regedit.exe, and then rename the following key to Old_Security:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer\Security

</li> <li>Restart the computer (you must do this).</li> <li>Run Instmsiw.exe for installer 2.0 again; this corrects the broken security key for the MSI service.</li></ol>

Keywords: kbpubtypekc kbprb KB319624

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.