# Closed Network Patch DB Failure

Last Updated On: 23 Oct 2026

8 minutes read

## Causes

Patch DB Sync can fail when:

- An old download tool is being used.
- Sync data files transferred to the server are incomplete or corrupted. This can result from a proxy issue or an unstable internet connection.
- The Scheduled DB is Disabled.
- The updatedb folder moved to the CRS folder is incomplete.

## Troubleshooting Steps

This procedure applies to closed-network synchronization using the external download tool. For an internet-connected server whose update remains In progress or fails, use [open-network database synchronization troubleshooting](https://www.manageengine.com/vulnerability-management/kb/patch-management/open-network-db-sync-failure.html).

**1. Verify Download Tool Version**

- Use the latest version of the external download tool.
- If outdated, download the [new tool](https://www.manageengine.com/patch-management/patch-management/help/patch-management/patch-management-for-closed-network.html#dmz).

**2. Check Download Status and Errors**

- Go to the directory where the external tool was executed.
- Open the `dwnload_status.log` file and check for [the error codes below](https://www.manageengine.com/patch-management/#error).

**3. Check Exception Traces**

- Open `download_tool_log.log` (found in the same directory).
- Search for [the exceptions below](https://www.manageengine.com/patch-management/#exception). These indicate what went wrong during the sync process.

**4. Check HTTP Status Codes**

- These are also found in `download_tool_log.log.`
- Search for [the HTTP status codes below](https://www.manageengine.com/patch-management/#http). These reflect whether the file was fetched or denied.

**5. Verify the updatedb Folder**

- Ensure the downloaded `updatedb` folder includes all required .xml and .sql files.
- If incomplete or corrupt, rerun the external download tool and retransfer the folder.

**6. Validate Scheduled Sync**

- In the Patch Manager Plus server console, navigate to **Threats & Patches ---> Update Now**. Review the Vulnerability DB Sync settings there.
- You can also trigger a manual sync by clicking on **Update Now** to test if the transfer was successful.

## Exceptions

### Exception: java.net.SocketTimeoutException: Read timed out

**Cause:** Timeout during sync due to slow file transfer

**Resolution:** Ensure the tool runs on a stable LAN. Retry the sync process and check for packet loss.

### Exception: java.net.SocketException: Connection reset

**Cause:** Incomplete file download or early disconnect

**Resolution:** Stabilize the network connection. Increase timeout duration if required.

### Exception: java.net.ConnectException: Connection timed out

**Cause:** Unable to connect to internal sync endpoint

**Resolution:** Check the local network route and firewall rules. Ensure the staging server is reachable.

### Exception: java.net.ConnectException: Connection refused

**Cause:** Internal service/port blocked

**Resolution:** Allow the required port in the firewall. Verify proxy rules if configured.

### Exception: java.net.UnknownHostException

**Cause:** DNS resolution failure

**Resolution:** Use the IP address directly or fix internal DNS/host mapping issues.

### Exception: java.net.ProtocolException: Bug in authorization handling

**Cause:** Proxy authentication failure or misconfiguration

**Resolution:** Recheck proxy authentication credentials and verify proxy configuration.

## Error Codes

| Error Code | Name | Cause | Resolution |
|---|---|---|---|
| 10008 | Download Failure | The download process failed due to a network issue or an internal error. | Review the `download_tool_log.log` file for exception traces to identify the root cause. Once reviewed, retry the download after verifying network connectivity and access to the repository path. |
| 10009 | Checksum Mismatch | The downloaded file was corrupted or modified during transfer, causing integrity check failure. | Use the external download tool to re-download the necessary files. After download, replace the existing folder contents to ensure data consistency. |
| 10010 | No Change in File | The file on the server is identical to the local copy; no updates were made. | No action is needed as the file is already up to date. However, if the sync process still fails, check the completeness of the `updatedb` folder to rule out partial updates. |
| 0 | Latest File Downloaded | The latest version of the file was successfully downloaded. | This indicates a successful operation and no further action is required. Ensure that the downloaded files are correctly placed inside the `updatedb` folder for sync to proceed as expected. |

## HTTP Status Codes

| HTTP Status | Meaning | Cause | Resolution |
|---|---|---|---|
| 200 / 206 | Download Successful | The file was retrieved successfully from the server. | No further action is needed. The file was downloaded completely without any interruption or error. |
| 404 | File Not Found or Link Expired | The requested file does not exist on the server or the download link has expired. | Re-run the external download tool to generate fresh links and retry the operation. Make sure the sync is targeting the correct database version. |
| 304 | Not Modified | The file has not changed since the last request, so the server didn’t resend it. | No action is required if the file already exists locally. However, if sync issues persist, verify that the file is present and complete in the local folder. |
| 403 | Access Denied or Proxy Block | The server denied access due to lack of permissions or a proxy-related restriction. | Ensure the proxy server isn't blocking access and verify authentication credentials. Update proxy configurations or include valid headers to allow communication. |