Skip to Content

Troubleshooting Windows Patch Catalog Update failures

A Windows Patch Catalog Update job (CUJ) fails to update the Patch Catalog and displays an error message.

This topic helps you locate and review the appropriate logs to determine why the CUJ job failed and either help you identify and resolve the issue or create a BMC Customer Support case.

Issue symptoms

A Windows Patch Catalog Update job fails with an error message in the job run log.

Issue scope

The issue may occur for all or specific Windows Patch Catalog update jobs.

Diagnosing and reporting an issue

Task

Action

Steps

Reference

1

Understand the problem scope


Verify the following:

  • Are all Windows Patch Catalog Update jobs affected or specific jobs?
  • Which Windows Patch Catalog Update jobs are affected?
  • Is the problem affecting all users/roles or confined to specific users/roles?
  • Is the problem consistent or intermittent? Does rerunning the job resolve the issue?


2

Identify recent changes

Did the affected Windows CUJ previously succeed or is this a new Catalog that has not previously been run?

If the affected CUJ run previously succeeded, when did it last succeed and have there been any known environment changes since then? For instance,

  • TrueSight Server Automation was upgraded to a new version
  • Ivanti URL was changed
  • Certificate changes
  • HTTP Proxy changes


3

Identify and locate the logs

In most cases, the error message for the CUJ failure is added to the Job Run Log.

To view the log, do the following:

  1. Log in to the TrueSight Server Automation console.
  2. Open the failing Windows CUJ.
  3. Select the Results tab.
  4. Right-click the latest run and select Show Log.

    image2020-6-29_20-23-17.png

4

Review the logs to identify the error for the CUJ failure.

Review the CUJ run log to determine the error message that caused the job to fail.

The "Resolutions for common issues" section describes common errors that can result in Windows CUJ failure along with how they can typically be resolved.

If you are unable to identify and resolve the problem, see Step 5 to create a BMC Support Case.


5

Creating a BMC Support Case

Provide the following information and log files when creating a case with BMC Customer Support:

  • Scope of the issue as identified in step 1
  • Any recent changes as identified in step 2
  • Exported Windows PCU job run log
  • The appserver log(s) of the Application Server where the CUJ was run



Resolutions for common issues

Symptom

Action

Reference

BLPAT1004 - Http Url is not accessible.

Possible remediation steps:

  1. Check the proxy login credentials.
  2. Check the vendor URL.
    https://content.ivanti.com/data/oem/BMC-Bladelogic/data/partner.manifest.xml
  3. Check the internet connectivity of the Application Server. Try to access the same URL listed in the error message via a browser.
  4. Review the Knowledge Article and Webinar link in the Reference section to troubleshoot the issue.


Error while add/update patch in depot: hotfix <catalog item> OR A depot object of the same type with the name < catalog item >, already exists in this group

Review the Knowledge article and Webinar link in the Reference section for details on troubleshooting this issue.

PKIX path building failed: java.security.cert.CertPathBuilderException: Could not build a validated path. (Caused By: PKIX path building failed: java.security.cert.CertPathBuilderException: Could not build a validated path. (Caused By: Could not build a validated path.))))"

When getting this error user should check with the Proxy admin if new certificates have been applied on proxy. Review Knowledge article and Webinar link for detailed information mentioned in reference section on how to apply the new certs.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

TrueSight Server Automation 22.2