10 Replies Latest reply on May 20, 2016 9:49 AM by phoffmann

    Management Suite 2016 - Scheduled Tasks are stuck at "Client has started processing task"   Return Code 1354

    Rookie

      Hi,

       

      We have just done a fresh install of Management Suite 2016 on Windows Server 2012 with a new database. I have begun packaging some of our applications and have run into a new issue I did not have with 9.6. All of my packages are getting stuck on active with a 1354 return code and a result note saying the "Client has started processing the task". The example below is a simple MSI distribution package which shows the issue. This issue is happening on all of our packages.

       

      Scheduled.PNG

       

      Task ID:

      Task ID.PNG

       

      Policy XML

      Policy XML.PNG

       

      <?xml version="1.0" encoding="utf-8"?>

      <ClientPolicy xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

        <PolicyInfo>

          <PortalInfo>

            <p>

              <Name>Title</Name>

              <Val>Google Chrome</Val>

            </p>

            <p>

              <Name>Description</Name>

              <Val>Google Chrome</Val>

            </p>

            <p>

              <Name>Category</Name>

              <Val>Browser</Val>

            </p>

            <p>

              <Name>CategoryID</Name>

              <Val>14</Val>

            </p>

            <p>

              <Name>ID</Name>

              <Val>28</Val>

            </p>

            <p>

              <Name>Size</Name>

              <Val>52396032</Val>

            </p>

            <p>

              <Name>Type</Name>

              <Val>MSI</Val>

            </p>

            <p>

              <Name>PublishedDate</Name>

              <Val>3/1/2016 9:23:40 AM</Val>

            </p>

            <p>

              <Name>Tags</Name>

              <Val>64 Bit,Microsoft Windows</Val>

            </p>

            <p>

              <Name>Logo</Name>

              <Val />

            </p>

            <p>

              <Name>ScreenShot_0</Name>

              <Val />

            </p>

            <p>

              <Name>ScreenShot_1</Name>

              <Val />

            </p>

            <p>

              <Name>ScreenShot_2</Name>

              <Val />

            </p>

            <p>

              <Name>ApplicationVendor</Name>

              <Val>Google</Val>

            </p>

            <p>

              <Name>EstDownloadTime</Name>

              <Val>5</Val>

            </p>

            <p>

              <Name>EstInstallTime</Name>

              <Val>5</Val>

            </p>

            <p>

              <Name>RebootExpected</Name>

              <Val>False</Val>

            </p>

            <p>

              <Name>TaskName</Name>

              <Val>Google Chrome - 2/26/2016 10:55:38 AM</Val>

            </p>

          </PortalInfo>

          <Mode>Required</Mode>

          <ItemType>SWD</ItemType>

          <TaskIdn>1104</TaskIdn>

          <LeaveInPortal>false</LeaveInPortal>

          <Interval>Once</Interval>

          <PolicyHash>S1PKtSSJ7NH8hC0GTw5P2lg2U/o=</PolicyHash>

          <TaskName>Google Chrome - 2/26/2016 10:55:38 AM</TaskName>

          <MultiTaskProtection>false</MultiTaskProtection>

          <TaskLastSavedDate>Tuesday, March 1, 2016 9:23:40 AM</TaskLastSavedDate>

          <PushTask>false</PushTask>

        </PolicyInfo>

        <RunInfo>

          <Settings>

            <p>

              <Name>IgnoreSubsequentAttempts</Name>

              <Val>False</Val>

            </p>

          </Settings>

          <IgnoreSubsequentAttempts>false</IgnoreSubsequentAttempts>

        </RunInfo>

      </ClientPolicy>

       


      SDCLIENT LOG

      • C:\Program Files (x86)\LANDesk\LDClient\Data\sdclient.log

       

      Tue, 01 Mar 2016 09:23:54 Core name 'Our Sever' obtained from the registry

      Tue, 01 Mar 2016 10:06:25

      Tue, 01 Mar 2016 10:06:25 CPolicyHistory::LoadHistoryDaysToKeep: Registry settings for task history maintenance mode (Days To Keep) is '5'

      Tue, 01 Mar 2016 10:06:25 PostInstallInventoryScan: Getting post package install inventory delay setting.

      Tue, 01 Mar 2016 10:06:25 PostInstallInventoryScan: Not running post package install inventory scan, the inventory scan delay value is out of range, min is 5, max is 60, current value is '-1'

      Tue, 01 Mar 2016 10:06:25 The nostatus flag has NOT been set.

      Tue, 01 Mar 2016 10:06:25 Core name 'Our Sever' obtained from the registry

      Tue, 01 Mar 2016 10:06:25 Sending task status, cmd line -coreandip=Our Sever -taskid=1104 -retcode=229638145 -complete -pkgid=28

       

      sdclient_task1104  

      • C:\Program Files (x86)\LANDesk\LDClient\Data\sdclient_task1104.log

      Tue, 01 Mar 2016 09:23:55 ******* sdclient starting to process task *******

      Tue, 01 Mar 2016 09:23:55 Task id to process: 1104

      Tue, 01 Mar 2016 09:23:55 Command line: /policyfile="C:\ProgramData\LANDesk\Policies\CP.1104.RunNow._chDj1tTzFaLrt2OsiRQH9ZQC0pM=.xml"

      Tue, 01 Mar 2016 09:23:55 The nostatus flag has NOT been set.

      Tue, 01 Mar 2016 09:23:55 Core name 'Our Sever' obtained from the registry

      Tue, 01 Mar 2016 09:23:55 Sending task status, cmd line -coreandip=Our Sever -taskid=1104 -retcode=229392442 "-ldap=CN=user,OU=Faculty&Staff,DC=ourdomain,DC=EDU" -pkgid=28

      Tue, 01 Mar 2016 09:34:02 File (\\ourserver\Deploy\Software\Google\googlechromestandaloneenterprise64.msi) is cached locally

      Tue, 01 Mar 2016 09:34:02 The nostatus flag has NOT been set.

      Tue, 01 Mar 2016 09:34:02 Core name 'Our Sever obtained from the registry

      Tue, 01 Mar 2016 09:34:02 Sending task status, cmd line -coreandip=Our Sever -taskid=1104 -retcode=229392444 "-ldap=CN=user,OU=Faculty&Staff,DC=ourdomain,DC=EDU" -pkgid=28

      Tue, 01 Mar 2016 09:44:04 About to call DownloadFiles (1 files) with these settings:

      Tue, 01 Mar 2016 09:44:04 m_allowedBandwidthWAN: 50

      Tue, 01 Mar 2016 09:44:04 m_allowedBandwidthLAN: 75

      Tue, 01 Mar 2016 09:44:04 m_discardPeriodSeconds: 604800

      Tue, 01 Mar 2016 09:44:04 m_preserveDirectoryStructure: 1

      Tue, 01 Mar 2016 09:44:04 m_bUseWanBWForPush: 0

      Tue, 01 Mar 2016 09:44:04 m_bSynchronize: 0

      Tue, 01 Mar 2016 09:44:04 Allowed download methods(m_downloadControl):

      Tue, 01 Mar 2016 09:44:04 PeerOneSource

      Tue, 01 Mar 2016 09:44:04 Peer

      Tue, 01 Mar 2016 09:44:04 Source

      Tue, 01 Mar 2016 09:44:04 m_preferredServerControl: AttemptPreferredServer

      Tue, 01 Mar 2016 09:44:06 The nostatus flag has NOT been set.

      Tue, 01 Mar 2016 09:44:06 Core name 'Our Sever' obtained from the registry

      Tue, 01 Mar 2016 09:44:06 Sending task status, cmd line -coreandip=Our Sever -taskid=1104 -retcode=229392444 "-message=100%" -pkgid=28

      Tue, 01 Mar 2016 09:44:06 The nostatus flag has NOT been set.

      Tue, 01 Mar 2016 09:44:06 Core name 'Our Sever' obtained from the registry

      Tue, 01 Mar 2016 09:44:06 Sending task status, cmd line -coreandip=Our Sever -taskid=1104 -retcode=229392258 "-ldap=CN=user,OU=Faculty&Staff,DC=ourdomain,DC=EDU" -pkgid=28

      Tue, 01 Mar 2016 09:54:39 ExpandEnvironmentVariables Result: /i /quiet /norestart

      Tue, 01 Mar 2016 09:54:39 MSI Client Thread

      Tue, 01 Mar 2016 09:54:39 PackagePath: [\\ourserver\Deploy\Software\Google\googlechromestandaloneenterprise64.msi]

      Tue, 01 Mar 2016 09:54:39 Execute Msiexec.exe with command Line: "Msiexec.exe"  /quiet /norestart /i "C:\Program Files (x86)\LANDesk\LDClient\sdmcache\Deploy\Software\Google\googlechromestandaloneenterprise64.msi" REBOOT=ReallySuppress

      Tue, 01 Mar 2016 09:55:55 MSI result DB50000

      Tue, 01 Mar 2016 09:55:55 Rebooting system if needed

      Tue, 01 Mar 2016 10:06:25 processing of package is complete, result 229638145 (0x0db00001 - code 1)

       

       

      PolicyTaskHandler.exe.log


      03/01/2016 09:23:43 INFO  13736:1     RollingLog : Core has changed, resetting the core language cache

      03/01/2016 09:23:43 INFO  13736:1     RollingLog : Getting core language for Key:CurrentLanguage Language:ENU

      03/01/2016 09:23:43 INFO  13736:1     RollingLog : Getting core language for Key:LegacyLanguage Language:ENU

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.ManagementSuite.Data.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\package.data.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.ManagementSuite.HPPowerSettings.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.ManagementSuite.HPBiosSettingsPolicy.Business.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.ManagementSuite.SecureEraseSettings.Business.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\AVBiz.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\patchbiz.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Current language: ENU

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Using culture info: en-US

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\PatchManagement.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.ManagementSuite.SoftwareDistribution.Business.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.PWM.Data.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\AlertBiz.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\PanelManager.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\UserManagement.Business.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\RCBehaviorBiz.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\CommonAgentSettingsProvider.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDESK.MDM.Console.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.PWM.Business.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\ManageLdappl.dll> returned True.  wasVerified: True

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : ***PolicyTaskHandler run options***

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : Accelerated push: [True]

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : Use DNS/WINS resolution for discovery: [True]

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : Wait for machines to finish: [False]

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : Maximum Push or Policy-supported push run time minutes: [15]

      03/01/2016 09:23:44 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : Verbose logging: [False]

      03/01/2016 09:23:46 INFO  13736:1     MDMConsole.MDMTaskHandler : MDMTaskHandler.FilterNodesAndProcess(): Called with 1 computer IDs, Task ID 1104

      03/01/2016 09:23:46 INFO  13736:1     MDMConsole.MDMTaskHandler : Queueing 0 devices to notify pipe.

      03/01/2016 09:24:07 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : PolicyTaskHandler finished processing task, setting task status to [PULL_AVAILABLE]...

        • 2. Re: Management Suite 2016 - Scheduled Tasks are stuck at "Client has started processing task"   Return Code 1354
          slatey Apprentice

          Did you guys check your LANDesk and LANDesk1 COM+ Objects? I had a similar issue on a brand new 9.6 core where every single package install (and remote control with a -5 can't auth error) would fail or rather go into:

                         "Client has initiated asynchronous policy execution" - Return Code 1354.

          Run PolicySync.exe

          02/25/2016 19:42:33 INFO 8864:1     RollingLog : ProcessUpgrade: Required policies need to be upgraded, performing upgrade...

          02/25/2016 19:42:40 INFO 8864:1     RollingLog : Request: Request policies

          02/25/2016 19:42:44 INFO 8864:1     RollingLog : Request: GetWebResponse ok

          02/25/2016 19:42:44 INFO 8864:1     RollingLog : Verify: failed, no signature

          02/25/2016 19:42:44 INFO 8864:1     RollingLog : Request: signature verification failed

          02/25/2016 19:42:44 INFO 8864:1     RollingLog : RunUpgrade: Upgrade done

          02/25/2016 19:42:45 INFO  8864:5 RollingLog : LoadLocalPolicyInfo: load local machine

          02/25/2016 19:42:45 INFO 8864:5     RollingLog : LoadLocalPolicyInfo: load user

          02/25/2016 19:42:45 INFO 8864:4     RollingLog : Request: Request policies

          02/25/2016 19:42:47 INFO 8864:4     RollingLog : Request: GetWebResponse ok

          02/25/2016 19:42:47 INFO 8864:4     RollingLog : Verify: failed, no signature

          02/25/2016 19:42:47 INFO 8864:4     RollingLog : Request: signature verification failed

          02/25/2016 19:42:47 INFO 8864:1     RollingLog : PolicySync: failed request

          02/25/2016 19:42:47 INFO 8864:1     RollingLog : Exit PolicySync.exe with code -3


           

          A quick Google led me to this:

          https://community.landesk.com/support/docs/DOC-24056

           

          And this as the solution: https://blogs.msdn.microsoft.com/distributedservices/2009/11/06/a-com-application-may-stop-working-on-windows-server-2008-when-the-identity-user-logs-off/

           

          So, I made two changes to the core server and restarted the COM+ objects:

           

          1. 1) GPedit.msc Comp Config>>Admin templates>>System>>User Profiles
            • Do not forcefully unload the user registry at logoff – ENABLED
          2. 2) On the COM+ applications under advanced I set Server Process Shutdown to Leave running when idle
          • 3. Re: Management Suite 2016 - Scheduled Tasks are stuck at "Client has started processing task"   Return Code 1354
            Rookie

            I made the changes suggested by Slatey even though we have no errors in our policy synch log. The changes unfortunately did not fix the issue. I figured it was worth a shot since they had a similar 1354 error code. We still have the result note saying the "Client has started processing the task" which is different from Slatey's result note.  Thank you for the suggested fix. All help is appreciated.


            Original Post Test Log of PolicySynch


            Run PolicySync.exe -taskid=1104

            03/01/2016 09:23:51 INFO  3128:1     RollingLog : Request: Request policies

            03/01/2016 09:23:52 INFO  3128:1     RollingLog : Request: GetWebResponse ok

            03/01/2016 09:23:52 INFO  3128:1     RollingLog : Request: Has 1 targeted policies

            03/01/2016 09:23:53 INFO  3128:1     RollingLog : HandleRunNow: has 1 run now policies

            03/01/2016 09:23:54 INFO  2072:1     RollingLog :

            Run PolicySync.exe /enforce

            03/01/2016 09:23:54 INFO  3128:1     RollingLog : Exit PolicySync.exe with code 0


            Today's test

            2016-03-04_11-56-12.png

            • 4. Re: Management Suite 2016 - Scheduled Tasks are stuck at "Client has started processing task"   Return Code 1354
              slatey Apprentice

              I may be barking up the wrong tree, but another couple of things to look at, even though you're not on 9.6, and the error message doesn't match exactly (but the code does):

               

              "Client has initiated asynchronous policy execution" - Return Code 1354

               

              How to troubleshoot tasks hung with a status of "Client has initiated asynchronous policy execution"

               

              Regards.

              • 5. Re: Management Suite 2016 - Scheduled Tasks are stuck at "Client has started processing task"   Return Code 1354
                Rookie

                I looked at both of those links previously before posting on the forum. They are very good but did not help with the issue. I do have an update to the issue though which is the software is installing correctly on the test machines but the console never gets updated and the job stays active with 1354 return code and a result note saying the "Client has started processing the task". So I guess the question is why is the job showing active in the console even though it is finished on the client.

                 

                Today's SDCLIENT log  (Showing job completed successfully)

                 

                , 04 Mar 2016 11:25:30 ******* sdclient starting to process task *******

                Fri, 04 Mar 2016 11:25:30 Task id to process: 1328

                Fri, 04 Mar 2016 11:25:30 Command line: /policyfile="C:\ProgramData\LANDesk\Policies\CP.1328.RunNow._GlnrAiISp94v5qVPIqi3qo9cCEM=.xml"

                Fri, 04 Mar 2016 11:25:31 The nostatus flag has NOT been set.

                Fri, 04 Mar 2016 11:25:31 Core name 'Our Server' obtained from the registry

                Fri, 04 Mar 2016 11:25:31 Sending task status, cmd line -coreandip=Our Server -taskid=1328 -retcode=229392442 "-ldap=CN=user,OU=Faculty&Staff,DC=ourdomain,DC=EDU" -pkgid=28

                Fri, 04 Mar 2016 11:35:38 File (\\Our Server\Deploy\Software\Google\googlechromestandaloneenterprise64.msi) is cached locally

                Fri, 04 Mar 2016 11:35:38 The nostatus flag has NOT been set.

                Fri, 04 Mar 2016 11:35:38 Core name 'Our Server' obtained from the registry

                Fri, 04 Mar 2016 11:35:38 Sending task status, cmd line -coreandip=Our Server -taskid=1328 -retcode=229392444 "-ldap=CN=user,OU=Faculty&Staff,DC=ourdomain,DC=EDU" -pkgid=28

                Fri, 04 Mar 2016 11:45:42 About to call DownloadFiles (1 files) with these settings:

                Fri, 04 Mar 2016 11:45:42 m_allowedBandwidthWAN: 50

                Fri, 04 Mar 2016 11:45:42 m_allowedBandwidthLAN: 75

                Fri, 04 Mar 2016 11:45:42 m_discardPeriodSeconds: 604800

                Fri, 04 Mar 2016 11:45:42 m_preserveDirectoryStructure: 1

                Fri, 04 Mar 2016 11:45:42 m_bUseWanBWForPush: 0

                Fri, 04 Mar 2016 11:45:42 m_bSynchronize: 0

                Fri, 04 Mar 2016 11:45:42 Allowed download methods(m_downloadControl):

                Fri, 04 Mar 2016 11:45:42 PeerOneSource

                Fri, 04 Mar 2016 11:45:42 Peer

                Fri, 04 Mar 2016 11:45:42 Source

                Fri, 04 Mar 2016 11:45:42 m_preferredServerControl: AttemptPreferredServer

                Fri, 04 Mar 2016 11:45:43 The nostatus flag has NOT been set.

                Fri, 04 Mar 2016 11:45:43 Core name 'Our Server' obtained from the registry

                Fri, 04 Mar 2016 11:45:43 Sending task status, cmd line -coreandip=Our Server -taskid=1328 -retcode=229392444 "-message=100%" -pkgid=28

                Fri, 04 Mar 2016 11:45:44 The nostatus flag has NOT been set.

                Fri, 04 Mar 2016 11:45:44 Core name 'Our Server' obtained from the registry

                Fri, 04 Mar 2016 11:45:44 Sending task status, cmd line -coreandip=Our Server -taskid=1328 -retcode=229392258 "-ldap=CN=user,OU=Faculty&Staff,DC=ourdomain,DC=EDU" -pkgid=28

                Fri, 04 Mar 2016 11:55:55 The item with id [google chrome] was detected and package install will not be processed

                Fri, 04 Mar 2016 11:55:55 RunPackageInstall: not install by detection

                Fri, 04 Mar 2016 11:55:55 processing of package is complete, result 0 (0x00000000 - code 0)

                • 6. Re: Management Suite 2016 - Scheduled Tasks are stuck at "Client has started processing task"   Return Code 1354
                  jhedelin Apprentice

                  Upgraded my LD 9.6 SP2 to Management Suite 2016 yesterday, having the same problem.

                  When i distribute a schedule task all my clients hangs at

                   

                  Client has started processing task (Code 1354)

                   

                  I think it has something with the new feature "Client certificate-based security" ?

                  If i check the PolicySync.exe.log file on a client that i have distributed the schedule task to i have found these messeges:

                   

                  03/10/2016 07:34:54 INFO  2064:1 RollingLog :

                  Run PolicySync.exe -taskid=3607

                  03/10/2016 07:34:54 INFO  2064:1 RollingLog : Request: Request policies
                  03/10/2016 07:34:55 INFO  2064:1 RollingLog : Request: GetWebResponse ok
                  03/10/2016 07:34:55 INFO  2064:1 RollingLog : Verify: failed, no signature
                  03/10/2016 07:34:55 INFO  2064:1 RollingLog : Request: signature verification failed
                  03/10/2016 07:34:55 INFO  2064:1 RollingLog : PolicySync: failed request
                  03/10/2016 07:34:55 INFO  2064:1 RollingLog : Exit PolicySync.exe with code -3

                   

                  Any suggestions? I have NOT uppgraded my server to: "Client certificate-based security" but i have approved all my new Landesk 10 cliens.

                  • 8. Re: Management Suite 2016 - Scheduled Tasks are stuck at "Client has started processing task"   Return Code 1354
                    Rookie

                    I took a look at the link and I did not have LANDeskComPlus local user in the Users group. I added it and did the rest of the suggestions but still am getting the same result after a reboot. I did not have the PolicySync.exe.log error before making these changes but took a shot anyway. Thank you for the suggested fix but I'm still looking.


                    Still active.PNG

                     

                    hu, 10 Mar 2016 09:32:37 Execute Msiexec.exe with command Line: "Msiexec.exe"  /quiet /norestart /i "C:\Program Files (x86)\LANDesk\LDClient\sdmcache\deploy\Software\VMWARE\VMware 12\VMwareWorkstation.msi" REBOOT=ReallySuppress
                    Thu, 10 Mar 2016 09:32:53 MSI result 8DB50643
                    Thu, 10 Mar 2016 09:32:53 CPolicyHistory::LoadHistoryDaysToKeep: Registry settings for task history maintenance mode (Days To Keep) is '5'
                    Thu, 10 Mar 2016 09:32:53 RunPackageInstall: stop on returncode=8db50643 of package=VMware 12
                    Thu, 10 Mar 2016 09:32:53 processing of package is complete, result -1917516221 (0x8db50643 - code 1603)

                     

                    As you can see above this job actually failed but it did not report it to the console. The console still says the job is Active. Even if the job is successful the console stays active.

                    • 9. Re: Management Suite 2016 - Scheduled Tasks are stuck at "Client has started processing task"   Return Code 1354
                      Rookie

                      Turns out the account I used for LANDesk was removed from the domain admins group. I have since put it back in and everything is now working. Thanks for all your help guys.

                      • 10. Re: Management Suite 2016 - Scheduled Tasks are stuck at "Client has started processing task"   Return Code 1354
                        phoffmann SupportEmployee

                        Since I just stumbled over this comment *puts on best practice hat*.

                         

                        Just to clarify:

                        • The COM+ components do NOT need a domain admin account
                        • In fact, the COM+ components "just" need a vanilla AD account (used to query AD / resolve users, etc)
                        • Theoretically, the LANDesk Scheduler account would be the only one approaching needing those privileges (and then only to RPC push agents out to devices, which should be a pretty rare occurence these days).
                        • The Scheduler is the "most privilege" requiring account (since this is the account we authenticate to shares to in order to calculate file hashes & so on).

                         

                        • There's really not much need for any domain admin-ery ...

                         

                        As an aside - I've added a comment to - Error: "Signature Verification Failed" from PolicySync.exe - since I've been playing around with LANDesk 2016 and using the secure www-service ... there's an easy gotcha around COM+ that I've fallen afoul of & wasted a few hours on. Hopefully my sharing the knowledge will prevent other folks from running into the same problem .

                         

                        Hope this helps.