Article ID: 826511 - View products that this article applies to.
For a Microsoft Office XP version of this article, see 296603
This step-by-step article describes how to use the Microsoft Office installation log files to troubleshoot Office Setup issues.
Occasionally a problem occurs with Office Setup and you may not receive an error message. Even if you receive an error message, you may have to use an installation log file as one of your tools to determine the issue.
This article discusses several techniques to interpret the information in Office installation log files. The topics are listed in the order that you want to use each technique. This article does not cover every situation that you may experience, but it discusses several examples where the Setup issue is resolved by interpreting a Setup log file.
Many articles in the Microsoft Knowledge Base that relate to installation errors also include sections of log files that help you confirm that the article describes the same issue that you are experiencing.
How to create a log fileOffice Setup automatically creates log files in your \Temp folder. The log files have names that are similar to the following:
The #### characters in the log file names are numbers that start with 0001. They increment by one each time that you run Setup. Therefore, the log file that has the highest number is the log file for the most recent time that you ran Setup.
Collapse this tableExpand this table
Note You may have only a Microsoft Windows Installer log file for the Office installation. In this situation, the Windows Installer log file for the Office installation has Task(0001) appended to the log file instead of Task(0002).
How to interpret log filesDepending on the problem that you are experiencing, you may have to view the Setup log file or the Windows Installer log file for the Office installation.
Setup log filesThe log file for the Setup.exe file is very short because the number of tasks that Setup.exe performs is limited to tasks like the following:
By default, Setup caches the whole source in Office. If the user's computer does not have sufficient disk space, Setup caches installation file for only the selected features. Setup retains the local installation source after the installation is complete.
The following information may be contained in the Setup log:
(http://support.microsoft.com/kb/830168/ )Frequently Asked Questions About the Local Install Source Feature
If you suspect problems with the command-line properties and switches that you are using, these items are also listed in the Setup log file. For example, if you use the following command line to run Setup
f:\Setup.exe companyname="my company" /qbthe following text is included in the Setup log:
Launch Setup 9/22/03 1:49:46 PM companyname="my company" /qb Detected Windows Info: PlatformId = 2 MajorVersion = 4 MinorVersion = 0 Setup path: \\server\share\2003_Admin\SETUP.EXE Adding property...companyname="my company" Recognized command line switch: /qb
Note Setup.exe does not actually use these command-line switches and properties; it just passes them to the Msiexec.exe file (the Windows Installer).
Office-specific properties added: companyname="my company" General properties added: LAUNCHEDFROMSETUP=1 SETUPEXEPATH=\\server\share\2003_Admin\ Writing Task: D:\WINNT\System32\msiexec.exe /I \\server\share\2003_Admin\PRO11.MSI METRICSSOURCE="\\server\share\2003_Admin companyname=""my company"" /qb" companyname="my company" LAUNCHEDFROMSETUP=1 SETUPEXEPATH=\\server\share\2003_Admin\ /qb
If the log file for Setup.exe ends in text that is similar to the following (return code: 1603), there was a problem with the Windows Installer portion of the installation:
In this case, you must review the Windows Installer log files for the Office installation.
9/22/03 3:34:27 PM Chained install return code: 1603 Shutting down chained setup processing. Set Verbose logging for subsequent setup. ***** Setup exits 9/22/03 3:34:27 PM (return = 1603)
Windows Installer log filesThe Windows Installer log files are significantly larger than the Setup log file and can appear to be unreadable at first. However, the following guidelines can help you narrow down the issue:
Verbose log filesAll the techniques that are listed in the "Windows Installer Log Files" section can be used on verbose log files. However, verbose logging increases Setup times. Only use verbose logging if you are having Setup problems that cannot be diagnosed with a default log file.
Article ID: 826511 - Last Review: March 22, 2012 - Revision: 4.0