6 Replies Latest reply on Apr 21, 2010 7:37 AM by tino_78

    Interpreting log to discover source of failure

    Apprentice

       

      I have an office 2007 exe package with an admin file, that I have set for a UNC path to the primary file, and to the msp file

       

       

      When I run it, i get a failure code of unknown status code.

       

       

      My delivery method is push and Standard Multicast distribution

       

       

       

       

       

      The log file is pasted below:

       

       

      Tue, 15 Jul 2008 17:29:32 Checking preferred server path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe instead of
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Tue, 15 Jul 2008 17:29:32 Path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe was redirected to
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Tue, 15 Jul 2008 17:29:32 File (
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe) is not in cache

      Tue, 15 Jul 2008 17:29:52 Checking preferred server path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe instead of
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Tue, 15 Jul 2008 17:29:52 Path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe was redirected to
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Tue, 15 Jul 2008 17:29:52 LSWD or Executable Client Thread

      Tue, 15 Jul 2008 17:29:52 PackagePath:     http://\\uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Tue, 15 Jul 2008 17:29:52 Checking preferred server path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe instead of
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Tue, 15 Jul 2008 17:29:52 Path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe was redirected to
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Tue, 15 Jul 2008 17:29:52 Checking recently used server path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe instead of
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Tue, 15 Jul 2008 17:29:52 Path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe was redirected to
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Tue, 15 Jul 2008 17:29:52 Processing generic executable

      Tue, 15 Jul 2008 17:30:03 Launched application '
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe' ('/adminfile "
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\updates\mgt-office12enterprise-bw edit.msp"') result 30066

      Tue, 15 Jul 2008 17:30:03 Installation result 80077572

      Tue, 15 Jul 2008 17:30:04 processing of package is complete, result -2146994830 (0x80077572 - code 30066)

      Wed, 16 Jul 2008 12:44:52 Checking preferred server path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe instead of
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Wed, 16 Jul 2008 12:44:52 Path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe was redirected to
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Wed, 16 Jul 2008 12:44:52 File (
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe) is cached locally

      Wed, 16 Jul 2008 12:44:52 Checking preferred server path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe instead of
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Wed, 16 Jul 2008 12:44:52 Path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe was redirected to
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Wed, 16 Jul 2008 12:44:54 Downloading file
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe (lbikJFps03025W+uWiPisQ==, 5)

      Wed, 16 Jul 2008 12:44:54 Downloading file 1 of 1 from '
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe'

      Wed, 16 Jul 2008 12:44:54 Checking preferred server path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe instead of
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Wed, 16 Jul 2008 12:44:54 Path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe was redirected to
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Wed, 16 Jul 2008 12:44:54 LSWD or Executable Client Thread

      Wed, 16 Jul 2008 12:44:54 PackagePath:     http://\\uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Wed, 16 Jul 2008 12:44:54 Checking recently used server path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe instead of
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Wed, 16 Jul 2008 12:44:54 Path
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe was redirected to
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

      Wed, 16 Jul 2008 12:44:54 Processing generic executable

      Wed, 16 Jul 2008 12:45:07 Launched application 'C:\Program Files\LANDesk\LDClient\sdmcache\SoftwareDistribution\Packages\OIT\Office2007\setup.exe' ('/adminfile "
      uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\updates\mgt-office12enterprise-bw-edit.msp"') result 30066

      Wed, 16 Jul 2008 12:45:07 Installation result 80077572

      Wed, 16 Jul 2008 12:45:07 processing of package is complete, result -2146994830 (0x80077572 - code 30066)

       

       

       

       

       

       

        • 1. Re: Interpreting log to discover source of failure
          ahe Expert

           

          Hello,

           

           

          does the installation account (Local System) can connect to this path?

           

           

          \\uncservepath.domain.com\SoftwareDistribution\Packages\OIT\Office2007\setup.exe

           

           

          You can check the permissions if you try to connect as "Local System" (net use...) and start your setup.exe, if the mapping is successful, s. link:

           

           

          How to open a command prompt running as Microsoft's "Local System" account

           

           

           

           

           

          Regards

          Axel

           

           

           

           

           

           

           

           

          • 2. Re: Interpreting log to discover source of failure
            Rookie

             

            short version:  we tried using the /adminfile method and didn't get far.. we ended up using the LIS.xml method and applying our patch w/ updates later in the script

             

             

            Couple of things about office.

             

             

            1.  Using the /adminfile is only good on initial first install.  You CANNOT use the /adminfile technique to reinstall!.  We had major problems with this when we had to go back and add a feature or reapply the oct settings we made using setup .exe /admin (launches oct/config wizard)

             

             

            2.  If you install like this, it looks like you don't use the "msocache" method where you setup all the files in msocache, then execute the install which uses the c:\msocache folder.  The beauty of this is self-REPAIRS, also your laptops can reinstall from LIS (local installation source) if there out and about and need a feature that you don't have installed... plus it's really fast and you can predeploy this way.. just search on msocache and you'll find out how to use this

             

             

            3. Our command line to install turned out to be file://fileserver/blah/blah/blah/setup.exe /config lis.xml.  This uses the CONFIG operator and reads the lis.xml file for a few config directions which sets up the cache I believe.  We later  execute c:\msocache\All Users\{90120000-0011-0000-0000-0000000FF1CE}-C\setup.exe  (see http://technet.microsoft.com/en-us/library/cc178956(TechNet.10).aspx)

             

             

             

            4.  Since we built the install using setup /admin which creates a bunch of msp's in the updates folder, we didn't want to keep doing that so we apply this statement for any additonal changes:

            A.  Copy \microsoft\office\12.xxxx\_patches\o2k7build_d.msp to the msocache\901...\

            B.  execute MSIexec /p o2k7build_d.msp

             

             

            So we run script a, then script b.. you'll find you'll want to throw things in there like pdf converter and perhaps the Getting started tutorials.

            Attached is the wise package code for our two executables which may or may not give you some ideas.

             

             

             

             

             

            • 3. Re: Interpreting log to discover source of failure
              Rookie

               

              ps.. if you followed all that, you would want to know what lis.xml contains ..

               

               

              only display level and liscacheaction are enabled.. everything else is commented out   ....< !

               

               

               

               

               

              <Configuration Product="ProPlus">

               

               

              <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="no" />

               

              <!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Professional Plus Setup(*).txt" /> -->

               

              <!-- <PIDKEY Value="BCDFGHJKMPQRTVWXY2346789B" /> -->

               

               

              <!-- <USERNAME Value="Customer" /> -->

               

              <!-- <COMPANYNAME Value="MyCompany" /> -->

               

              <!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->

               

              <LIS CACHEACTION="CacheOnly" />

               

              <!-- <SOURCELIST Value="
              server1\share\Office12;
              server2\share\Office12" /> -->

               

              <!-- <DistributionPoint Location="
              server\share\Office12" /> -->

               

              <!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->

               

              <!-- <Setting Id="Reboot" Value="IfNeeded" /> -->

               

              <!-- <Command Path="msiexec.exe" Args="/i
              server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> -->

               

               

              </Configuration>

               

               

              • 4. Re: Interpreting log to discover source of failure
                Apprentice

                Just as an update, there was something screwey going on with my test computer.  I used another computer and the install went just fine.  However, the advice given in these posts will be helpful down the line.

                • 5. Re: Interpreting log to discover source of failure
                  oku Apprentice

                  Hi Com,

                  just wanted to know if u can share what is causing this error, we have tested office 2007 deployment and deploy it to 3 machines, 2 succesfully installed and the other one have the same error like you, anyone  know why, check on the client sdmcache and all the files are already coped down.

                  • 6. Re: Interpreting log to discover source of failure
                    Rookie

                    One time same things happen to my office 2007 install (code 30066), it was the result of not enough space on the instalaltion drive on the client !!!

                    If it can help someone...