Uninstallation of plugin fails with error 2503 Called RunScript when not marked in progress

Products

• CA Client Automation - IT Client Manager
• CA Client Automation

Issue/Introduction

Uninstallation of a DSM plugin (AM, SD or RC) using add/remove Programs or msiexec command fails with error :
“Error 2503 Called RunScript when not marked in progress”

C:\Windows\TEMP directory has read only settings for users

In MSI logs there are these lines :

Action start 17:19:41: RemLegacyAgent_Pre.
MSI (s) (10:9C) [17:19:41:517]: Skipping action: RemLegacyAgent (condition is false)
MSI (s) (10:9C) [17:19:41:517]: Skipping action: fail.87DF9952_DC90_4899_BEB4_CAEC652B6A39 (condition is false)
MSI (s) (10:9C) [17:19:41:517]: Doing action: InstallFinalize
Action ended 17:19:41: RemLegacyAgent_Pre. Return value 1.
MSI (s) (10:9C) [17:19:41:517]: Running Script: C:\Windows\Installer\MSI5815.tmp
MSI (s) (10:9C) [17:19:41:517]: PROPERTY CHANGE: Adding UpdateStarted property. Its value is '1'.
MSI (s) (10:9C) [17:19:41:517]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287035 
MSI (s) (10:9C) [17:19:41:517]: Note: 1: 2503 
Action start 17:19:41: InstallFinalize.
MSI (s) (10:9C) [17:19:41:532]: Product: CA DSM Agent + Software Delivery plugin -- Error 2503.Called RunScript when not marked in progress.

Error 2503.Called RunScript when not marked in progress.
MSI (s) (10:9C) [17:19:41:532]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287035 
MSI (s) (10:9C) [17:19:41:532]: Note: 1: 2502 
Action ended 17:19:41: InstallFinalize. Return value 3.
MSI (s) (10:9C) [17:19:41:532]: Product: CA DSM Agent + Software Delivery plugin -- Error 2502.Called InstallFinalize when no install in progress.

MSI (s) (10:9C) [17:19:41:532]: No System Restore sequence number for this installation.
MSI (s) (10:9C) [17:19:41:532]: Unlocking Server
MSI (s) (10:9C) [17:19:41:532]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Error 2502.Called InstallFinalize when no install in progress.
Action ended 17:19:41: INSTALL. Return value 3.

 

Environment

Client Automation - 14.5 CU6

Cause

The cause of this problem is that logged user that only read NTFS access on c:\windows\temp

Resolution

As workaround following powershell commands could be used.

Example for SD Agent uninstallation :

$VarTemp=[System.Environment]::GetEnvironmentVariable("TEMP","Machine")
$VarTmp=[System.Environment]::GetEnvironmentVariable("TMP","Machine")

[System.Environment]::SetEnvironmentVariable("TEMP","C:\temp","Machine")
[System.Environment]::SetEnvironmentVariable("TMP","C:\temp","Machine")

Restart-Service msiserver

$software = Get-WmiObject -Class Win32_Product | Where-Object { $_.Name -like 'CA DSM Agent + Software*' }
$software.Uninstall()

[System.Environment]::SetEnvironmentVariable("TEMP",$VarTemp,"Machine")
[System.Environment]::SetEnvironmentVariable("TMP",$VarTmp,"Machine")

Restart-Service msiserver

 

This workaround set the system TEMP and TMP variables to c:\temp

Then it uninstalls the SD Agent and finally set the system TEMP and TMP variables to original values.

 

As solution for new Agents, open a case at Broadcom technical Support and ask for the fix T5J8135

This fix delivers this file :

Name = DeployWrapper.dll

Size = 1,677,824 bytes

Modified Date = 29/03/2024

Version = 14.5.0.602

 

Correction done by fix T5J8135 :

Following problems observed when agent is deployed with DM Deploy in some environments:
1. vc redest package hangs for 4 to 5 hours.
2. msi packages make use of C:\windows\Temp. But the Client does not want that path due to policy restrictions.