client has initiated asynchronous policy execution

Hi,

We just upgraded to Management Suite 9.60.0.244

When I try to distribute an exe file I get this message and return code 1354.

There is also an exclamation mark on the task and when I start it is possible to restart direcly after. Just as it is not really run?

The file gets copied to the client machine but the file is not executed.

I have tried to run it both silently and with a progress bar but nothing happends.

The log file does not tell me anything I manage to understand.

I have seen this happen to others but no solution how to solve this.

This is found in the sdclient_taskxxx file

The file is distributed from server1

Wed, 15 Oct 2014 07:53:03 ******* sdclient starting to process task *******

Wed, 15 Oct 2014 07:53:03 Task id to process: 512

Wed, 15 Oct 2014 07:53:03 Command line: /policyfile="C:\ProgramData\LANDesk\Policies\CP.512.RunNow._lIW0e3L0PG&#47vd8TIqNKU9OBgrGU=.xml"

Wed, 15 Oct 2014 07:53:03 File (\\server1\app\Landesk distribution\Microsoft\Patches\kb2878218\mso2010-kb2878218-fullfile-x86-glb.exe) is not in cache

Wed, 15 Oct 2014 07:53:03 The nostatus flag has NOT been set.

Wed, 15 Oct 2014 07:53:03 Core name 'server2' obtained from active task list

Wed, 15 Oct 2014 07:53:03 Sending task status, cmd line -coreandip=server2 -taskid=512 -retcode=229392444 "-ldap=CN=name,OU=IT,OU=HQ,OU=Con,OU=Users,OU=Company,DC=server1,DC=local" -pkgid=367

Wed, 15 Oct 2014 07:53:04 About to call DownloadFiles (1 files) with these settings:

Wed, 15 Oct 2014 07:53:04 m_allowedBandwidthWAN: 25

Wed, 15 Oct 2014 07:53:04 m_allowedBandwidthLAN: 75

Wed, 15 Oct 2014 07:53:04 m_maxDiscoveryThreads: 1430663218

Wed, 15 Oct 2014 07:53:04 m_discardPeriodSeconds: 604800

Wed, 15 Oct 2014 07:53:04 m_preserveDirectoryStructure: 1

Wed, 15 Oct 2014 07:53:04 m_bUseWanBWForPush: 0

Wed, 15 Oct 2014 07:53:04 m_bSynchronize: 0

Wed, 15 Oct 2014 07:53:04 Allowed download methods(m_downloadControl):

Wed, 15 Oct 2014 07:53:04 PeerOneSource

Wed, 15 Oct 2014 07:53:04 Peer

Wed, 15 Oct 2014 07:53:04 Source

Wed, 15 Oct 2014 07:53:04 m_preferredServerControl: AttemptPreferredServer

Wed, 15 Oct 2014 07:53:08 The nostatus flag has NOT been set.

Wed, 15 Oct 2014 07:53:08 Core name 'server2' obtained from active task list

Wed, 15 Oct 2014 07:53:08 Sending task status, cmd line -coreandip=server2 -taskid=512 -retcode=229392258 "-ldap=CN=name,OU=IT,OU=HQ,OU=Con,OU=Users,OU=Company,DC=server1,DC=local" -pkgid=367

Wed, 15 Oct 2014 07:53:09 ExpandEnvironmentVariables Result:

Wed, 15 Oct 2014 07:53:09 The nostatus flag has NOT been set.

Wed, 15 Oct 2014 07:53:09 Core name 'server2' obtained from active task list

Wed, 15 Oct 2014 07:53:09 Sending task status, cmd line -coreandip=server2 -taskid=512 -retcode=229392406 "-ldap=CN=name,OU=IT,OU=HQ,OU=Con,OU=Users,OU=Company,DC=server1,DC=local" -pkgid=367

Wed, 15 Oct 2014 07:53:11 LSWD or Executable Client Thread

Wed, 15 Oct 2014 07:53:11 PackagePath:             [\\server1\app\Landesk distribution\Microsoft\Patches\kb2878218\mso2010-kb2878218-fullfile-x86-glb.exe]

Wed, 15 Oct 2014 07:53:11 Processing generic executable

I guess it has something to do with the delivery method? If I check Agent settings in old sheduled tasks I can see they refer to my earlier configured delivery method. In my new task it is default set to  "keep agent's current settings" and it is not possible to find my earlier created delivery methods.

I really would appreciate any help. :-)