Office 2010 GPO deployment broken with bad config.xml file

For several months I have been using a batch file to call my Office 2010 install and it has been working fine. Today when I put a PC in the Office install OU it does not install, when I run the setup.exe directly from the deploy folder I get an xml error:

The setup configuration file \\deployserver\x64_SP2\ProPlus.WW\config.xml is not valid. Verify this file is formatted correctly and run setup again.

I have not made any changes to the config.xml file since I moved the deploy point to a new server some months ago. Oddly enough, even the old location (which does not have SP2 streamed into it) does not work either, I get the same xml formatting error message. I have tried this on several different new PCs that have never had Office on them. The xml file gives no error when run thru an xml checker. My xml is below.

----------------------------------------------------------------------

<Configuration Product="Office14.ProPlus">

<Display Level="basic" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
      
<Logging Type="standard" Path="%temp%" Template="Microsoft Office Professional Plus Setup(*).txt" />

<PIDKEY Value="MyKeyCode" />

<USERNAME Value="DAH" />

<COMPANYNAME Value="My Company" />
      
<INSTALLLOCATION Value="%programfiles%\Microsoft Office" />
      
<LIS SOURCELIST="\\do-vs-app05\Office2010\x64_SP2" />
      
<DistributionPoint Location="\\do-vs-app05\Office2010\x64_SP2" />
      
<OptionState Id="OptionID" State="absent" Children="force" />
      
<Setting Id="SETUP_REBOOT" Value="IfNeeded" />
      
<Command Path="%windir%\system32\msiexec.exe" Args="/i \\do-vs-app05\Office2010\x64_SP2\ProPlus.WW\ProPlusWW.msi" QuietArg="/q" ChainPosition="after" Execute="install" />

</Configuration>
LarryDAHAsked:
Who is Participating?
 
LarryDAHConnect With a Mentor Author Commented:
For some reason it just started working again on its own. Not sure what happened.
0
 
LarryDAHAuthor Commented:
Looking at the setup log file I found this error message

<snip>

LIS: finished parsing LIS package "{90140000-0019-0409-1000-0000000FF1CE}"
LIS: start parsing setup xml
LIS: finished parsing LIS package "{90140000-001B-0409-1000-0000000FF1CE}"
Product: PROPLUS
  AddOnGroup Culture: en-us
    AddOnId: WORD.EN-US
    AddOnId: OFFICE.EN-US
    AddOnId: PUBLISHER.EN-US
    AddOnId: OFFICE32.EN-US
    AddOnId: ACCESS.EN-US
    AddOnId: INFOPATH.EN-US
    AddOnId: ONENOTE.EN-US
    AddOnId: PROOFING.EN-US
    AddOnId: OUTLOOK.EN-US
    AddOnId: GROOVE.EN-US
    AddOnId: EXCEL.EN-US
    AddOnId: POWERPOINT.EN-US
Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office14.PROPLUS.
Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office14.PROPLUS.
Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office14.PROPLUS.
Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office14.PROPLUS.
Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office14.PROPLUS.
Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office14.PROPLUS.
Detecting Applications Qualified for Upgrade
No upgradable applications found
Parsing product config.xml file: \\do-vs-app05\Office2010\x64_SP2\ProPlus.WW\config.xml
Parsing config.xml at: \\do-vs-app05\Office2010\x64_SP2\ProPlus.WW\config.xml
Preferred product specified in config.xml to be: OFFICE14.PROPLUS
Error: Invalid product: OFFICE14.PROPLUS specified in config.xml when product PROPLUS has already been selected Type: 41::InvalidProductInConfigXml.

Error: \\do-vs-app05\Office2010\x64_SP2\ProPlus.WW\config.xml Type: 148::InvalidParsingOfConfigXml.

Error: \\do-vs-app05\Office2010\x64_SP2\ProPlus.WW\config.xml Type: 148::InvalidParsingOfConfigXml.

Showing parent-less message Title: 'Setup Error', Message: 'The setup configuration file \\do-vs-app05\Office2010\x64_SP2\ProPlus.WW\config.xml is not valid.  Verify this file is formatted correctly and run setup again.'
Message returned: 1
0
 
McKnifeCommented:
Try and build a new config file.
Take the most simple one for a test.
0
 
LarryDAHAuthor Commented:
Problem solved itself, not sure why.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.