Home » Patch Deployment Errors Troubleshoot
 

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.

Patch Deployment Troubleshoot

Follow the steps below to enable patch deployment troubleshoot:

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

Patch deployment troubleshoot

Patch Deployment Errors and Resolution

The deployment errors can be troubleshooted seamlessly based on the broaded 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

  2. 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 in pending in the system(s). The updated changes will be reflected upon a successful reboot.

Patch Redeployment and Resynchronization

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

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

 

If you have any further questions, please refer to our Frequently Asked Questions section for more information.