Error codes for Office 2010 update packages
Applies to: Office 2010
Topic Last Modified: 2011-10-12
Administrators can use Setup logs to help troubleshoot errors in Office 2010 software update packages (sometimes called patches). This article lists the error codes for Office 2010 software updates and explains how to use Microsoft self-extractor logs to troubleshoot errors.
In this article:
Error codes used by software update packages
Using Microsoft Self-Extractor logs to troubleshoot errors
Error codes used by software update packages
The following table lists the error codes that may be used by Office 2010 update packages. These error codes are available within executable files from service packs and public updates only. You can find the codes in the software update (patch) log files. They are typically used in custom Microsoft System Center Configuration Manager 2007 and third-party deployment scripts, and software update installation scripts.
| Error message | Value |
|---|---|
Success |
= 0 |
Error: General Detection error |
= 17301 |
Error: Applying patch |
= 17302 |
Error: Extracting file |
= 17303 |
Error: Creating temp folder |
= 17021 |
Success: Reboot flag set |
= 17022 |
Error: User cancelled installation |
= 17023 |
Error: Creating folder failed |
= 17024 |
Patch already installed |
= 17025 |
Patch already installed to admin installation |
= 17026 |
Installation source requires full file update |
= 17027 |
No product installed for contained patch |
= 17028 |
Patch failed to install |
= 17029 |
Detection: Invalid CIF format |
= 17030 |
Detection: Invalid baseline |
= 17031 |
Error: Required patch does not apply to the machine |
= 17034 |
You do not have sufficient privileges to complete this installation for all users of the machine. Log on as administrator and then retry this installation. |
=17038 |
Installer was unable to run detection for this package. |
=17044 |
This installation requires Windows Installer 3.1 or greater. |
=17048 |
Using Microsoft Self-Extractor logs to troubleshoot errors
Administrators can use Setup log files to help troubleshoot errors. Setup logs are not automatically created during the installation of the Office 2010 updates. To generate the Microsoft Self-Extractor logs, you must use the /log switch and the path of a specific log file.
To create a log for an Office 2010 SP1 package, type the following at the command prompt:
Office2010SP1ClientUpdateFilename **/log:%temp%\**Logfilename.txt
where:
Office2010SP1ClientUpdateFilename is the Office 2010 SP1 Microsoft Self-Extractor file (.exe). For example, officesuite2010sp1-kb2460049-x86-fullfile-en-us.exe.
%temp% refers to the Windows temp folder. The /log command does not create a folder, so using the %temp% folder ensures that the location always exists.
LogFilename.txt represents the log file name which you must provide. For example, Office2010SP1SetupLog.txt.
Example
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.