1 Reply Latest reply on Apr 15, 2015 10:10 AM by masterpetz

    Asyncronisation

    Specialist

      Got an asyncronsation problem for lot of push task. Can't seem to find a common denominator to see what is stuck on the computer or server. Have rebooted, reinstalled agent stopped processes, stopped services but can't find the point what the computer is waiting for.

      04/15/2015 10:40:51 INFO  14088:1     RollingLog : Core has changed, resetting the core language cache

      04/15/2015 10:40:51 INFO  14088:1     RollingLog : Getting core language for Key:CurrentLanguage Language:ENU

      04/15/2015 10:40:51 INFO  14088:1     RollingLog : Getting core language for Key:LegacyLanguage Language:ENU

      04/15/2015 10:43:13 INFO  21748:1     RollingLog : TaskHandlerProxy: C:\Program Files\LANDesk\ManagementSuite\PolicyTaskHandler.exe /TASKID=5318

      04/15/2015 10:43:13 INFO  21748:1     RollingLog : Core has changed, resetting the core language cache

      04/15/2015 10:43:13 INFO  21748:1     RollingLog : Getting core language for Key:CurrentLanguage Language:ENU

      04/15/2015 10:43:13 INFO  21748:1     RollingLog : Getting core language for Key:LegacyLanguage Language:ENU

      04/15/2015 10:44:09 INFO  21748:1     RollingLog : Task 5318 exitcode 16 has been translated to status 16

      04/15/2015 10:44:09 INFO  21748:1     RollingLog : Current language: ENU

      04/15/2015 10:44:09 INFO  21748:1     RollingLog : Using culture info: en-GB

      04/15/2015 10:44:12 INFO  21748:1     RollingLog : Resolving DAL scopes for user idn: 3

      04/15/2015 10:44:12 INFO  21748:1     RollingLog : UpdateTaskStatus: Setting task 5318 status to ASYNC_EXECUTION

      04/15/2015 10:44:12 INFO  21748:1     RollingLog : Sendingstatus mbsdk

       

      04/15/2015 10:40:51 INFO  14088:1     RollingLog : Core has changed, resetting the core language cache

      04/15/2015 10:40:51 INFO  14088:1     RollingLog : Getting core language for Key:CurrentLanguage Language:ENU

      04/15/2015 10:40:51 INFO  14088:1     RollingLog : Getting core language for Key:LegacyLanguage Language:ENU

      04/15/2015 10:43:13 INFO  21748:1     RollingLog : TaskHandlerProxy: C:\Program Files\LANDesk\ManagementSuite\PolicyTaskHandler.exe /TASKID=5318

      04/15/2015 10:43:13 INFO  21748:1     RollingLog : Core has changed, resetting the core language cache

      04/15/2015 10:43:13 INFO  21748:1     RollingLog : Getting core language for Key:CurrentLanguage Language:ENU

      04/15/2015 10:43:13 INFO  21748:1     RollingLog : Getting core language for Key:LegacyLanguage Language:ENU

      04/15/2015 10:44:09 INFO  21748:1     RollingLog : Task 5318 exitcode 16 has been translated to status 16

      04/15/2015 10:44:09 INFO  21748:1     RollingLog : Current language: ENU

      04/15/2015 10:44:09 INFO  21748:1     RollingLog : Using culture info: en-GB

      04/15/2015 10:44:12 INFO  21748:1     RollingLog : Resolving DAL scopes for user idn: 3

      04/15/2015 10:44:12 INFO  21748:1     RollingLog : UpdateTaskStatus: Setting task 5318 status to ASYNC_EXECUTION

      04/15/2015 10:44:12 INFO  21748:1     RollingLog : Sendingstatus mbsdk

       

      04/15/2015 09:05:32 INFO  19600:1     RollingLog : Task 5317 exitcode 16 has been translated to status 16

      04/15/2015 09:05:32 INFO  19600:1     RollingLog : Current language: ENU

      04/15/2015 09:05:32 INFO  19600:1     RollingLog : Using culture info: en-GB

      04/15/2015 09:05:36 INFO  19600:1     RollingLog : Resolving DAL scopes for user idn: 3

      04/15/2015 09:05:36 INFO  20872:1     RollingLog : Task 3476 run schedldapresolver.exe return 0

      04/15/2015 09:05:36 INFO  19600:1     RollingLog : UpdateTaskStatus: Setting task 5317 status to ASYNC_EXECUTION

      04/15/2015 09:05:36 INFO  19600:1     RollingLog : Sendingstatus mbsdk

       

       

      How to interpret Scheduler Task Status Codes and MAC_STATUS for a task

      Status 16 is Waiting, will retry failed machines

       

      Is there a way to find the thing it is waiting for ? This issues have been with me since the upgrade to 9.6 SP1