5 Replies Latest reply on Aug 25, 2017 7:16 AM by phoffmann

    LANDESK Package Deployment Failures?

    Swatto Rookie

      Hello all,

       

      We have an inconsistent package deployment issue where sometimes packages fail to install on client machines - this can be during OS provisioning or during a scheduled task deployment.  We use UNC paths to distribute all our LANDESK packages as IIS can sometimes have issues with certain file types that it does not recognise.  This is what we see in the log files:

       

      The log file gets spammed with this:

       

      Mon, 31 Oct 2016 10:15:30 CPolicyStatus::ReadFromFile: failed MyXML::ParseFile

      Mon, 31 Oct 2016 10:15:30 CPolicyStatus::ReadFromFile: failed MyXML::ParseFile

      Mon, 31 Oct 2016 10:15:30 CPolicyStatus::ReadFromFile: failed MyXML::ParseFile

      Mon, 31 Oct 2016 10:15:30 CPolicyStatus::ReadFromFile: failed MyXML::ParseFile

       

      and then the failed package shows this in the log file:

       

      Mon, 31 Oct 2016 11:20:40 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 0 times

      Mon, 31 Oct 2016 11:20:40 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 1 times

      Mon, 31 Oct 2016 11:20:40 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 2 times

      Mon, 31 Oct 2016 11:20:40 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 3 times

      Mon, 31 Oct 2016 11:20:40 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 4 times

      Mon, 31 Oct 2016 11:20:40 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 5 times

      Mon, 31 Oct 2016 11:20:40 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 6 times

      Mon, 31 Oct 2016 11:20:40 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 7 times

      Mon, 31 Oct 2016 11:20:40 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 8 times

      Mon, 31 Oct 2016 11:20:41 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 9 times

      Mon, 31 Oct 2016 11:20:41 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 10 times

      Mon, 31 Oct 2016 11:20:41 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 11 times

      Mon, 31 Oct 2016 11:20:41 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 12 times

      Mon, 31 Oct 2016 11:20:41 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 13 times

      Mon, 31 Oct 2016 11:20:41 PushToDone: Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu was just downloaded but we failed to get hash 14 times

      Mon, 31 Oct 2016 11:20:41 Download Error: err=3, path=\\coreserver\Infrastructure\Packages\Internet Explorer 10\IE10_86\Windows6.1-KB2639308-x86.msu

      Mon, 31 Oct 2016 11:20:42 processing of package is complete, result -1918107543 (0x8dac0069 - code 105)

       

      I have tried the following:

       

      Resetting the package hash

      Re-replicating the package from the core to the preferred server

      Checked all share and NTFS security permissions to make sure they match the core

       

      Does anyone know what these things mean in the log files please?

       

      Strange thing is that packages do not fail when deployed from the core server itself - only when deployed from preferred servers.

       

      Any help would be greatly appreciated - I currently have a support request logged with LANDESK but have not had any useful information as to what these errors mean.

        • 1. Re: LANDESK Package Deployment Failures?
          michael.odriscoll SupportEmployee

          Hi Steve,

           

          Thanks for posting this to the Community.

           

          Did you discover a root cause for this issue? If so, please share with the Community, you might help somebody out.

           

          Michael

          • 2. Re: LANDESK Package Deployment Failures?
            brian.collins Rookie

            Michael,

            You probably got this fixed, however, may be this will help someone else.  We had this same issue because we moved the package around in the ldlogon folder and it also moved the ldcacheinfo folders.  Therefore, the hash was incorrect.  We had to delete all the ldcacheinfo folders underneath the package.  This can be daunting for a big package with lots of folders.  You can do the following to fix it.

             

            First get a listing of ldcachinfo folders into a text file from command line.

            dir /b /s *ldcacheinfo* > ldcachedinfo.txt

             

            Now create a batch file:

            *****************************************************************

            @echo off

             

             

            for /f "USEBACKQtokens=*" %%a in (ldcacheinfo.txt) do (

            echo %%a

            rmdir /q /s "%%a"

            )

            pause

            ******************************************************************

            • 3. Re: LANDESK Package Deployment Failures?
              phoffmann SupportEmployee

              If the hash is incorrect, you can right-click the package in the console & select "reset package hash" (this sort of stuff can happen if someone/something changes a / several file(s) on you after you saved & tried to deploy the package out).

               

              Here's a screenshot to guide you:

               

              That may be easier / useful to have in addition to the above approach.

               

              IMPORTANT NOTE -- when deleting files on the client-side cache, please remember to re-start the TMC (Targeted Multicast Service). It checks cached files upon start-up and in regular intervals (about every 10 minutes, if memory serves) -- since you've mass-deleted stuff, it's a good idea to force the re-check so the TMC "knows" about the file-deletions.

              • 4. Re: LANDESK Package Deployment Failures?
                brian.collins Rookie

                phoffman,

                Good morning and thank you for the suggestion.  We actually tried that first, however, since the ldcacheinfo folders were already there from where we moved it from before; It still used those to compare the files and therefore failed when comparing during the scheduled task run.

                • 5. Re: LANDESK Package Deployment Failures?
                  phoffmann SupportEmployee

                  Gotcha - yeah, if the "wrong" files are down already, not much you can do beyond what you did .