1 Reply Latest reply on Dec 7, 2016 8:02 AM by michael.odriscoll

    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.