Export (0) Print
Expand All

Error codes for 2007 Office update packages

Updated: November 15, 2007

Applies To: Office Resource Kit

 

Topic Last Modified: 2008-09-26

The following table lists the error codes that may be used by 2007 Office update packages. These error codes are available within executable files from service packs and public updates only. The codes are found in the patch logs and they are typically used in custom Microsoft Systems Management Server (SMS) and third-party deployment scripts, and patch 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

Administrators can use Setup log files to help troubleshoot errors. Setup logs are not automatically created during the installation of the 2007 Office system Service Pack 1 (SP1) updates. To generate the Microsoft Self-Extractor logs, you must use the /log switch along with a path to a specific log file.

To create a log for a 2007 Office system SP1 package, type the following at the command prompt:

2007OfficeSystemSP1ClientUpdateFilename /log:%temp%\Logfilename.txt

where:

2007OfficeSystemSP1ClientUpdateFilename is the 2007 Office system SP1 Microsoft Self-Extractor file (.exe).

%temp% refers to the Windows temp folder. The preceding 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, Office2007SP1SetupLog.txt.

For example, type:

office2007sp1-kb936982-fullfile-en-us.exe /log:%temp%\Office2007SP1SetupLog.txt

In addition to the file name specified, other log files are created based on the patches being installed by the Microsoft Self-Extractor file.

The following table lists the log files that are created for the 2007 Office system SP1 files by using the command in the preceding example.

 

2007 Office system SP1 client update Log files

office2007sp1-kb936982-fullfile-en-us.exe

ClientSharedMUIsp1-en-us.log

MAINMUIsp1-en-us.log

MAINWWsp1.log

Proofsp1-en-us.log

Proofsp1-es-es.log

Proofsp1-fr-fr.log

Office2007SP1SetupLog.txt

project2007sp1-kb937154-fullfile-en-us.exe

ProjectWWsp1.log

ProjectMUIsp1-en-us.log

Project2007SP1SetupLog.txt

sharepointdesigner2007sp1-kb937162-fullfile-en-us.exe

SharepointdesignerWWsp1.log

SharepointdesignerMUIsp1-en-us.log

Sharepointdesigner2007SP1SetupLog.txt

visio2007sp1-kb937155-fullfile-en-us.exe

VisioWWsp1.log

VisioMUIsp1-en-us.log

Visio2007SP1SetupLog.txt

For failures, it is important to check the log file specified in the command line. If one of the patches 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 patch is not applied.

A successful installation is indicated by a line such as the following:

OPatchInstall: Property 'SYS.PROC.RESULT' value '0'

The log files can also provide information about a request to restart the computer at the end of the installation. In such cases, the log file provides an indication that the restart was necessary, as shown next:

OPatchInstall: Property 'SYS.PATCH.NEEDREBOOT' value '1'

To obtain information about why the restart is required, you must review the MAINWWsp1.LOG file. If a different package is being installed, review the <product>WWsp1.LOG file for the product being installed. To find the information, open the file 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 Enterprise 2007. The file C:\Program Files\Common Files\Microsoft Shared\OFFICE12\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.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft