Troubleshooting Windows Patching
See the slide deck below for a guide to troubleshooting patching in Windows.
- Why a Windows Patch Analysis Job does not report a missing expected patch (user contribution)
- Why Windows Patch Analysis Job Results can conflict with 3rd-party Vendors (user contribution)
- Why a Windows Patch Analysis Job can report an unexpected patch as missing (user contribution)
- How to analyze Trace.txt generated by a Windows Patch Analysis Job (user contribution)
Debugging the Shavlik Downloader
To enable DEBUG logging, add the following text to appserver.cf file:
#Downloader debug log4j.logger.com.bladelogic.model.job.compliance.patch.ShavlikResult=DEBUG log4j.logger.com.bladelogic.app.util.DownloadServer=DEBUG
Incorrect patch payload
Shavlik downloads the following key files: hfnetchk.cab, pd4.cab and pd5.cab. To view the contents of these files, you can extract them and convert them to XML.
The following table presents common issues and the corresponding file to convert and review to troubleshoot each issue:
|Issue||File to convert and review|
|Payload is not shown. URL incorrect or incorrect payload is downloaded.||pd5.cab|
|Patches are not shown in analysis.|
This file also indicates the availability of products and the OS and SP level for each patch.
Turning on debug tracing for cl5.exe
To validate the payload, the Shavlik engine runs the cl5.exe tool on the target. If this tool is not working properly, you can turn on tracing on the target, using the following command:
CL5.exe 2097197 1 <Log Directory>
The customary value for maximum log size is 5000000. This command writes some values to the registry.
To turn off CL5 tracing, use the following command:
CL5.exe 2097197 0