1 Reply Latest reply on May 28, 2013 3:07 PM by jbaits

    Problem running command with PackageBoot

    sysadminchris

      So I'm deploying Office 2013 Professional, and removing Office 2010 Home and Business.  Unfortunately, since Access isn't part of Office Professional 2013, the Office 2013 installer leaves access installed and it needs to be removed.  I have the following in PackageBoot (attached in pic).  My commands work fine if done manually. 

       

      I get the following error when trying to deploy this package, and I'd love to know what I'm doing wrong.

       

       

      2013-05-28    15:15:36:695    4432    1380    Handler    :: START ::  Handler: Command Line Install

      2013-05-28    15:15:36:813    4432    1380    Handler    :::::::::

      2013-05-28    15:15:36:939     968    10e0    Report    Uploading 4 events using cached cookie, reporting URL = http://server.local:8530/ReportingWebService/ReportingWebService.asmx

      2013-05-28    15:15:36:955    4432    1380    Handler      : Updates to install = 1

      2013-05-28    15:15:36:962     968    10e0    Report    Reporter successfully uploaded 4 events.

      2013-05-28    15:15:37:065    4432    1380    Handler    HandlerSecsInADay = 86400.

      2013-05-28    15:15:44:358    4432    1380    Handler      : WARNING: Command line install completed. Return code = 0x00000002, Result = Failed, Reboot required = false

      2013-05-28    15:15:44:484     968    1684    AU    >>##  RESUMED  ## AU: Installing update [UpdateId = {E4486761-5496-4C7F-AAC9-1E365A2E62A8}]

      2013-05-28    15:15:44:484     968    1684    AU      # WARNING: Install failed, error = 0x80070643 / 0x00000002

      2013-05-28    15:15:44:484    4432    1380    Handler      : WARNING: Exit code = 0x8024200B

      2013-05-28    15:15:44:595    4432    1380    Handler    :::::::::

      2013-05-28    15:15:44:713    4432    1380    Handler    ::  END  ::  Handler: Command Line Install

        • Re: Problem running command with PackageBoot
          jbaits

          Is configuninstall.xml in that same directory on all machines? I would include the xml file with the package and point the uninstaller at it from there. Also, are all the machines 64-bit running 32-bit installations? If not you may be better off making a script that detects architecture and runs the proper commands.