This section contains potential problems and error codes that you may encounter when upgrading Privileged Account Manager.
Issue: When you upgrade to 3.2 from any lower version through command line or MSI, the message Attempt to add node with existing siblings is displayed continuously without progressing to upgrade. This issue occurs when the upgrade through other modes are disabled by setting the value of Allow Package Management Through Host Console to No in the Host Console.
Workaround: Set the Allow Package Management Through Host Console to Yes and perform upgrade again.
Issue: When you upgrade from 3.1 to 3.2 in Windows, Command Control Agent upgrade fails with an error. This issue occurs because the LogonUI.exe or scrncapt.exe is active in the agent machine.
Workaround: To workaround this issue, close all the VMWare console sessions and Agent sessions and perform upgrade again. It is recommended to upgrade to 3.2 during an outage or a downtime.
Issue: When you upgrade Framework package (spf) of the AIX agent through UI, the upgrade fails with the error message Failed to receive response from the module.
Workaround: To workaround this issue, you must perform hard restart of the AIX agent from the Host Console and try upgrading again.