Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter >
> 
> 
Office 2013 Package Fails to Install

Answered Office 2013 Package Fails to Install

  • Wednesday, December 26, 2012 7:19 AM
     
     
    Sign In to Vote
    0

    I am trying to deploy Office 2013 Professional Plus via SCE, using config.xml as the answer file, but I am getting this failure:

    2012-12-21 13:32:04:118 5832 f20 Handler   : WARNING: Command line install of ""C:\Windows\SoftwareDistribution\Download\Install\setup.exe" " took too long (more than 16 hours) and was stopped.
    2012-12-21 13:32:04:118 5832 f20 Handler   : WARNING: Exit code = 0x80242007
    2012-12-21 13:32:04:118  992 17ec AU >>##  RESUMED  ## AU: Installing update [UpdateId = {7A1E75E4-67CA-4D36-A828-15C9F8F51459}]
    2012-12-21 13:32:04:118 5832 f20 Handler :::::::::
    2012-12-21 13:32:04:118  992 17ec AU   # WARNING: Install failed, error = 0x80242007 / 0x80242007
    2012-12-21 13:32:04:118 5832 f20 Handler ::  END  ::  Handler: Command Line Install
    2012-12-21 13:32:04:118  992 17ec Shutdwn InstallAtShutdown got install progress. 

    I have also tried Office 2013 Enterprise using an MSP answer file as a troubleshooting measure and got a similar failure.

    The files are being downloaded from the SCE server and copied to SoftwareDistribution\Download\Install.

    If I attempt to install Office manually from the same distribution point, it succeeds and uses the instructions in config.xml.  It does prompt me with the choice of Upgrade or Customize, but other than that the install completes without interaction.

    Does anyone have an idea why this might be failing?

     

All Replies

  • Wednesday, December 26, 2012 10:41 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hello,

    I'm not sure if it is supported to deploy Office 2013 with SCE 2010. Just for your reference, here are some articles about using SCCM 2012 to deploy Office 2013:

    Deploying Office 2013 using ConfigMgr 2012 (Part 1)
    http://myitforum.com/myitforumwp/2012/09/13/office-2013-part-1/

    Deploying Office 2013 with SCCM 2012 SP1 Beta (Part 2)
    http://myitforum.com/myitforumwp/2012/09/14/office-2013-part-2/

    Please check if any step in the articles could help. I'll do some further research on this issue and keep you updated later.

    Thanks,

    Yog Li
    TechNet Community Support

     
  • Thursday, December 27, 2012 3:39 AM
     
     
    Sign In to Vote
    0

    Thanks for the reply.  I cannot follow the steps in the article to solve my problem because the /admin option can only be used with the Enterprise version of Office 2013.  In fact I'm surprised that the person who wrote the article used the MSDN download because currently only retail versions are available there.

    In my test lab, I'll need to use the TechNet or MSDN versions, so that will require using config.xml as the answer file, since it will not be the Enterprise version.  We have a volume license, but I can't really use that media for my test lab.

     
  • Friday, December 28, 2012 9:04 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hello,

    Did you check the WindowsUpdate.log file on the problematic computers? Any error message can be found? And what is the Operating System? I had seen a simialr issue of deploying Office 2010 using SCE 2010:

    Unable to deploy Office 2010 via SCE 2010
    http://social.technet.microsoft.com/Forums/en-US/systemcenterdevelopment/thread/3f49639f-4ea8-406f-94a2-0a0490b36855#2dd51c24-d114-4e5e-b452-8d56923aa220

    The issue was resolved by a updata package in the following KB article. Please check if it helps in this scenario:

    An update has been released to resolve issues where System Center Essentials updating Windows 7 SP1-based computers with locally published content may fail with error 0x80070570
    http://support.microsoft.com/kb/2607070

    Furthermore, SCE 2010 is not in the list of Deployment methods for Office 2013. Perhaps you need another method to deploy Office 2013 in the list below:

    Deployment methods for Office 2013
    http://technet.microsoft.com/en-us/library/ee624360.aspx

    Thanks,

    Yog Li
    TechNet Community Support

     
  • Saturday, December 29, 2012 6:33 AM
     
     
    Sign In to Vote
    0

    Hi -

    I posted the error from the Windows Update log at the beginning of the thread: Basically it's "Install failed, error = 0x80242007".

    I had already seen the articles about Window 7 SP 1 and application installation failures, but I think I read that the newer SCE client resolves that issue.  I can try installing 2607070, but I think it will not be applicable.

    Once I confirm that, I'll try deploying Office 2010 as a troubleshooting measure, since we know that is supported.

    Thanks.

     
  • Sunday, December 30, 2012 12:42 AM
     
     
    Sign In to Vote
    0

    I confirmed that 2607070 is not needed.  When I try to install it, I get the message "Install is not needed since Windows Update Agent is already installed."  So the newest version of WUA must include the fix.

    I just learned that the error code I get simply means that the installer is hung up.  I mentioned that when I installed manually from the downloaded files, it prompts me with the choice of Upgrade or Customize.  This made me wonder whether or not my config.xml file is complete.  Anyone know if I'm missing something that is needed for a silent (upgrade) install?  Here are the contents of the file:

    <Configuration Product="ProPlusr">

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

     <USERNAME Value="John Doe" />

     <USERINITIALS Value="JD" />

     
     <COMPANYNAME Value="MyCompany" />
     
     <PIDKEY Value="xxxxxxxxxxxxxxxxxxxxxxxxxx" />

     
     <!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->
     
     <!-- <LIS CACHEACTION="CacheOnly" /> -->
     
     <!-- <LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" /> -->
     
     <!-- <DistributionPoint Location="\\server\share\Office" /> -->
     
     <!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->
     
     <!-- <Setting Id="SETUP_REBOOT" Value="IfNeeded" /> -->
     
     <!-- <Command Path="%windir%\system32\msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> -->

    </Configuration>

     
  • Thursday, January 03, 2013 7:41 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hello,

    About using and configuring the config.xml file, please refer to:

    config.xml file
    http://technet.microsoft.com/en-us/library/cc179195.aspx

    Besides, I would suggest you using the Office Forum in this scenario:

    TechCenter > Microsoft Office Forums
    http://social.technet.microsoft.com/Forums/en-US/category/officeitpro

    Thanks,

    Yog Li
    TechNet Community Support

     
  • Tuesday, February 26, 2013 2:37 AM
     
     
    Sign In to Vote
    0

    The problem I've been describing was for trying to get SCE to deploy Office 2013 in a test environment.  I had just two computers in the group which was to get the package installed.  Apparently, the problem was a lack of disk space, because I was able to deploy it successfully after restoring images of the machines to larger partitions.  One of them was down to about 2 GB and the other was down to about 4 GB of free space.  Even though there was that much disk space left after downloading the package, it must actually require quite a bit of free space, possibly because earlier version of Office was already installed(?).

    So, I guess this proves that Office 2013 can be deployed via SCE, which is what one would expect.  In my case it was the Pro Plus version using config.xml as the answer file.