PM patches remain in Packaging status

book

Article ID: 50291

calendar_today

Updated On:

Products

CA Client Automation CA Client Automation - Patch Manager

Issue/Introduction

When this issue occurs, all PM patches accepted will go into and then remain in status state of "packaging" and not proceed to "testing".

If you check you would find that the patch(es) are actually downloaded to the PM downloads folder (usually 'C:\Windows\Temp' or 'C:\Program Files (x86)\CA\DSM\PatchManagement\downloads')

What is actually failing is the registration of that package into the DSM/ITCM manager.

In upm.log the following errors are typically seen together:

2011-07-01 03:25:47,426 [DownloadedPatchTask] DEBUG [com.ca.pmengine.infrastructure] - Creating volume(s) for package:UPM - Windowsxp-kb971633-x86 EN - {3e271a7b-bee5-47f0-bb23-c7d4324378f8} (FFE0151C63484CC39A4F4D41A2C35240)
2011-07-01 03:25:47,788 [DownloadedPatchTask] DEBUG [com.ca.pmengine.infrastructure] - Adding volume elements to volume:DEE88719408844288381B61BB12C1D79
2011-07-01 03:25:48,302 [DownloadedPatchTask] ERROR [com.ca.pmengine.eventmanager] - Error ocurred executing a DSM Webservice method. Reason: No elements copied
2011-07-01 03:25:48,737 [DownloadedPatchTask] DEBUG [com.ca.pmengine.infrastructure] - releaseSession(): returning session to pool
2011-07-01 03:25:48,737 [DownloadedPatchTask] ERROR [com.ca.pmengine.decision] - Patch Windowsxp-kb971633-x86 EN {3e271a7b-bee5-47f0-bb23-c7d4324378f8} package registration failed
2011-07-01 03:25:48,738 [DownloadedPatchTask] FATAL [com.ca.pmengine.decision] - Patch Windowsxp-kb971633-x86 EN {3e271a7b-bee5-47f0-bb23-c7d4324378f8} Package Registration Failed

Cause

This problem can occur when one of following conditions are meet:

  • The user name set in PM configuration for DSM connection is not the local Administrator

  • UAC (User Account Control) is enabled.

For example:

In this screenshot, user TEST is specified and is a local admin. UAC is not enabled on the Windows server machine, so problem occurs.

Environment

CA Client Automation - All versions 14

Resolution

There are 2 possible solutions:

  • Turn Off UAC* and
  • Set the local Administrator in PM configuration for DSM connection

    or

  • Turn Off UAC*

    and
  • Gives FULL CONTROL NTFS rights on C:\Program Files (x86)\CA\DSM\SD\ASM\LIBRARY for user defined in PM configuration for DSM Connection

*Turning off UAC is not always required. If the companion action does not resolve the situation however, turning off UAC should be the next step.

Attachments