Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. OFF2000: "Installer Terminated Prematurely" Error Message When You Use ! Logging Option

OFF2000: "Installer Terminated Prematurely" Error Message When You Use ! Logging Option

View products that this article applies to.

This article was previously published under Q292032

↑ Back to the top

Symptoms

If you use the ! logging option when you install Office 2000 (for example, e:\setup.exe /L*V! C:\verbose.txt), you may receive the following error message near the end of the installation:
Installer terminated prematurely.
When you click OK to this error message, you receive the following error message:
The I/O operation has been aborted because of either a thread exit or an application request.
If you view the contents of the verbose log file, you see text similar to the following: 
Action 13:29:18: ForceReboot. 
MSI (c) (8F:4B): Executing op: RegAddRunOnceEntry(Name=904000001E872D116BF00006799C897,Command=/I "{00000409-78E1-11D2-B60F-006097C998E7}" AFTERREBOOT=1 RUNONCEENTRY="904000001E872D116BF00006799C897" /qF /lmewuifsoarpcv!+! "c:\verbose2.txt")
1: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce 2: 904000001E872D116BF00006799C897 3: C:\WINDOWS\SYSTEM\MsiExec.exe /@ "904000001E872D116BF00006799C897" 
1: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\RunOnceEntries 2: 904000001E872D116BF00006799C897 3: /I "{00000409-78E1-11D2-B60F-006097C998E7}" AFTERREBOOT=1 RUNONCEENTRY="904000001E872D116BF00006799C897" /qF /lmewuifsoarpcv!+! "c:\verbose2.txt" 
MSI (c) (8F:4B): Executing op: End(Checksum=0,ProgressTotal=0)
MSI (c) (8F:4B): FEATURECACHE: Entering Invalidate
MSI (c) (8F:4B): Generating exception report.
=====================================================
Exception code: C0000005 ACCESS_VIOLATION
Module: C:\WINDOWS\SYSTEM\MSI.DLL
Function: 0x244517e4
=====================================================

Registers:
EAX:00000026  EBX:00000026  ECX:245288F0  EDX:8200A00C  ESI:0082C154  EDI:2453B8A0
CS:EIP:015F:244517E4 SS:ESP:0167:0077EABC  EBP:2453B8A0
DS:0167  ES:0167  FS:2F3F  GS:0000
Flags:00010246

Call stack:
Address   Frame
244517E4  2453B8A0 0x244517e4
 -- 0x00000000 0x24539B90 0x00000000 0x00000000

Installer terminated prematurely.

↑ Back to the top

Cause

When you use the ! logging option and there is no fatal error during the installation, the Windows Installer creates a RunOnce registry key with invalid characters.

↑ Back to the top

Resolution

To resolve this problem, run Setup without the ! logging option. For example, you can use a command line similar to the following:
e:\setup.exe /L*V C:\verbose.txt
It is not necessary to use the ! logging option on computers where the Office installation does not stop responding (hang).

↑ Back to the top

Status

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

↑ Back to the top

More information

At times, Office Setup stops responding (hangs), and you do not receive any error message. In this situation, it is recommended that you restart your computer and re-run Office Setup with verbose logging enabled and the ! option included in the command line.

To do this, start Office Setup by following these steps:
  1. Click Start and then click Run.
  2. In the Open box, type the following command line, and then click OK:
    path\Setup.exe /L*v! C:\Verboselog.txt
    NOTE: path is the full path to your Office source location.
Generally, 19 lines of logging information are cached in memory before being written to the verbose log file (in this case, C:\Verboselog.txt). If you do not use the ! option for the /L (logging) switch, you may lose some or all of this cached information if Setup stops. If you use the ! option, the most you lose is one line, because the ! option forces the Windows Installer to write logging information to the log file one line at a time (there is no caching of information).

↑ Back to the top

Keywords: kbbug, kberrmsg, kbpending, KB292032

↑ Back to the top

Article Info
Article ID : 292032
Revision : 4
Created on : 1/31/2007
Published on : 1/31/2007
Exists online : False
Views : 523