How to use a setup log file to troubleshoot Office Setup?

[Sabastiaan]

Hello everyone,
Several times there are an issues with the Microsoft Office. A problem sometimes occurs with the setup of Office unless you receive an error message. Many times, even if an error message appears, I may need to use a setup log file as a tool to identify the problem. I want to know that is there any logic that describes several techniques to interpret the information contained in the installation log files in Office. If yes, then please tell me how to use a setup log file to troubleshoot Office Setup? Thanks in Advance.!!

[Raine]

Setup for Office automatically creates log files in your \ Temp. Their names are similar to the following names :

• Setup.exe - Microsoft Office Setup (0001). txt
• Windows Installer (Updated system files) - Microsoft Office Setup (0002)_ Task (0001). Txt
• Windows Installer (Installation of Microsoft Office) - Microsoft Office Setup (0003)_ Task (0002). Txt

You might have observed that the log file that has the highest number is the log file the most recent time that you ran Setup. You can have a single log file Microsoft Windows Installer to install Office. Where appropriate, Task (0001) is inserted into the log file name for Windows Installer installation of Office, instead of Task (0002).

[Kirmiac]

The log file Setup.exe is very short, because the number of tasks that Setup.exe performs is limited to the tasks below :

1. Read the Setup.ini file.
2. Analyze properties and switches on the command line to pass to Windows Installer. A common mistake is to include the following on a command line :
   
   • Transform = path \ file name processing. Mst
3. Then you will have to verify that the operating system and service pack are used correctly.
4. After that check the file version Msi.dll.
5. Then start Instmsi (w). Exe to install Windows Installer.
6. Once you have installed the Windows Installer, Search for beta versions of Office installed.
7. Check the version of the Tahoma font and TahomaBD.

[Zenon]

By default, Setup creates a local installation source of Office, but only if you install this software from the CD-ROM or an image of compressed CD. If disk space is sufficient on the local computer, Setup caches the entire installation source by default. Windows Installer uses this local installation source to install Office, and it remains available for repairing, reinstalling or updating Office. Users can install features on demand or run Setup in maintenance mode to add new ones. Because Setup creates the local installation source by default, you do not have to set other options. It creates the local installation source in the following hidden folder on the user's computer :

• drive \ Msocache \ Downloadcode

[Bigga Lexx]

In the journal entries that contain "Note", the four-digit number following this element can be directly mapped to the Windows Installer errors. "Return Value 3" is another string to search the log file. If you are not having an error number or if you do not remember, but you locate "Return Value 3" in the log file, it is clearly the area in which you focus your troubleshooting. Any action performed during the program installation is recorded in the log files. If an action is completed, a return value is subsequently noted. If the return value is 1, the action was successful and if it fails, the return value is 3.

[Rob Dizzle]

The verbose logging is not used for the initial installation of Office, but it can be used in case of failure of the setup, the second attempt installation creates a detailed log file. However, the logging options used for these logs are not detailed all the options that are available for Windows Installer. If you want to create a Windows Installer log file more detailed with all the logging options you can use the combination of parameters * v for the / L switch. You should know that you can create a verbose log file when you run an administrative installation of Office by using a command line similar to the following :

• path \ setup.exe / a path \ Pro11.msi / L * v C: \ Verboselog.txt