1 Reply Latest reply on Jan 20, 2017 8:13 AM by Justus.Niemeyer

    Software Deployment Failing Despite Reporting Success

    Justus.Niemeyer Apprentice

      Hello All,

       

      I've been having a problem today I haven't seen before. I'm installing an MSI package that I've deployed out 300+ times to a new machine I just built. The installation is appears to finish much to quickly, reports successful installation, but doesn't actually finish.

       

      Here is what the sdclient_task###.log looks like:

       

       

      Thu, 19 Jan 2017 15:37:17 ******* sdclient starting to process task *******

      Thu, 19 Jan 2017 15:37:17 Task id to process: 101

      Thu, 19 Jan 2017 15:37:17 Command line: /policyfile="C:\ProgramData\LANDesk\Policies\CP.101.RunNow._vtjUJdoq9BDe1ufUQSdhToxlSLc=.xml"

      Thu, 19 Jan 2017 15:37:17 The nostatus flag has NOT been set.

      Thu, 19 Jan 2017 15:37:17 Core name 'LandeskServer.domain.local' obtained from active task list

      Thu, 19 Jan 2017 15:37:17 Sending task status, cmd line -coreandip=LandeskServer.domain.local -taskid=101 -retcode=229392442 "-ldap=CN=username,OU=AdminS,DC=domain,DC=local" -pkgid=56

      Thu, 19 Jan 2017 15:37:17 File (http://LandeskServer/landesk/packages/RSA/AMAgent/RSAAuthClient.msi) is not in cache

      Thu, 19 Jan 2017 15:37:17 The nostatus flag has NOT been set.

      Thu, 19 Jan 2017 15:37:17 Core name 'LandeskServer.domain.local' obtained from active task list

      Thu, 19 Jan 2017 15:37:17 Sending task status, cmd line -coreandip=LandeskServer.domain.local -taskid=101 -retcode=229392444 "-ldap=CN=username,OU=AdminS,DC=domain,DC=local" -pkgid=56

      Thu, 19 Jan 2017 15:37:18 About to call DownloadFiles (1 files) with these settings:

      Thu, 19 Jan 2017 15:37:18 m_allowedBandwidthWAN: 50

      Thu, 19 Jan 2017 15:37:18 m_allowedBandwidthLAN: 75

      Thu, 19 Jan 2017 15:37:18 m_discardPeriodSeconds: 604800

      Thu, 19 Jan 2017 15:37:18 m_preserveDirectoryStructure: 1

      Thu, 19 Jan 2017 15:37:18 m_bUseWanBWForPush: 0

      Thu, 19 Jan 2017 15:37:18 m_bSynchronize: 0

      Thu, 19 Jan 2017 15:37:18 Allowed download methods(m_downloadControl):

      Thu, 19 Jan 2017 15:37:18 PeerOneSource

      Thu, 19 Jan 2017 15:37:18 Peer

      Thu, 19 Jan 2017 15:37:18 Source

      Thu, 19 Jan 2017 15:37:18 m_preferredServerControl: AttemptPreferredServer

      Thu, 19 Jan 2017 15:37:32 The nostatus flag has NOT been set.

      Thu, 19 Jan 2017 15:37:32 Core name 'LandeskServer.domain.local' obtained from active task list

      Thu, 19 Jan 2017 15:37:32 Sending task status, cmd line -coreandip=LandeskServer.domain.local -taskid=101 -retcode=229392444 "-message=11%" -pkgid=56

      Thu, 19 Jan 2017 15:37:37 The nostatus flag has NOT been set.

      Thu, 19 Jan 2017 15:37:37 Core name 'LandeskServer.domain.local' obtained from active task list

      Thu, 19 Jan 2017 15:37:37 Sending task status, cmd line -coreandip=LandeskServer.domain.local -taskid=101 -retcode=229392444 "-message=100%" -pkgid=56

      Thu, 19 Jan 2017 15:37:38 The nostatus flag has NOT been set.

      Thu, 19 Jan 2017 15:37:38 Core name 'LandeskServer.domain.local' obtained from active task list

      Thu, 19 Jan 2017 15:37:38 Sending task status, cmd line -coreandip=LandeskServer.domain.local -taskid=101 -retcode=229392258 "-ldap=CN=username,OU=AdminS,DC=domain,DC=local" -pkgid=56

      Thu, 19 Jan 2017 15:37:40 The item with id [] was detected and package install will not be processed

      Thu, 19 Jan 2017 15:37:40 RunPackageInstall: not install by detection

      Thu, 19 Jan 2017 15:37:40 processing of package is complete, result 0 (0x00000000 - code 0)

       

      It almost seems as though the log is trying to tell me the package already exists even though it doesn't. It also strikes me as odd that the id is blank. I searched around and found some less-than-helpful stuff regarding this that related to deleting all of the Policies in the ProgramData folder (which I have tried.)

       

      I should mention, there has been one change between the last time I successfully deployed this package and now. I have implemented the Landesk CSA into our environment. However, this machine is located within the local network, so I wouldn't assume it would be causing these kinds of issues.

       

      Any ideas?

       

      Thanks,

       

      Justus