For example, if the Office SP1 file name that you are using is officesuite2010sp1-kb2460049-x86-fullfile-en-us.exe and the log file that will contain the results is named Office2010SP1SetupLog.txt, you would type the following command:
officesuite2010sp1-kb2460049-x86-fullfile-en-us.exe /log:%temp%\Office2010SP1SetupLog.txt
In addition to the file name that is specified, other log files are created, based on the software updates that the Microsoft Self-Extractor file installs. When you use the /log command, a log file is created for every .msp package that is contained in the Microsoft Self-Extractor file (.exe).
The following table lists the log files that are created for the Office 2010 SP1 files by using the command in the above example. It also lists the logs files that are created for Microsoft Project 2010 SP1, Microsoft SharePoint Designer 2010 SP1, and Microsoft Visio 2010 SP1.
|
Office 2010 SP1 client update
|
Log files
|
|
officesuite2010sp1-kb2460049-x86-fullfile-en-us.exe
|
clientsharedmuisp1-en-us_MSPLOG.LOG
officesuitemuisp1-en-us_MSPLOG
officesuitewwsp1-x-none_MSPLOG.LOG
proofingsp1-en-us_MSPLOG.LOG
proofsp1-en-us_MSPLOG.LOG
proofsp1-es-es_MSPLOG.LOG
proofsp1-fr-fr_MSPLOG.LOG
Office2010SP1SetupLog.txt
|
|
project2010sp1-kb2460052-x86-fullfile-en-us.exe
|
projectwwsp1-x-none_MSPLOG.LOG
projectmuisp1-en-us_MSPLOG.LOG
Project2010SP1SetupLogFiles.txt
|
|
sharepointdesigner2010sp1-kb2460057-x86-fullfile-en-us.exe
|
sharepointdesignerwwsp1-x-none_MSPLOG.LOG
sharepointdesignermuisp1-en-us_MSPLOG.LOG
SharePointDesigner2010SP1SetupLogFiles.txt
|
|
visio2010sp1-kb2460061-x86-fullfile-en-us.exe
|
visiowwsp1-x-none_MSPLOG.LOG
visiomuisp1-en-us_MSPLOG.LOG
Visio2010SP1SetupLogFiles.txt
|
Failure messages
For failures, it is important to check the log file that is specified on the command line. If one of the software updates within the Microsoft Self-Extractor fails, an error code such as the following appears near the end of the log file:
OPatchInstall: Property 'SYS.PROC.RESULT' value '17031'
This code indicates that the version of the Office installation does not match the version that is expected. The software update is not applied.
A successful installation is indicated by a line such as the following:
OPatchInstall: Property 'SYS.PROC.RESULT' value '0'
Computer restart messages
The log files can also provide information about a request to restart the computer at the end of an installation. In such cases, the log file indicates that the restart is necessary, as shown next:
OPatchInstall: Property 'SYS.PATCH.NEEDREBOOT' value '1'
To obtain information about why the restart is required, you must review the officesuitewwsp1-x-none_MSPLOG.LOG file. If a different package is being installed, review the <product>wwsp1-x-none_MSPLOG.LOG file for the product that is being installed. To find the information, open the file by using a text editor such as Notepad, and search for this text (in Notepad, click Find on the Edit menu): “being held in use”. Then repeat the search.
When a restart is required, a message such as the following might be displayed:
"MSI (s) (F4:34) [16:34:37:904]: Product: Microsoft Office Professional Plus. The file C:\Program Files\Common Files\Microsoft Shared\OFFICE14\RICHED20.DLL is being held in use by the following process Name: searchprotocolhost , Id 3128."
In this example, the message indicates that the RICHED20.DLL file could not be updated because Microsoft Desktop Search was using that file. In some cases, you may be prompted to restart a process that was using a file during the update installation.