Quantcast
Channel: LANDESK User Community : All Content - Software Distribution
Viewing all articles
Browse latest Browse all 766

How to troubleshoot policy status reporting

$
0
0

1. On the core server navigate to c:\program files\landesk\managementsuite directory.

 

2. Open the apmservice.ini and add a logging section and the the following value:
Keepevents=on

 

Should look like:

[Logging]

Keepevents=on

 

3. Stop and restart the APM service
Verify that the ldmain\sdstatus\stored directory was created.  If the stored directory does not get created.  Please create it.

 

4. Enable XTrace for sdclient

 

5. Rerun the policy or detached task

 

6. Check the sdclient log to make sure the status is being sent by sdclient.

 

7. Verify that the status XML file was forwarded by the alert service by checking the alert.log in the %ProgramFiles%\landesk\shared files folder. This log should list the status for the HTTP post to the core server.

 

Should look something like:

 

2009-03-03 22:30:10(5252-5544) alert.exe:Processing alert internal.192_168_0_15.swd_sdclient.status instance
  2009-03-03 22:30:11(5252-5544) alert.exe:Alert transmitted to http://LANDesk.Gateway@192.168.0.15/incomingdata/postcgi.exe?prefix=sdstatus\&suffix=.swd.xml

 

8. Check the IIS log on the core for the HTTP POST results. Verify event is in the stored policy events ldmain\sdstatus\stored. Also verify that the event was not put into the badstatus directory (Ldmain\sdstatus\badstatus).

 

9. Check APMStatusUpdateHandler.exe.log for errors.  (LDMS 9.0sp2 and later)

 

10. Check the version of the Core Server. The latest support packs must be installed. See Community article 1001.


Viewing all articles
Browse latest Browse all 766

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>