| ErrorCode | Cause | OS/Plugin | Resolution |
| Error: cannot proceed to next state since none of the conditions for the state met. State "StartScript". code: 7079 | There are quite a few possible causes for this. One potential (and common cause) is the use of the banner message during the login process. The banner display could be interfering with the parsing of the input. | Unix | Check the banner message, making sure there are no non-printable characters Check the output of the debug logs carefully. Make sure that the password prompt as well as the standard prompt are properly accounted for in the prompts ini file |
| Error: cannot proceed to next state since none of the conditions for the state met. State "StartScript". code: 7079 | CPM Using PMTerminal Plugin instead of supported TPC. Data Execution Prevention is enabled for the operating system and all processes, including the Windows kernel and drivers. | Unix/Windows Usage | There are several solutions for this problem. The most recommended solution is to use TPC (Terminal plugin controller) rather than PMterminal whenever possible. The latest download of TPC can be found here: https://community.cyberark.com/marketplace/s/#a3550000000El8nAAC-a3950000000jju7AAA For some plugins, this is not possible. In those cases, check details in this article: https://community.cyberark.com/s/article/00001806 |
| Error in changepass to user <User> on domain <Domain> (\\Domain). (winRC=2245) The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements." | The period between 2 password changes is shorter than Minimum Password Age configuration in GPO or If the account object belongs to an account group, a reconcile will fail if first account against any account of an account group is a reconcile with WinRC=2245 | Windows | The answer or the steps taken to resolve the issue. Option 1- Update the security policy on the target machine or domain GPO \Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy The Minimum password age policy setting determines the period of time (in days) that a password can be used before the system requires the user to change it. You can set passwords to expire after a number of days between 1 and 999, or you can specify that passwords never expire by setting the number of days to 0. If Maximum password age is between 1 and 999 days, the minimum password age must be less than the maximum password age. If Maximum password age is set to 0, Minimum password age can be any value between 0 and 998 days. This policy setting is supported on versions of Windows that are designated in the Applies To list at the beginning of this topic. Additionally, you can associate a Reconcile account to the platform in order to override the Minimum Password Age by resetting the password. Note: Any authenticated domain user can use the 'net accounts' command to look at the password policy details from the command line. Option 2 - When a new group is created, the group object has no password, it is empty. Thus, running a reconcile will fail with WinRC-2245. The action of reconcile against an account group does not create a new password and sets on that object, instead, CPM grabs the password of the account group and sets that target account with that group's password. To resolve this error, please run a change on any account that belongs to that group. This action will create a password for the group object. When creating an account group, CPM will create: 1-A folder called group on the safe that holds all accounts that belongs to an account group 2-Will create an object with the name of the group on that folder, group. |
| Execution error. Error: Invalid prompt or did not receive any prompt. State: "SwitchUser". code: 7001 | The prompts the target machine sending are in non English character causing TPC not understanding the prompts and timed out. | Unix | Update the UnixProcess.ini to change the language before every change password or switch user operations. Sample UnixProcess.ini file (modified from CPM 9.9.5) attached, tested with Chinese zn_CH CentOS Linux NOTE: Some UNIX distributions require different syntax for the LANG variable. For example, in the attached process file, the LANG variable is set to LANG=en_US.UTF8. Some UNIX distributions will recognize LANG=en_US.UTF-8 or LANG=en_utf8 (notice the dash [ - ] or lowercase "utf"). The most compatible syntax with most distributions is UTF-8 (using the dash). Sample change below: SwitchUser=LANG=en_US.UTF8, su - <username> ChangePass=LANG=en_US.UTF8, passwd <username> ChangePassNoUserName=LANG=en_US.UTF8, passwd PRSwitchUser=LANG=en_US.UTF8, su - <extrapass3\username> PRResetPass=LANG=en_US.UTF8, passwd <username> SudoPasswd=LANG=en_US.UTF8, sudo passwd <username> PRSwitchUserAfterResetPass=LANG=en_US.UTF8, su - <username> |
| Execution error. Change process failed - Failed to find account <username>. Review the logs for more information. Error code:8001 | In the current plugin in order to support Username as the username defined on the account (sAMAccoutName), the Display Name property on the target account must be changed to match the sAMAccountName | Windows LDAP | There are two workaround options available: 1) For Basic Authentication: Update the Display Name property of the target account in the LDAP Directory to match the sAMAccountName property 2) Use NTLM authentication. With NTLM authentication sAMAccountName can be used as the username property. |
| Action changepass is not supported for users of type 'Service' by the SAP plugin. | The account is not able to run in change mode and must be set to ChangePasswordInResetMode | SAP NetWeaver | The service account cannot change it's own password so Use ChangePasswordInResetMode parameter to treat password changes as reconcile/reset should solve the issue. Please follow the below instructions for enable this on the platform: Log into PVWA -> Administration tab -> Platform Management -> [platform] -> Edit -> Automatic Password Management -> additional policy settings and update the value for the 'ChangePasswordInResetMode' parameter to Yes -Specify service account itself as the reconcile account. |
| Failure Description: Error in reading xml file <path to xml file> while trying to get tag Reconcile account on logon | ChangePasswordInResetMode is set to "yes" in the platform settings (under Automatic Password Management -> Additional Policy Settings) which causes the CPM to perform a reconcile process whenever a change process is initiated on accounts on the platform (immediate or periodic changes). The error happens because the account either has no reconcile account associated or the account that is associated is not accessible to the CPM user processing the change. | Windows/Unix | If the password change should process as a true change function, then: 1 PVWA--Platform Management-->Edit-->Additional Policy Settings 2. Change ChangePasswordInResetMode is set to "no" 3. Restart CPM service If the password change should process in reset mode using reconcile account, then: 1. Make sure there is a reconcile account properly associated with the account 2. Verify that the CPM user has List, Use and Retrive Password permissions on the safe where the reconcile account is stored |
| First login - Failed to verify user after switching. code: 8008 | The default Idira process to recognize Solaris machines requires that the whoami command exists. However, the whoami command is not found on the Sun Solaris machine. | Sun OS | Detail resolution listed in this article: https://community.cyberark.com/s/article/CPM-SunOS-Solaris-Failed-to-verify-user-after-switching-code-8008 |
| Error in changepass to user <User> on domain (Domain). (winRc=1327) Logon failure: user account restriction. Possible reasons are blank passwords not allowed, logon hour restrictions, or a policy restriction has been enforced. | There is a restrictive security setting on the target Windows computer. It could be a "User Rights Assignment" or a "Security Option" defined in the OS's "Local Security settings". | Windows | The below list has 2 possible target node security settings that can be changed to correct the issue. You can access a full list of the "Local Security Settings" via Start menu > Run..., type "secpol.msc" and Enter button. 1. The user itself does not have permission to change its own password. In other words, the Security Policy of your Windows machine is denying the change. 2. The "LAN Manager Authentication level" on the CPM Server is not compatible with that set on the target Windows computer. Check the "Local Security Settings" (secpol.msc) by navigating to Local Policies, Security Options, and the "Network security: LAN Manager authentication level". Additional Information: Windows System Error Codes such as "WinRC=1327" are sent from the target Windows OS. You can see descriptions at the following Microsoft website. http://msdn.microsoft.com/en-us/library/ms681381%28v=VS.85%29.aspx |
| EXT01::Invalid Username - Username must contain only alphanumeric characters. Error code:8019 | Additional restrictions for forbidden characters implemented base on below security bulletin https://community.cyberark.com/s/article/CyberArk-Security-Bulletin-CA20-02 The underlying cause of the issue. Cause is an optional field as it is not appropriate or necessary for some types of articles. The reason because the username contain blacklisted characters which meet the CiscoProcess.ini exception check. The default value for CheckUsernameForBlackList is only accepting alphanumeric characters for username. | Cisco | https://community.cyberark.com/s/article/CPM-Username-must-contain-only-alphanumeric-characters-Erro... |
Got timeout. Received: CScript Error: Loading your settings failed. (Access is denied. ) Did not find any matching prompt for 'CScript Error: Loading your settings failed. (Access is denied. ) | Two registry keys are missing from the default profile which causes access denied failure when cscript executes for the PluginManagerUser service accou | Windows Usage | Launch regedit.exe Navigate to: HKEY_USERS/.DEFAULT/Software/Microsoft/ Under Microsoft, If the following key doesn’t exist add it: Windows Script Host Under Windows Script Host, If the following key doesn’t exist add it: Settings |
| failed validating <drive>:\Program Files (x86)\CyberArk\Password Manager\bin\CASSLEAY32102o.dll fips dll file. [1172] | The calibeay*.dll and cassleay*.dll library files are not updated properly on the CPM. | | 1. STOP the Password Manager service on the CPM. 2. Backup or remove these files: "C:\Program Files (x86)\CyberArk\Password Manager\cassleay32102o.dll" "C:\Program Files (x86)\CyberArk\Password Manager\calibeay32102o.dll" "C:\Program Files (x86)\CyberArk\Password Manager\Vault\calibeay32102o.dll" "C:\Program Files (x86)\CyberArk\Password Manager\Vault\cassleay32102o.dll" "C:\Program Files (x86)\CyberArk\Password Manager\bin\calibeay32102o.dll" "C:\Program Files (x86)\CyberArk\Password Manager\bin\cassleay32102o.dll" "C:\Program Files (x86)\CyberArk\Password Manager\Scanner\calibeay64102o.dll" "C:\Program Files (x86)\CyberArk\Password Manager\Scanner\cassleay64102o.dll" 3. Run a repair on the CPM. New copies of these files are put in place. They are different than the two with the same names that are deleted. They have the same names and version numbers, but they have different sizes and are digitally signed: calibeay32102o.dll - File Version: 1.0.2.15 - Product Version: 1.0.2o - Size: 1486000 bytes - Signed cassleay32102o.dll - File Version: 1.0.2.15 - Product Version: 1.0.2o - Size: 287648 bytes) - Signed 4. RESTART the Password Manager service on the CPM. |
| Failed to acquire lock on services database ip <Address> service name <Service Name>. Error: 183 Message: Cannot create a file when that file already exists | The target Windows machine is overloaded with events (such as from failed logon attempts for a service which you would see in event viewer system log) which prevents the CPM from locking the database in order to update the password on a Windows service. | Windows Usage | Address the issue with the offending service causing the overloading of events on the target Windows machine. If possible, stop the service temporarily to determine if it is the one causing the problem. You can test this by attempting to update the password on the target service again. If it succeeds, then fix the issue with the offending service (such as correcting its logon password). |
| Error in reading xml file, Error: 2112 | Error return code 2112 means "PM_ERROR_INVALID_PARAMETERS". This usually indicates that no logon account is associated with the target account. | SAP NetWeaver | The account in PVWA will need to be associated with a Logon Account for SAP configuration. If you can log in successfully with the account, you should be able to use the same account for the logon account. The account will also need the right permissions to change its own password, if not you will need to use a logon account which has permissions to log in and change users account passwords. The following link should be able to provide some guidance on setting up the Logon Account for SAP: https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/SAPApplicationsPlugin.htm#reconcile/logon-account https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/SAPApplicationsPlugin.htm#!#Prerequi |
Change process failed - Target account does not have the required permissions to execute this action. Error code:8015". Failed to submit request. Received status code: 403 - Forbidden. Received error type:Authorization_RequestDenied. Error description: Insufficient privileges to complete the operation. | We suspect that this issue is happening due to a possible recent change in the Azure behavior - When we fail to change an account's password, it gets locked by Azure. In order to remove this lock use one of two ways. The Azure Password Management target account is missing permissions to manage it's own password. | Azure | In order to remove this lock use one of the following methods. Manually reset the password from the Azure web portal. Notice that after performing the reset you will get a temporary password - use it to login to Azure, it will prompt you to set a new password. After doing so, given that the account is defined with the proper permissions, you should be able to use it to change\reconcile. If you already have an account that has the permissions and able to log in, you can use it to reconcile the problematic account's password. This will also remove the 'lock'. The target Azure Directory account does not have the necessary permissions to change it's own password. The account must possess one of the following permissions in order to rotate it's own password: Password Administrator User Administrator Privilege Authentication Administrator Global Administrator If the account does not have one of these permissions, a logon account must be associated to the target account. The logon account must possess one of the permissions mentioned above. Note: The logon account does not need the Global Administrator role to rotate a Global Administrator user. In order to eliminate creating another Global Administrator in your environment, you can assign the "Privilege Authentication Administrator" role to the logon account so you can rotate the password of the Global Administrator Account. |
| EXT01::Fingerprint mismatch for 'ssh-ed25519@22:1.1.1.1'. Error code:9007 | As the error suggests, the cached/stored key in the Windows registry on the CPM does not match the key provided from the target. This can occur after situations such as a manual change to the targets' key or after system maintenance/patching. By default, the UnixviaSSH and UnixviaSSHKeys plugins, do not allow for automatic acceptance of new SSH keys. This is by design, as it is a security concern, and could be a sign that there may be a security breach. | SSH | https://community.cyberark.com/s/article/CPM-SSH-Fingerprint-Mismatch |