Issue
After scheduling a repair task or policy, clients complete with a status message of “Successful” a result of "No Patches Available"
Cause
This is caused by patches in the repair task not being detected as needed on the client. Patches can only be applied if the vulnerability definition being scanned for shows the computers as affected.
Typically this is because a security scan has not been run recently.
Resolution
- Make sure the vulnerability is in the Scan folder in the Patch Manager window.
- Run a Security Scan, verify that the Distribution and Patch Settings are configured to scan for the type of definition desired. (vulnerability, LANDesk update, etc.)
- Verify that the scan completed successfully.
- Add the machine(s) to the repair task and restart the task.
Alternatively, when repairing against a group of definitions in Security and Patch Manager, both the Scan and Repair take place during the repair job
──────────────────────────────────────────────────────────────────────────────
This issue can also be indicative of a failure for the Core Server to access the database to get the patch information. This is typically done through the GetAllPatches web call from client to core. The core then generates an XML that gets downloaded to the client that contains the data about the patches that need to be installed. Failures to parse the XML on the client can cause the issue as well.
──────────────────────────────────────────────────────────────────────────────
The following details this issue:
Getting errors in the vulscan log that reflect:
Warning: AddPatchesToPatchList - Failed to parse xml data or there were no patches 0x80004005
No patches found for vulnerability="Vulnerability ID". Returning PATCH_NO_PATCHES_AVAILABLE
Cause
This is due to an incompatible Vulscan.dll version causing the .XML data for the patch information to be parsed incorrectly.
After the Vulnerability Scanner has run on a client, it will report back the vulnerabilities found to the server. If autofix is enabled, or the vulscan task is a repair job, it will also request the corresponding patch details from the core server.
An .XML file containing the patch data will then be downloaded to the client.
Typically this .XML file will have a name like the following:
If repairing against a group: GetPatchesForGroup.CoreNameAndRevision.patchlist.xml
If repairing a particular vulnerability: GetPatchesForVulnerability.PatchName.CoreNameAndRevision.patchlist.xml
The client then attempts to parse this XML and pass the information over to the Software Distribution portion of the repair process.
Resolution
Check the Vulscan.dll version on the core in your LDLogon directory. If the DLL version is 9.0.4.6 then you will need to replace it with the 9.0.3.76 DLL found in your SP3 install directory or you can contact support and we can send you the proper Vulscan.dll.