3 Replies Latest reply on Aug 17, 2010 8:21 AM by Ascott860

    Policy Based Task Stuck in Active Status

    zeetwoeight Apprentice

      Hi all,


      I've setup a Policy Based - Required - Run Once distribution for XP SP3.  The systems successfully get updated but in LDMS, the task status is showing Active - Software distribution task has been started.  Even after multiple reboot and rescans of the systems, the status of the task never changes.  As a result, some of the systems are 'unaware' of having had the installation completed and therefore, run the package multiple times.


      Anyone seen this before?  Any suggestions?



        • 1. Re: Policy Based Task Stuck in Active Status
          phoffmann SupportEmployee

          Could you specify which version of LANDesk you use and your patch level?


          It's possible that I've got another sighting of this in Europe ... not sure (hence the request for the info) ... certainly if there's 2 sightings of this then this would make it more likely that there's a genuine defect.


          Have you any idea about "when" this happens most likely? I.e. - if the Core / Database-server is under particular strain, is it more likely to happen? Does it also happen during "quiet" periods I/O wise (so not necessarily a performance / bottleneck problem)?


          Any regularities that have been observed would help...


          - Paul Hoffmann

          LANDesk EMEA Technical Lead

          • 2. Re: Policy Based Task Stuck in Active Status
            zeetwoeight Apprentice

            LDMS SP3


            There isn't any time that this really happens most likely.  I set it up yesterday and our server was not under any unusual load.  Today I have see three systems that started to get the policy a second time since the original policy distribution hasn't reported back as successfully completed.



            • 3. Re: Policy Based Task Stuck in Active Status
              Ascott860 Specialist

              LDMS 9 SP1. Machines stuck in active status, but do have the software installed. Usually happens when more then one policy is queued up to the machine.