- 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.
12-03-2025 11:26 PM
Hello,
I deployed a new CPM (v12.6.13), domain joined the machine, gave it permissions to the reconcile safe. However, Windows domain accounts fail to perform verify, change, reconcile operations. Webapp and REST API plugins are functioning fine.
Following errors occur on WinDomain Accounts (PMWindows.dll):
Reconcile Operations:
CACPM406E Reconciling Master
Error: CACPM243W Failed to read from third party log file.
Error: The system cannot find the file specified
The PM is trying to reconcile this password because its status matches the following search criteria: ResetImmediately,Failure
Safe: {SafeName}
Folder: {Folder}
Object: {ObjectName}
Code: -1073741515
Change Operations:
CACPM072E Login process on the remote machine fauled (Error: -1073741515, The CPM is trying to change this password because its status matches the following search criteria: ResetImmediately
Safe: {SafeName}
Folder: {Folder}
Object: {ObjectName}
I have tried the following things:
Any guidance to fix this issue will be deeply appreciated. Thanks.
12-05-2025 06:18 AM
So 139 and 445 were working for a local windows server account but password change was failing on that. 139 did not connect to the DC for password change however it did not connect even for the functioning CPM. After a lot of trials, errors, and diagnoses it turned out that the problem was with the PassChng.exe bundled with the Credential Management Framework Bundle (v14.6.3). When I replaced it with the one which came in the installation package by default, all functions started functioning again.
However now I am getting the following error on Windows LDAP accounts:
Execution error.
PreReconcile process failed - Invalid input in paramter 'LogonDomain'
Refer to logs for more information.
The CPM is trying to change this password because its status matches the following search criteria: ResetImmediately.
I have tried all combinations of username as sAMAccountName and upn and LogonDomain as both fqdn and NetBIOS however it fails to work.
PS: regarding the LDAP issue, changing the reconcile account LogonDomain to NetBIOS name fixed it (reconcile account was a WinDomain account)
12-04-2025 07:42 AM
What about windows local accounts? If windows local accounts are also failing, then Test connectivity to the target from CPM using PowerShell on port 139. and 445 and see if the result is true or false. As well as you can post the settings ncpa.cpl related to ipv4.
tnc -computername <targetip> -p 445
tnc -computername <targetip> -p 139If Windows local accounts are fortunately working, then you can test your DC server on port 139 and 445
12-04-2025 11:54 AM
Hi @Mairaj Aziz
Can you please clarify the following ?
Please check if Check if PMWindows.dll is being blocked from Anti-Virus.
Try exlucding CPM PasswordManager is excluded from Anti-Virus real-time scanning.
On the CPM server, verify that Network security: LAN Manager authentication level is not set to "Send NTLMv2 response only\refuse legacy."
Please refer to this KB and try to perform the manual steps using command prompt from CPM server
https://community.cyberark.com/s/article/How-does-CPM-manage-Windows-accounts-passwords
Please refer to this article more error code and its solutions
https://community.cyberark.com/s/article/CPM-CACPM243W
Hope it helps!
12-05-2025 06:18 AM
So 139 and 445 were working for a local windows server account but password change was failing on that. 139 did not connect to the DC for password change however it did not connect even for the functioning CPM. After a lot of trials, errors, and diagnoses it turned out that the problem was with the PassChng.exe bundled with the Credential Management Framework Bundle (v14.6.3). When I replaced it with the one which came in the installation package by default, all functions started functioning again.
However now I am getting the following error on Windows LDAP accounts:
Execution error.
PreReconcile process failed - Invalid input in paramter 'LogonDomain'
Refer to logs for more information.
The CPM is trying to change this password because its status matches the following search criteria: ResetImmediately.
I have tried all combinations of username as sAMAccountName and upn and LogonDomain as both fqdn and NetBIOS however it fails to work.
PS: regarding the LDAP issue, changing the reconcile account LogonDomain to NetBIOS name fixed it (reconcile account was a WinDomain account)
12-05-2025 06:18 AM
So 139 and 445 were working for a local windows server account but password change was failing on that. 139 did not connect to the DC for password change however it did not connect even for the functioning CPM. After a lot of trials, errors, and diagnoses it turned out that the problem was with the PassChng.exe bundled with the Credential Management Framework Bundle (v14.6.3). When I replaced it with the one which came in the installation package by default, all functions started functioning again.
However now I am getting the following error on Windows LDAP accounts:
Execution error.
PreReconcile process failed - Invalid input in paramter 'LogonDomain'
Refer to logs for more information.
The CPM is trying to change this password because its status matches the following search criteria: ResetImmediately.
I have tried all combinations of username as sAMAccountName and upn and LogonDomain as both fqdn and NetBIOS however it fails to work.
PS: regarding the LDAP issue, changing the reconcile account LogonDomain to NetBIOS name fixed it (reconcile account was a WinDomain account)
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!

