# Troubleshooting patch deployment errors

Deploying patches across multiple endpoints spread over various geographical locations can be difficult. While this diversity can be unified with a dedicated patch deployment policy, there are several instances wherein the deployments cannot be completed successfully.

Be it an issue of the user endpoints or the network stability, resolving such errors can be a daunting task, especially in an enterprise with a multitude of endpoints.

Using the **Patch Deployment Troubleshoot** functionality, admins can now diagnose deployment errors and resolve them in just a few clicks. This feature is applicable for both Automate Patch Deployment and Manual Deployment tasks.

**Note:** This feature is available on Endpoint Central versions 11.2.2328.01 and above. If you're on a lower version and would want to try out the feature, kindly reach out to support.

## Steps to enable Patch Deployment Troubleshoot

- Navigate to **Deployment > Automate Patch Deployment** (or **Manual Deployment**) > click on the deployment task  
- Click on **Troubleshoot** and select **Setup/Component Issues** or **Installation Issues**  
- Click on the applicable error to check for the details and the steps to troubleshoot  

![Patch deployment troubleshoot UI](https://www.manageengine.com/patch-management/images/patch-deployment-troubleshoot.png)

## Patch deployment errors and resolution

The deployment errors can be troubleshooted seamlessly based on the broader classification, as mentioned below:

### Setup/Component issues

This view lists the issues in setup/components in the network causing patch deployment failure in the systems.

#### 1) Distribution Server Issues

You can refer to the list of the common error codes for the Distribution Server issues and their resolution.

- a) **Replication executable crashed**

This error occurs in case the dcreplication.exe file has crashed or is due to an access violation exception. Kindly contact support with the Distribution Server logs for a quicker error resolution.

- b) **DS Nginx module download failure - Error 404**  
  **DS Nginx module download failure - Error 403**  
  **DS Nginx module download failure - Error Checksum mismatch**

The above-mentioned error codes occur in case of server file replication failure in the Distribution Server. Kindly contact support with the Endpoint Central server logs for a quicker error resolution.

- c) **DS Nginx Conf replication failure**

This error occurs in case of dependency file replication failure in the Distribution Server. For resolution, kindly contact support with the Endpoint Central server logs and the Distribution Server logs.

- d) **Replication failure - Improper patch store location configured**

This error occurs in case of a replication failure due to improper configurations of the Patch repository in the Distribution Server. [Learn more](https://www.manageengine.com/patch-management/how-to/how-to-migrate-the-patch-store.html).

- e) **Replication failure - Improper software repository configured**

This error occurs in case of a replication failure due to improper configurations of the Software repository in the Distribution Server. [Learn more](https://www.manageengine.com/products/desktop-central/moving-software-repository-location.html).

### Installation issues

This view lists the issues causing patch installation failure in the systems, even after a successful deployment.

#### 1) Low disk space

This error occurs due to one of the following reasons:

- Disk space less than 5 GB in the Distribution Server installed folder.  
- The disk space is about to reach its limit in the Patch Store directory or the Software Repository.  

To resolve this error, ensure that there is sufficient space for the patch installation in the above-mentioned directories.

#### 2) Reboot pending

This occurs when the updates have been installed but a reboot is pending in the system(s). The updated changes will be reflected upon a successful reboot.

## Re-deploy and re-sync

Once the error codes mentioned above have successfully been resolved, patches would automatically be re-deployed in case of **Setup/Component issues**. In case of **Installation issues**, the patches need to be re-deployed via a **Manual Deployment** task.

![Sync now button in Troubleshooting view](https://www.manageengine.com/patch-management/images/patch-deployment-troubleshoot-1.png)

Once the errors have been resolved, you can click on **Sync Now** to get the updated status on these errors.