8 Replies Latest reply on Jul 17, 2014 7:54 PM by NeoIsTaken

    Failed, task handler exception

    Rookie

      I was deploying a scheduled task, that was created by using a scheduled template.  Initial deployment was to about 7 machines.  That went OK.   At that point I added an additional 22 machines that needed to receive the deployment.

       

      Now anytime I run the task, it states Failed, task handler exception.  Does anyone know how to get past this error?  I have already tried deleting and recreating the scheduled task.

       

      Any ideas?

        • 1. Re: Failed, task handler exception
          phoffmann SupportEmployee

          Context and such would be helpful here.

           

          What kind of task are you scheduling? Are we talking provisioning here, or software distribution, or something else?

           

          Also, what version of LANDesk are you on, what service pack do you have?

           

          - Paul Hoffmann

          LANDesk EMEA Technical Lead

          • 2. Re: Failed, task handler exception
            Rookie

            LANDesk Management Suite version 8.80.0.249

             

            The task is a scheduled template from the "operating system deployment" tab.  It contains a few packages that are chained together.

             

            The whole process worked fine on about 7 machines.  Without making any changes to any components, only adding machines to the scheduled task, the task handler exception appears.

            • 3. Re: Failed, task handler exception
              Rookie

              I just submitted a landesk support case for it.

              • 4. Re: Failed, task handler exception
                Rookie

                One of the machines the software package was being deployed to, would not resolve.  When I removed this PC from the list the scheduled task responded normally.

                • 5. Re: Failed, task handler exception
                  Rookie

                  Solved via landesk support ticket.

                  • 6. Re: Failed, task handler exception
                    Rookie

                    Can you (or anyone) elaborate anymore on this? I am seeing this error in my environment as well.

                     

                    Trying to repair a Custom Definition as a scheduled task to three machines.

                    • 7. Re: Failed, task handler exception
                      phoffmann SupportEmployee

                      After a bit of digging, I've found the relevant case (if needed - case ref # 488774 to save future searches).

                       

                      The solution in that particular case was to remove devices that didn't have an IP (thus couldn't be resolved).

                       

                      The log that showed the problem was the "prov_schedule.exe.log".

                       

                      In particular, the line that indicated the problem was one such as:

                       

                      2/18/2010  1:46:23 PM : Prod(templateIdn:958), deviceIdn:240, Unable to  resolve  the IP address.  Using IP:  instead of Host:N02742.

                       

                      So you'd need to check in the COMPUTER table (or via LANDesk query) which device had a DEVICE_IDN of 240 and remove that.

                       

                      Since you're trying to deal with custom definitions, I doubt you're using provisioning. How exactly are you doing this?

                       

                      If this is going through policies that's one set of logs - another set of logs would be necessary to be looked at (the CUSTJOB logs in this case).

                       

                      So it's a bit more tricky, and depends on what exactly you're doing and how, so you may wish to get in touch with support as the details may be different for you whilst the general symptoms are similar, if that makes sense .

                       

                      - Paul Hoffmann

                      LANDesk EMEA Technical Lead

                      • 8. Re: Failed, task handler exception
                        Specialist

                        Just to add another solution to an old post.

                        Our resolution was the original template was deleted via a cut and past. This changed the ID of the template causing an already scheduled job to throw this error