1 Reply Latest reply on Jan 14, 2014 10:11 AM by sterling22

    Stuck Tasks - Task Queued - Ghost Tasks

    Rookie

      We have machines that are perpetually trying to run an old policy based task. Problem is that the task doeesn't exist anymore in LANDesk. Is there somewhere else we can look for this task to remove it permanently?

       

      Example Task 2146 shows up in the SDClient logs on a good amount of computers. If I go into Scheduled Tasks and look up that Task ID it doesn't show up.

       

      SDCLIENT LOG

      Thu, 09 Jan 2014 09:35:12 FlushClientTaskQueue: queue is empty

      Thu, 09 Jan 2014 21:07:47 ExpandEnvironmentVariables Result: /s

      Thu, 09 Jan 2014 21:07:47 Cannot start sdclient for task 5845, the task 2146 is being processed on the client

      Thu, 09 Jan 2014 21:07:47 bind or column index out of range

      Thu, 09 Jan 2014 21:07:47 Cannot start sdclient for task 5845, the task 2146 is being processed on the client

      Thu, 09 Jan 2014 21:07:47 bind or column index out of range

       

      task2146.png

        • 1. Re: Stuck Tasks - Task Queued - Ghost Tasks
          sterling22 SupportEmployee

          This task is being called from the clients database (.db3) and is not being cleared after being run.  You can rebuild that clientside .db3 file which will force it to re-sync with the core as to what policies are actively being broadcast from the core so it cleans up any rogue tasks that didn't clear properly.  Here is the process we run to rebuild the .db3 file on the client.  If you take this and copy it into a managed script under the [MACHINES_NT] section you can use sofware distribution to deliver the script to your clients and it will rebuild the .db3 or you can do these steps manually on a client to rebuild the .db3 file.  

           

          REMEXEC1=cmd /c del /f /q "%LDMS_CLIENT_DIR%\sdclient.tasks.xml"

          REMEXEC2=cmd /c del /f /q "%LDMS_CLIENT_DIR%\..\Shared Files\cbaroot\alert\queue\internal*.xml"

          REMEXEC3=cmd /c net stop "LANDesk Policy Invoker"

          REMEXEC4=cmd /c del /f /q "c:\Documents and Settings\All Users\Application Data\LANDesk\ManagementSuite\Database\*.db3*"

          REMEXEC5=cmd /c del /f /q "c:\programdata\LANDesk\ManagementSuite\*.db3*"

          REMEXEC6=cmd /c "%LDMS_CLIENT_DIR%\clientdbutil.exe" /create

          REMEXEC7=cmd /c net start "LANDesk Policy Invoker"

          1 of 1 people found this helpful