×
×
×
×

Problem Generating Patch Scan Data

Last Updated On: 16 Oct 2026|
5 minutes read |

Problem

For a resource-specific 404, such as Downloading dcpatchutils.dll.gz failed with error code : 404 or Downloading patch-scan-data.xml.gz failed with error code : 404, follow scan resource download and extraction checks and collect the URL and serving-host response for that file.

Patch Manager Plus Agent downloads the scanning-related files that contain the latest patch details. If an issue occurs while downloading or extracting these files, the patch scan fails with the error "Failed to download required scan files".

Cause

  • A scan started immediately after agents are installed on a fresh setup can fail because the scanning-related files are not yet available.
  • The proxy can restrict downloads of scanning-related files.
  • The antivirus can block the Patch Manager Plus Agent folder.
  • Communication between the server and agent can be unstable.
  • Computers in a remote office might be unable to reach the Distribution Server.
  • File replication from the server to the Distribution Server can fail.

Resolution

Check these log signatures as separate stages:

  • Unable to Open Json: open .../data/patch/patch-settings.json: no such file or directory identifies a missing local scan-settings file. Record the exact path and use the scan-data availability checks below.
  • Unable to send the Patch Scan Fail Status Update to the Server: HTTP Get Status Code - 404 Not found identifies a response while reporting the scan failure. Record the requested URL and full HTTP response; investigate that status-upload request separately.

Record the scan time, agent build and remote-office assignment. If the issue continues, include these details, the agent bundle from the Agent Troubleshooting Tool, and the matching serving-host logs. These messages alone do not establish that fresh-setup database synchronization caused the failure.

  1. Fresh setup: Ensure that the Vulnerability DB sync has completed successfully on the Update Vulnerability DB page. Wait for the update to complete, and then retry the scan.
  2. Proxy restriction: Ensure that the proxy configured in the Patch Manager Plus Agent does not block scanning-related files from being downloaded to the default agent installation directory, /usr/local/manageengine/uems_agent.
  3. Agent blocked by antivirus: Add the Patch Manager Plus Agent folder, located at /usr/local/manageengine/uems_agent by default, to the antivirus exception list.
  4. Server-agent communication issues: Ensure stable network connectivity between the agent and the server when the agent communicates directly with the server. Use the Agent Troubleshooting Tool to diagnose connectivity issues.
  5. Distribution Server not reachable: Ensure stable network connectivity between remote-office agents and the Distribution Server. For endpoints assigned to a Remote Office with a Distribution Server, open Agent → Computers and verify that the endpoint is assigned to the expected Remote Office. Use the Agent Troubleshooting Tool to diagnose connectivity issues.
  6. Replication failures: Verify that Distribution Server replication is current. In the Patch Manager Plus console, open Agent → Scope of Management → Remote Offices, and check DS Sync Status and Remarks. Also ensure that the server and Distribution Server can communicate.

Related