Update '{0FE78361-E9DC-43AF-BFF9-26249486B6E5}' could not be insta

[Todd]

We just began a rollout of Office 2007 to our department (various Dell model
Windows XP SP2 computers ) and have seen several failures with this error
from the event viewer:

Product: Microsoft Office Professional Plus 2007 - Update
'{0FE78361-E9DC-43AF-BFF9-26249486B6E5}' could not be installed. Error code
1603. Additional information is available in the log file
C:\WINDOWS\TEMP\MSI3e418.LOG.

I can't find anything in the log named.

Rerunning the install usually results in a successful install.

Any ideas on what's causing the error and how to prevent it?

Thanks,
Todd

 

[Bob Buckland ?:-\)]

Hi Todd,

Are these upgrades to an existing older version of Office?

Are you deploying using GPO with config.xml settings or using the Office Customization Tool (OCT) and .msp patch files?

What is the command line you're using/and or config.xml settings?

====================
We just began a rollout of Office 2007 to our department (various Dell model
Windows XP SP2 computers ) and have seen several failures with this error
from the event viewer:

Product: Microsoft Office Professional Plus 2007 - Update
'{0FE78361-E9DC-43AF-BFF9-26249486B6E5}' could not be installed. Error code
1603. Additional information is available in the log file
C:\WINDOWS\TEMP\MSI3e418.LOG.

I can't find anything in the log named.

Rerunning the install usually results in a successful install.

Any ideas on what's causing the error and how to prevent it?

Thanks,
Todd >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Todd]

Hi Bob,

Thanks for the reply. This is an upgrade from Office 2003 Professional.
We're using SMS to send it out and used the OCT to customize the install.
Here are the msp files in the updates folder:

10/14/2007 07:43 PM 12,743,168 ClientSharedMUIsp1-en-us.msp
12/19/2006 09:59 AM 1,240 eula.txt
01/28/2008 02:09 PM 11,896,320 excel.msp
10/14/2007 07:43 PM 21,981,184 MAINMUIsp1-en-us.msp
10/14/2007 07:43 PM 229,852,160 MAINWWsp1.msp
04/16/2008 03:02 PM 11,524,096 Ofc2007.MSp
10/14/2007 07:43 PM 6,956,544 Office64WWsp1.msp
02/25/2008 11:08 AM 5,050,368 outlfltr.msp
01/28/2008 02:10 PM 14,201,344 outlook.msp
10/14/2007 07:43 PM 5,749,760 Proofsp1-en-us.msp
10/14/2007 07:43 PM 324,608 Proofsp1-es-es.msp
10/14/2007 07:43 PM 324,608 Proofsp1-fr-fr.msp
10/27/2006 10:18 PM 75 README.TXT
12/19/2006 09:59 AM 1,240 SupplementalEula_OfficeClient_ar-sa.txt
02/15/2008 04:54 AM 9,736,192 targetdir.msp
02/15/2008 04:55 AM 15,180,288 visio.msp
02/25/2008 11:07 AM 11,772,416 xlconv.msp

The Ofc2007.MSp is the one created with the OCT. We're running setup with
no additional switches, everything is taken care of with the OCT
customizations. No user interaction is required.

We've seen 30 errors out of 225 attempts and this particular error has
occured 15 times so far. Of course we never saw this in our testing and
pilot phases.



Todd Lorenc
NYS Dept of Taxation & Finance

 

[Todd]

Any Ideas?

Hi Bob,

Thanks for the reply. This is an upgrade from Office 2003 Professional.
We're using SMS to send it out and used the OCT to customize the install.
Here are the msp files in the updates folder:

10/14/2007 07:43 PM 12,743,168 ClientSharedMUIsp1-en-us.msp
12/19/2006 09:59 AM 1,240 eula.txt
01/28/2008 02:09 PM 11,896,320 excel.msp
10/14/2007 07:43 PM 21,981,184 MAINMUIsp1-en-us.msp
10/14/2007 07:43 PM 229,852,160 MAINWWsp1.msp
04/16/2008 03:02 PM 11,524,096 Ofc2007.MSp
10/14/2007 07:43 PM 6,956,544 Office64WWsp1.msp
02/25/2008 11:08 AM 5,050,368 outlfltr.msp
01/28/2008 02:10 PM 14,201,344 outlook.msp
10/14/2007 07:43 PM 5,749,760 Proofsp1-en-us.msp
10/14/2007 07:43 PM 324,608 Proofsp1-es-es.msp
10/14/2007 07:43 PM 324,608 Proofsp1-fr-fr.msp
10/27/2006 10:18 PM 75 README.TXT
12/19/2006 09:59 AM 1,240 SupplementalEula_OfficeClient_ar-sa.txt
02/15/2008 04:54 AM 9,736,192 targetdir.msp
02/15/2008 04:55 AM 15,180,288 visio.msp
02/25/2008 11:07 AM 11,772,416 xlconv.msp

The Ofc2007.MSp is the one created with the OCT. We're running setup with
no additional switches, everything is taken care of with the OCT
customizations. No user interaction is required.

We've seen 30 errors out of 225 attempts and this particular error has
occured 15 times so far. Of course we never saw this in our testing and
pilot phases.



Todd Lorenc
NYS Dept of Taxation & Finance