Failed to serialize string sp_password. SQL account reconciliation issue. Any expertise to fix this please ?

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

Failed to serialize string sp_password. SQL account reconciliation issue. Any expertise to fix this please ?

L1 Bithead

ReconcileIsWinAccount=Yes

ReconcileCommand= sp_password @new='%NEWPASSWORD%', @loginame='%USER%'

--------------Debug logs--------------

Logon with reconcile account succeeded

Reconciling with statement sp_password @new="%NEWPASSWORD%", @loginame="%USER%"

ExecutionStringTemplate: [sp_password @new="%NEWPASSWORD%", @loginame="%USER%"] Length: [52]

'newpassword' is not a valid parameter name. Please update the command : 'sp_password @new="%newpassword%", @loginame="%user%"' so that it contains only valid parameters.

Failed to serialize string sp_password @new="%NEWPASSWORD%", @loginame="%USER%"

Failed to reconcile with statement sp_password @new="%NEWPASSWORD%", @loginame="%USER%"

Clean ups

Rc: 2120

Ending plug-in

------------------------------------------------------------

Note: strangely there is another account(different name) which is associated with same platform & safe which is working fine and I can reconcile it.

6 REPLIES 6

L7 Applicator

The default plugin has restrictions over what characters can be in the password - if one is working and one isn't, verify the password doesn't contain any of them. I would expect an error like that if it did.

 

CommandForbiddenCharacters='\/@".{}() -;|*>~!^#   ;Characters that cannot be used in the parameters of the change/reconcile command.

CommandBlackList=delete,drop,exec,create,alter,rename,truncate,comment,select,insert,update,merge,call,explain,lock,grant,revoke      ;Words that cannot be used in the change/reconcile command. Separate multiple values with a comma.

L3 Networker

Hi @Amit Maharana​ ,

 

There seems to be a problem with the command that is used for reconciliation. Can you check the command under the particular platform that the account is associated with --> Automatic Password Management --> Additional Policy Settings --> Reconcile Command. You can check the command based on your SQL Server on the CyberArk Page.

 

You can navigate to this page and find you database server and then move to the part where the Reconciliation command is mentioned. --> Databases | CyberArk Docs

L3 Networker

Hi @Amit Maharana​ ,

 

There seems to be a problem with the command that is used for reconciliation. Can you check the command under the particular platform that the account is associated with --> Automatic Password Management --> Additional Policy Settings --> Reconcile Command. You can check the command based on your SQL Server on the CyberArk Page.

 

You can navigate to this page and find you database server and then move to the part where the Reconciliation command is mentioned. --> Databases | CyberArk Docs

Hi @Malcolm Murray​ ,

Missed to mention that failing & succeeding accounts are all part of different account groups. But the Group Platform is unique meaning that all accounts in both groups are associated with same Group Platform.

 

Also, when i remove the failing account from accounts group and try to reconcile, it works.

Perhaps the account group is choosing a bad password. Have you checked that?

Quite unlikely. Because the group platform password policy is exact same as account platform.

  • 428 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!