Microsoft KB Archive/298037

= You receive a &quot;The Windows Installer service is already running on your system&quot; error message when you run Office XP Setup =

Article ID: 298037

Article Last Modified on 12/4/2007

-

APPLIES TO


 * Microsoft Office XP Professional Edition
 * Microsoft Office XP Standard Edition
 * Microsoft Office XP Developer Edition

-



This article was previously published under Q298037



For a Microsoft Office 2000 version of this article, see 239584.



SYMPTOMS
When you run Setup for Office XP, you may receive the following error message:

The Windows Installer service is already running on your system. Please wait until it is finished and then apply this update.



CAUSE
You receive this error message if all of the following are true:
 * You run Setup by using a transform that was created by the Custom Installation Wizard (CIW).
 * When you create the transform, you specify an additional program to run with Setup.
 * The additional program that you specify in the Custom Installation Wizard is an updater that contains a Windows Installer patch file (.msp). For example, the patch file WRD1001.exe contains the following .msp file: Winword.msp.

When the updater is run during Office Setup, you are essentially running two Windows Installer Setups at the same time. You can only do this if you are chaining together two or more Windows Installer product installations (.msi files) by using a customized Setup.ini file.



WORKAROUND
To work around this problem, do not include an updater that contains an .msp file in your transform. Instead, use one of the following methods.

Method 1: Use an Administrative Installation
If you create an administrative installation for Office, you can update the administrative installation with Office updates. When you install Office on network client computers, the updates will be automatically installed along with Office. Also, you can update the administrative installation with more updates in the future and then use a simple command line on the network client computers to update them.

NOTE: You can only create administrative installations if you have an Enterprise edition of Office. For additional information about applying updates to administrative installations, click the article number below to view the article in the Microsoft Knowledge Base:

301348 OFFXP: How to Install a Public Update to Administrative Installations

Method 2: Use a Customized Setup.ini File
Office XP can use a new section in the Setup.ini file for chaining .exe and .msi files onto an Office installation. Because of this, you can use Msiexec.exe (the main Windows Installer executable) to apply a patch immediately after you install Office. To create this new section, you can use the Setup INI Customization Wizard to modify the Setup.ini file.

NOTE: You do not need an Enterprise edition of Office to use this method.  Expand the .msp files from the IExpress download packages by using a command line similar to the following

\WRD1001.exe /c /t:c:\Wordfiles

where  is the path to the downloaded IExpress package. This command line extracts Winword.msp to the c:\Wordfiles folder.

 Copy Winword.msp to a network share. Install the Office XP Resource Kit to install the Setup INI Customization Wizard. Click Start, point to Programs, point to Microsoft Office Tools, point to Microsoft Office XP Resource Kit Tools, and then click Setup INI Customization Wizard. In the Specify an administrative installation point dialog box, type the path to an administrative installation or to a copy of the Office CD-ROM on a server. Click Next. In the Specify an INI file to customize dialog box, select Setup.ini and then click Next.</li> Configure any options in the Specify logging and display settings to use during Setup dialog box, and then click Next.</li>  In the Select MSI and EXE files to include in your INI file dialog box, type the local path to Msiexec.exe in the Name and path of the MSI or EXE file to add box, and then click Add. The local path to Msiexec.exe will vary, according to the following table. <pre class="fixed_text">  Microsoft Windows version   Path to Msiexec.exe --

Windows 98                 C:\Windows\System\Msiexec.exe Windows Me                 C:\Windows\System\Msiexec.exe Windows NT 4.0             C:\Winnt\System32\Msiexec.exe Windows 2000               C:\Winnt\System32\Msiexec.exe NOTE: You might receive an error message that states that Msiexec.exe cannot be found. Click Yes to add the path anyway.

</li> Click Next in the Select MSI and EXE files to include in your INI file dialog box.</li> In the Specify options for each package in your INI file dialog box, select the entry for Msiexec.exe.</li> In the Command line arguments edit box, type a command line similar to the following:

/p \\server\share\winword.msp

</li> Click Next.</li> In the View the summary of your INI file dialog box, click Save As.</li> In the Save As dialog box, type a name for your customized .ini file, and then click Save.</li> Click Finish in the last dialog box of the Setup INI Customization Wizard.</li> Install Office by using the customized Setup.ini file. The following is a sample command line that specifies a customized Setup.ini file:

\\server\share\Setup.exe /settings \\server\share\files\setup\chainsetup.ini

</li></ol>

How to Chain More Than One Patch
If you have more than one patch to chain onto your Office installation, follow these steps to include the additional patches.

NOTE: If you did not follow the preceding steps to include the first patch, please do that now. <ol> Open your customized Setup.ini file in a text editor like Notepad.</li> Locate the [ChainedInstall_1] section.</li>  Copy the entire [ChainedInstall_1] section. The following is an example of how this section may appear in your customized Setup.ini file: <pre class="fixed_text">[ChainedInstall_1] Path=c:\windows\system\msiexec.exe CmdLine=/p \\server\share\winword.msp TaskType=exe IgnoreReturnValue=0 Reboot=0 </li> Paste the copied section below the [ChainedInstall_1] section.</li> Rename [ChainedInstall_1] in the copied section to [ChainedInstall_2].</li> <li>Change the CmdLine line to specify the second .msp file.</li> <li>Repeat these steps for a third and subsequent patch to add to the installation. For each additional patch that you add, increment the index number (n) in the [ChainedInstall_n] section heading by one.</li> <li>Save and close the customized Setup.ini file.</li> <li>Install Office by using the customized Setup.ini file. The following is a sample command line that specifies a customized Setup.ini file:

\\server\share\Setup.exe /settings \\server\share\files\setup\chainsetup.ini

</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
When you create a transform by using the Custom Installation Wizard (CIW), you can add programs to your Office installation in the Add Installations and Run Programs dialog box. However, when you click Add, there is a warning in the Add Program Entry dialog box:

See the Office Resource Kit for information about adding a Windows Installer package (*.MSI, *.MST or *.MSP) or a program (MSIEXEC.EXE or maybe SETUP.EXE) that launches such a package.

If you ignore this warning, you will experience the symptoms described in the &quot;Symptoms&quot; section of this article.

For additional information about chaining together two Office product installations, click the article number below to view the article in the Microsoft Knowledge Base:

281933 OFFXP: How to Deploy Multiple Products in a Single Installation

Additional query words: prb OFFXP

Keywords: kbsetup kbtshoot kberrmsg kbprb KB298037

-

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

© Microsoft Corporation. All rights reserved.