- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
08-12-2024 09:22 AM
When performing a PSM upgrade from 12.6 to 14.2, I get a bunch of errors in the PSMInstall.log file like this:
12/08/2024, 11:00:48 Logging on to the Vault ...
12/08/2024, 11:00:48 Reading category LogonDomain on file/password "="PSMARHCAPSM01""" in Safe PSM ...
12/08/2024, 11:01:00 An error occurred while creating the Vault environment: ITATS012E Invalid parameters. Details: CVTPT116E Input parameter [FileName] value is invalid (Code=6).
12/08/2024, 11:01:00 Working on password "="PSMARHCAPSM01""" in Safe PSM ...
12/08/2024, 11:01:01 An error occurred while creating the Vault environment: CASVL006E Invalid characters in object name. ["] is not allowed.
12/08/2024, 11:01:01 Failed to access password object "="PSMARHCAPSM01""".
12/08/2024, 11:01:06 Retrying password rotation...
12/08/2024, 11:01:06 Logging on to the Vault ...
12/08/2024, 11:01:07 Reading category LogonDomain on file/password "="PSMARHCAPSM01""" in Safe PSM ...
12/08/2024, 11:03:43 An error occurred while creating the Vault environment: ITATS012E Invalid parameters. Details: CVTPT116E Input parameter [FileName] value is invalid (Code=6).
12/08/2024, 11:03:43 Working on password "="PSMARHCAPSM01""" in Safe PSM ...
12/08/2024, 11:03:45 An error occurred while creating the Vault environment: CASVL006E Invalid characters in object name. ["] is not allowed.
12/08/2024, 11:03:45 Failed to access password object "="PSMARHCAPSM01""".
12/08/2024, 11:03:50 Retrying password rotation...
12/08/2024, 11:03:50 Logging on to the Vault ...
12/08/2024, 11:03:50 Reading category LogonDomain on file/password "="PSMARHCAPSM01""" in Safe PSM ...
12/08/2024, 11:03:51 An error occurred while creating the Vault environment: ITATS012E Invalid parameters. Details: CVTPT116E Input parameter [FileName] value is invalid (Code=6).
12/08/2024, 11:03:51 Working on password "="PSMARHCAPSM01""" in Safe PSM ...
12/08/2024, 11:04:53 An error occurred while creating the Vault environment: CASVL006E Invalid characters in object name. ["] is not allowed.
12/08/2024, 11:04:53 Failed to access password object "="PSMARHCAPSM01""".
12/08/2024, 11:05:00 Password rotation failed for "="PSMARHCAPSM01""", the password has not been updated. Check the logs for more details and invoke password rotation via CPM or contact CyberArk support.
Why is it constructed this way? object "="PSMARHCAPSM01""" and how do I fix it?
08-12-2024 06:08 PM
Hi @Jamie Legleiter
The above error messages indicates that,
Hope it helps !
08-13-2024 06:21 AM
I know what the error means, my question is why is it formatting things the way it is.
For more context, these are domain-joined PSM servers and use AD PSMConnect\PSMAdminConnect accounts. I noticed in the basic_psm.ini, the upgrade added a line that matches the error:
[Main]
PSMVaultFile="C:\Program Files (x86)\CyberArk\PSM\Vault\Vault.ini"
PSMAppCredFile="C:\Program Files (x86)\CyberArk\PSM\Vault\psmapp.cred"
PSMGWCredFile="C:\Program Files (x86)\CyberArk\PSM\Vault\psmgw.cred"
LogsFolder="C:\Program Files (x86)\CyberArk\PSM\Logs"
TempFolder="C:\Program Files (x86)\CyberArk\PSM\Temp"
PSMServerId="PSM-RHCAPSM01"
PSMServerAdminId="="PSMARHCAPSM01"" <-added during the upgrade, ties in to the errors referenced in the OP
PSMServerAdminId="Operating System-RHWindowsDomainPSMAdminAccount-contoso.com-PSMAdminConnect" <- the correct entry
ConfigurationSafe="PVWAConfig"
ConfigurationFolder=Root
PVConfigurationFileName=PVConfiguration.xml
PoliciesConfigurationFileName=Policies.xml
PSMSubnetRulesConfigurationFileName=PSMSubnetRules.xml
RecordingsDirectory="D:\CyberArk\PSM\Recordings"
IdentityUM=No
SamlCpEnabled=No
AuthorizeSAMLAuthOnly=No
Once I remove the misconfigured line, I can start the service, so maybe the errors are innocuous and can be ignored since it's trying to do things to an account in the safe that isn't used anyway.
But my question now is how do I configure future upgrades to make the installation be more domain account-aware? On the surface, this seems like a bug.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

