Troubleshooting CPM Password Reconciliation Failure (Error Code CACPM406E)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PAM Self-Hosted Articles
10 min read
L5 Sessionator
No ratings
When Central Policy Manager (CPM) fails to reconcile a password(manual reconciliation, pre-reconciliation, or in scheduling task), the following error will be shown:
CACPM406E Reconciling <object type> Safe: <safe>, Folder: <folder>, Object: <object> failed (try <retry number>). Code: <code>, Error: <error>

The accompanying error codes and relevant action indicate the reason for the occurrence, which will be listed in this article. 

Steps

In the table below, we'll explore the most common occurrences of these errors:
 
ErrorCode:Cause:Resolution:
 Code: 2101, Error: Error in prereconcilepass to user
If the reconciliation of the Windows domain account was working fine in the past, the Reconciliation account password has expired.
  1. Domain password is expired on the Directory server.
  2. Non Domain Admin account has been modified after a risk assessmen
1. Resetting the password for the domain reconciliation account would resolve this issue.
2.
a) The account password should be "un-expire" after its expiration took place.
This can be done in Active Directory via cmdlet or via the "Active Directory Users and Computers" in the Active Directory in the relevant user's "pwdLastSet". Note: You need to open Active Directory Users and Computers and have ‘Advanced options’ enabled to view the "Attribute Editor" tab. 
 
Now, locate your user and open their properties > Attribute Editor > Attributes > pwdLastSet and set '0' apply, and then set '-1' and apply again, which will extend the previously expired Password: 
 
ka3Vy00000CJgJBIA1__eid=ka3Vy00000CJgJB&feoid=00N2J000009R3kv&refid=0EM2J000003LZIx.png
Then, the Domain password that have expired should be also configured to avoid the recurrence of the issue:
b) Define the "ExpirationPeriod" parameter in the Master Policy to be lower than the policy for the domain expiration.
c) Or, set the "HeadStart" parameter in the Policy file to avoid changing the password when it is already expired in the Domain. 
d) Or, set the Domain password not to expire.
 
3. Identify the problems with the account using dsacls.exe check that the account has the reset properties.
Code 2101,Error: Error in reading xml file <file name> while trying to get tag Reconcile account on prereconcile passThere is no reconcile account associated with the password object, however the policy has reconciliation enabled. The error occurs when CPM is trying to retrieve reconcile account info to proceed with the reconciliation and fails with the above error message.There are two ways to handle this situation:

1. Associate a reconcile account with the password object
2. Associate the account that experiences the problem with a policy that does not allow reconciliation (RCAutomaticReconcileWhenUnsynched=No, RCAllowManualReconciliation=No)
Code: 2108, Error: reading xml file while trying to get tag extrapass1 on (verifypass/loginpass/changepass)There is no logon account associated with the password object; however, the platform requires a logon account to work.To resolve this issue, associate a logon account with the password object.
To check if a specific plugin requires a logon account please check the documentation in the marketplace, this can be found under Resource for the plugin you are having difficulty with.
Code: 8046, Error: Execution error. Failed to verify after Reconcile action. Error code:8046This error is seen for SSH Keys accounts. This error occurs if the hidden .ssh directory under user's home directory (/home/<UserName>/.ssh) has been created by a privilege user. In this case, the user itself has no permission on the .ssh directory and CPM fails to modify / change authorized_keys file.Check the owner of the .ssh directory under user's home directory  (/home/<user>). You can use the following command as an example:

ls -al

The output of the ls -al command will look similar to the list below. Here, in this example, the user is john and the group is also john. Notice that the .ssh directory's owner and group are root and not john.

total 32
drwx------.  5 john john   4096 Jan 31 22:27 .
drwxr-xr-x. 16 root root   4096 Jan 31 22:26 ..
-rw-r--r--.  1 john john     18 Jan 16  2015 .bash_logout
-rw-r--r--.  1 john john    176 Jan 16  2015 .bash_profile
-rw-r--r--.  1 john john    124 Jan 16  2015 .bashrc
drwxr-xr-x.  2 john john   4096 Jul 14  2010 .gnome2
drwxr-xr-x.  4 john john   4096 Mar 20  2016 .mozilla
drwxr-xr-x.  2 root root   4096 Jan 31 23:03 .ssh

If the user itself is not owner of the .ssh directory and files within it, change the permissions to the .ssh directory and files within it by following steps outlined below:
1-On the user's home directory, use the following command to change the owner of the .ssh directory. In this example, our user is hjohn and group is john.
chown john:john .ssh (notice the colon in between owner and group)

2-Change to the .ssh directory by using cd .ssh

3-Change ownership of authorized_keys file to john. See below:
chown john:john authorized_keys (notice the colon in between owner and group)

4-Try again reconciling the account
Code: 2114 Error: Error in prereconcilepass to user target.domain.fqdn\localaccount on domain taraget.domain.fqdn(\\mydc1.domain.fqdn) Reason: The username or password is incorrect (winRc=1326)Windows Domain reconcile account. The reconcile account's password is in sync and can verify.

When you kick off a reconcile task on a Windows Local account using an associated Windows Domain reconcile account whom has the DC name in the address field you encounter the error.
When using the Windows Domain plugin, If the target account has a reconcile account and you are kicking off a reconcile task - it will attempt to log into the domain controller with a username of <address>\<username>.  

If the address is a domain controller then the username used is “dc.domain.fqdn\myusername”, which translates into something that is NOT a valid username for the account.  

When the address is the domain FQDN - like it’s supposed to be, then the username used is “domain.fqdn\myusername”, which is a valid username for the account so it will complete the reconcile task successfully.

This is an issue for both logon and reconcile accounts - their address needs to be the domain FQDN, not a DC, and not an IP.

A DC address will work for a target account that does not have a logon account or a reconcile account assigned, but it is still recommended to use domain FQDN.  

If you use a particular DC name in the address field, then you eliminate all the redundancy and cause a single point of failure for the management.
1) Update the address field of the Windows Domain reconcile account in PVWA from "dc.domain.fqdn" to "domain.fqdn" and save the account.
2) Kick off another reconcile task on the Windows Local target account using the Windows Domain reconcile account you updated above.
CACPM406E Reconciling Password Safe: Lin-Fin, Folder: Root, Object: Operating System-UnixSSH-10.0.4.2–root failed (try #0). Code: 7251, Error: CACPM243W Failed to read from third party log file. Error: The system cannot find the file specified.
Same position of the file path of the .ini as the "ヨ" in the log name:
IE. Parse error. Error reading file C:\Program Files (x86)\CyberArk\Password Manager\tmp\Lin-Prd-PCI-Lin-Fin-Root-Operating System-UnixSSH-10.0.4.2?root-08-11-16 12-02-11.ini. File doesn't exist. code: 7251
 
In the pm.log you see event CACPM111I where the .ini was created, but in the same position as the "ヨ" and the "?" you find a DASH
IE.  CACPM111I Creating text INI file for password handler process (C:\Program Files (x86)\CyberArk\Password Manager\tmp\Lin-Prd-PCI-Lin-Fin-Root-Operating System-UnixSSH-10.0.4.2–root-08-11-16 12-02-11.ini).

 

The DASH character found in the path is not actually a DASH (ascii: 45), it's an EN DASH (unicode: 8211).  This is an unsupported character for object names.

 

Rename the account object to not have the unsupported character
 
On the account details page: 
-Click Edit 
-Expand the Show advanced section 
-In the Name field, retype the object name using a standard DASH rather than the EN DASH and save 

 

CACPM406E Reconciling Password Safe: <MySafe>, Folder: Root, Object: Operating System-<Policy>-<Server>-<User> failed (try #0). Code: 2101, Error: Error in reconcilepass to user Server\User on domain Server(\\Server). Reason: An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry. (winRc=1016). The issue could be a general problem with the server.  Microsoft describes the WinRC code 1016, and proposes a solution in the following MSDN article. 

http://msdn.microsoft.com/en-us/library/ms838132.aspx
Restart the system. You may have to use the Emergency Repair Disk to restore the system configuration information.
CACPM406E Reconciling Master
Error: Error in prereconcilepass to user CONSECCAMSP01.xxxxx.net\admin on domain CONSECCAMSP01.xxxxx.net(\\CONSECCAMSP01.xxxxx.net).
Reason: The network path was not found.
(winRc=53).
Reconcile account details -
The CPM is trying to reconcile this password because its status matches the following search criteria: ResetImmediately
Safe: P-WL-INT-INF-Admin
Folder: Root
Object: Operating System-S-IN-P-RW-WL-Ex-A-CONSECCAMSP01.xxxxx.net-admin failed (try #0)
Code: 2104
 TCP port 445 is not listeningRun the following command on (the command is specific for Windows 10) to allow inbound Firewall rule for TCP port 445:

The following command resolved the issue. 
netsh advfirewall firewall add rule name="Allow SMB" dir=in action=allow protocol=TCP localport=445

Afterward, verify TCP port 445 is now listening (e.g. netstat command)
Code: 8057, Error: Execution error. EXT01::Reconcile process failed - The server asked for root's password while using sudo. This scenario is not supported. Error code:8057 The CPM is trying to reconcile this password because its status matches the following search criteria: ResetImmediately.Sudoers file has "Defaults rootpw" set meaning when run command with sudo it is required to enter the password of root.
This is not a supported scenario as the purpose of reconcile is to "reset" root account password.
In this case, if running sudo required root's account password, we are stuck here because we do not know root's password since beginning.
1. Remove the "Defaults rootpwd" configuration so that sudo does not prompt for root's password and instead prompts for the reconcile account's password.
2. Make the reconcile account a poweruser (set reconcile account with UID 0), and set UseSudoOnReconcile to No. If sudo is not being used then the root password is not prompted for, but if sudo is not being used the reconcile account needs to be a power user.
Code: 2101, Error: Error in reconcilepass to user <the account IP and user> on domain <Computer name/Domain name/IP>. Reason: Access is denied. (winRc=5).Although the user has local admin rights, the computer/domain, the policy restricts the CPM from changing the password remotely.1. Configure the reconcile account with the local administrator user.
Do the following:
1.Disable UAC on target from the security policy: Run secpol.msc | Local Policies | Security Options | User Account Control: Run all administrators in Admin Approval Mode. Set: "Disabled".
2.Disable UAC Remote Restrictions on target using: Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System, Value: LocalAccountTokenFilterPolicy = 1 (0 is enabled).

Notes: Changing the registry requires a reboot to the machine.
If the reconcile user is not able to change the password manually, the solution will not help since the user doesn't have admin permissions on the machine.
Code: 2114 Error: Error in verifypass to user target.domain.fqdn\localaccount on domain target.domain.fqdn(\mydc1.domain.fqdn) Reason: The specified domain name is invalid or cannot be resolved (winRc=1208)The CPM cannot locate or resolve the target domain during password reconciliation. This may be due to DNS misconfiguration, expired credentials, or network segmentation.Confirm that the domain name is correctly configured in the platform settings. Ensure DNS resolution is functioning and that the CPM server has network access to the domain controller. Retry reconciliation after validation.

 
Rate this article:
  • 40881 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎03-31-2026 11:13 AM
Updated by: