Patch Scan Failed
Problem
Patch scanning starts during the documented scan scenarios but fails.
Cause
The firewall on the Patch Manager Plus server might block the data.
Resolution
Add the Patch Manager Plus port, 8020 by default, to the firewall exceptions list. In Windows, open Start → Run, enter firewall.cpl, open Exceptions, and click Add Port.
Other Error Codes
For a patch scan failure that persists after the applicable steps below, use the log-collection procedure. Confirm the scan type and resource error before repeating a repair.
For a Linux scan remark such as Failed due to incorrect meta files. Ensure that the vulnerability database is up to date. If still issue persist contact support with server and agent logs., verify the completed vulnerability DB update and Linux package-manager metadata results, then initiate a fresh patch scan. If the error remains after successful synchronization, collect the server and Linux agent logs. See database synchronization and Linux deployment diagnostics. Synchronization alone is not a guaranteed repair.
If a scan reports a resource download or extraction failure, record the resource filename, full error and failure time. A successful connectivity test does not confirm that the resource was transferred or extracted correctly.
For drvforceupdate.exe.gz extraction failed, record the complete extraction error and collect the affected agent diagnostic bundle using the persistent scan-failure procedure. If reinstalling the agent has already failed to resolve the issue, include that result rather than assuming another reinstall will repair it.
For Downloading dcpatchutils.dll.gz failed with error code : 404 or Downloading patch-scan-data.xml.gz failed with error code : 404, collect the requested resource URL, server and agent builds, and the Central Server or Distribution Server response and replication status. Resource names vary by scan implementation; use the file named in the actual remark rather than assuming every build requires the same legacy scan file. If the failure persists, collect the affected agent logs for Support.
Collect logs for a persistent patch scan failure
A green Agent Binaries result in the Agent Troubleshooting Tool does not confirm that a patch scan completed. Check the patch scan status and timestamps separately. For a scan that remains In Progress or times out, record the scan attempt and tool results and collect the diagnostic bundle below. Do not repeat a checksum or signature repair unless the scan reports that error.
- Record the affected computer, server and agent builds, scan time, resource filename and full error.
- Use the Agent Troubleshooting Tool to collect agent and patch scan logs, reproduce the failure and generate the diagnostic bundle.
- Share the bundle and scan evidence with Support. For an affected remote office, include the Distribution Server logs requested for that failure.
If the affected agent runs on the Central Server computer, identify that computer in the case. Collect its agent diagnostic bundle and the Central Server logs for the same failed scan. Record whether other endpoints can scan successfully. Keep the agent and server log locations separate. See patch-scan verification.
Patch scan failed due to dcdriverupdates.dll.gz extraction failure
Cause
The dcdriverupdates.dll.gz file required during patch scan could not be extracted on the managed machine, which prevents the scan components from loading.
Resolution
Uninstall the Patch Manager Plus agent from the affected machine, reinstall it, and initiate the patch scan again. If the issue continues, use the Agent Troubleshooting Tool to collect agent and patch scan logs, reproduce the issue, and share the generated log bundle with support.
Patch scanning failed due to signature mismatch in dcdriverupdates.dll
Cause
The updated driver DLL signature is unavailable in builds 11.3.2400.12 through 11.3.2400.23. When BIOS and Driver update types are disabled in Patch DB settings, dcdriverupdates.dll is not loaded during patch scan or deployment.
Resolution
Upgrade Patch Manager Plus to the latest build. If the issue continues, collect patch scan and agent logs with the Agent Troubleshooting Tool and share the generated support file with support.
Patch scan failed with checksum mismatch
Cause
The downloaded scan-related file does not match the expected checksum because the file is corrupted, incomplete, or the local scan components are outdated.
Resolution
For an agent managed through a Distribution Server, first use the Agent Troubleshooting Tool to verify communication from the agent to the Distribution Server on port 8384. Restore that connection if it fails, then initiate a patch scan again.
Before reinstalling the agent, record the exact file, requested URL, serving Central Server or Distribution Server, and failure time. Check communication and replication for that serving host. Compare the affected endpoint copy with the copy being served. Retry the scan after correcting a confirmed transfer or replication problem. If the mismatch remains, collect agent and serving-host logs for the same attempt. See replication and agent download checks.
If these checks do not resolve the checksum error, follow the agent reinstall procedure:
- Uninstall the Patch Manager Plus agent from the affected machine.
- Remove the remaining agent installation folder, if present.
- Reinstall the agent and initiate the patch scan again.
If the issue affects multiple machines, verify the server build and upgrade it if required. If the issue continues, collect agent, patch scan, and download logs with the Agent Troubleshooting Tool and share the generated support bundle with support.
Superseded-tree-scan-data.7z extraction failed during patch scanning
Cause
The file required for supersedence evaluation could not be extracted on the managed machine because its local scan data is corrupted or incomplete. This is a local endpoint scan-data issue; unaffected endpoints can continue scanning and deploying patches.
Resolution
- Uninstall the Patch Manager Plus agent from the affected machine.
- Delete the remaining agent installation directory, if it still exists.
- Reinstall the agent and trigger the patch status scan again.
If the issue continues, collect patch scan and agent logs with the Agent Troubleshooting Tool and share the generated logs with support.
Downloading global metadata.xml failed with error code 12175
Cause
Error code 12175 indicates an SSL certificate validation problem during secure communication.
Resolution
Import the required third-party SSL certificate and certificate chain into Patch Manager Plus, and restart the server service. Refer to Import an SSL certificate. If the issue continues, contact support with the relevant log files.
Patch scan failed with error code 12007
Error code 12007 indicates a name-resolution failure. Follow the DNS and connectivity checks in HTTP error 12007.
Patch scan fails on an end-of-life operating system
Patch scanning can fail when the endpoint operating system is no longer supported. Upgrade the endpoint to a supported operating system and run the scan again. Refer to Supported applications for the current support scope.