This content has been marked as final. Show 7 replies
XTrace support is enabled by creating DWORD values under the XTrace registry key:
These DWORD values need to be set to a non-zero value. Each application has it’s own unique value, these are listed in the “XTrace Enabled Applications” section of this document.
The name of the XTrace log is the value name with a .xlg extension. This log file will show up in the same directory as the application that is being traced.
Example, to enable XTrace support for the local task API, the ltapi.dll, file it would be necessary to create the XTrace registry key, as outlined above. Typically the key will exist through LANDesk but the XTrace key will need to be created. Once the key is created, create a DWORD value named “ltapi” and set it to 1. Now when an application such as the local scheduler loads and uses ltapi.dll an ltapi.xlg file will be created.
Below is an example of common xtrace functions. Just copy and paset to a *.reg file and enable the entries you want.
Windows Registry Editor Version 5.00
Thanks for your reply. I had managed to sort this out.
But the *.xlg file does not give me much info to work on.
I have attahced for your review.
The issue i have is that my polices install ok but the status is not being updated is say pending even when the install is complete.
Any Suggestions or advice
sdclient.xlg 241 bytes
I have set this up as per attched
But not sure what you should see on the sdclient.xlg file
You mention check the status as below
Check the sdclient log to make sure the status is being sent by sdclient.
All that appears in this file is the following:
01/06/2009 15:58:19.782 280 308 xtrace.c 432 Start of log for process C:\Program Files\LANDesk\LDClient\policy.client.invoker.exe
01/06/2009 15:58:19.782 280 308 xtrace.c 433 process log file C:\Program Files\LANDesk\LDClient\sdclient.xlg
01/06/2009 16:16:42.090 280 308 xtrace.c 432 Start of log for process C:\Program Files\LANDesk\LDClient\policy.client.invoker.exe
01/06/2009 16:16:42.090 280 308 xtrace.c 433 process log file C:\Program Files\LANDesk\LDClient\sdclient.xlg
01/06/2009 16:42:13.211 252 320 xtrace.c 432 Start of log for process C:\Program Files\LANDesk\LDClient\policy.client.invoker.exe
01/06/2009 16:42:13.211 252 320 xtrace.c 433 process log file C:\Program Files\LANDesk\LDClient\sdclient.xlg
01/06/2009 16:48:17.595 252 320 xtrace.c 432 Start of log for process C:\Program Files\LANDesk\LDClient\policy.client.invoker.exe
01/06/2009 16:48:17.595 252 320 xtrace.c 433 process log file C:\Program Files\LANDesk\LDClient\sdclient.xlg
01/06/2009 16:48:33.183 252 320 xtrace.c 432 Start of log for process C:\Program Files\LANDesk\LDClient\policy.client.invoker.exe
01/06/2009 16:48:33.183 252 320 xtrace.c 433 process log file C:\Program Files\LANDesk\LDClient\sdclient.xlg
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.
I have attached alert log if this helps
alert.log 58.7 K
Wierd. Is this happening on all machines? I have never seen a 406 response from the web service. If happening on all machines, try resetting IIS. If only on a few machines, you may have an incomplete agent install, see this article http://community.landesk.com/support/docs/DOC-4449.
Error: 406 - Client browser does not accept the MIME type of the requested page.
Configured the IUSR account to have Full Control to the ldmain\sdstatus folder on the core.
LDMain is the Managementsuite dir.