Article ID: 296604
This article has been archived. It is offered "as is" and will no longer be updated.
The Microsoft Office XP Setup program automatically creates log files in your Temp folder. The log files have names similar to the following
where <edition> is the edition of Office that you are installing. For example, these files may be:
Log file for Log file name ----------------------------------------------------------------------- Setup.exe Office XP <edition> Setup(nnnn).txt Windows Installer (System Files Update) Office XP <edition> Setup(nnnn)_Task(0001).txt Windows Installer (Office installation) Office XP <edition> Setup(nnnn)_Task(0002).txt
Office XP Professional Setup(0001).txtThe nnnn characters in the log file names are numbers beginning with 0001. They increment by 1 if you have to run Setup multiple times. Therefore, the log file with the highest number is the log file for the last time you ran Setup.
Office XP Professional Setup(0001)_Task(0001).txt
Office XP Professional Setup(0001)_Task(0002).txt
NOTE: You may have a Windows Installer log file only for the Office installation and not the System Files Update. Because the System Files Update installation is not required on most versions of Windows, a log file is not created. In this situation, Task(0001) instead of Task(0002) is appended to the Windows Installer log file for the Office installation.
You cannot modify the logging options for the Setup.exe log file. However, you can customize the logging options for the Windows Installer log file.
The following table lists the available logging options that you can use with the /L switch of the Windows Installer.
NOTE: Do not use the ! option unless the Office installation stops responding. For additional information about this problem, click the article number below to view the article in the Microsoft Knowledge Base:
Parameter Description ------------------------------------------------------------------------ i Status messages w Non-fatal warnings e All error messages a Start up of actions r Action-specific records u User requests c Initial UI parameters m Out of memory p Terminal properties v Verbose output o Out-of-disk-space messages + Append to existing file * Wildcard, log all information except for the v option. ! Empty the logging cache, line by line, to the log file. The default is to write to the log file when 20 lines have been cached in memory.
(https://support.microsoft.com/kb/297107/EN-US/ )OFFXP: Err Msg: Installer Terminated Prematurely Using ! Option
Note that verbose logging is turned on by default for Office XP installations, but not all logging options are included. If you want to use all available logging options, see the "Use Complete Verbose Logging" section of this article.
path\setup.exe /L*v c:\Officelog.txtThis command line creates the installation log files. File names will be based on the Officelog.txt name, which located on the root of your C drive. For example, the command line creates the following log files for an Office installation that requires the System Files Update:
Officelog.txtNOTE: You can specify any path and file name for this log file.
The following is a sample command line:
path\setup.exe /Lme! c:\customlog.txt
Type=voicewarmupYou can also specify a path for your log files by creating a Path= line in the [Logging] section. For example, if you create the following entry in the [Logging] section
Path=c:\Logfilesthe Logfiles folder is created on the root of your C drive (if it does not already exist), and any log files that were created during the Office installation will be created in this folder.
If you modify the Setup.ini file in the Files\Setup folder of your administrative installation, you do not need a custom command line. However, if you rename the modified Setup.ini file, or it is located in a location other than the Files\Setup folder of your Office installation, use a command line similar to the following to reference the new settings file
path\setup.exe /settings \\servername\share\CustomSetup.iniwhere path is the path to Setup, servername is the server, and share is the share on the server.
Logging does not occur when you run Office Setup after Office has already been installed--for example, if Setup runs because a feature is being installed on demand (it was originally set to Installed on First Use), or you click Detect and Repair on the Help menu.
If you want to log either of these two situations, you can turn on logging by making the following changes in the Windows registry.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.