Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Replication-agentclassname: agent CUST1-Customer273-Customer273-Databaseservername\VS1-628 failed. Unable to start execution of step 2 (reason: Error authenticating proxy Domainname\user system error: The referenced account is currently locked out and may not be logged on to.). The step failed.
|English: Request a translation of the event description in plain English.|
More information that may be causing this issue:
Has the SQL Server service account been changed or expired? If so, was it updated in the SQL Server configuration manager? The reason I ask, is that I found information on this error after gpofix has been run. The issue can affect the servers via Active Directory. The documentation I found showed that other users had to uninstall and then reinstall to sync up Active Directory and resolve the replication issue. Run your agents one by one to see if you can manually force this error in your event log.
Diving deeper, I found the following information.
This is a general error, which can be raised regardless of whether replication is being used. For a server in a replication topology, the error is typically raised because the SQL Server Agent service account is changed by using the Microsoft Windows Service Control Manager instead of SQL Server Configuration Manager. When you try to run an agent job after changing the service account, the job might fail with an error message that is similar to the following:
"Executed as user: <user account>. Replication-Replication Snapshot Subsystem: agent <agent name> failed. Executed as user: <user account>. A required privilege is not held by the client. The step failed. [SQLSTATE 42000] (Error 14151). The step failed."
This problem occurs because the Windows Service Control Manager cannot grant the required permissions to the new service account for SQL Server Agent.
To avoid this problem in the future, always use SQL Server Configuration Manager instead of the Windows Service Control Manager to change service accounts and passwords.
To resolve this problem, use SQL Server Configuration Manager to change the service account back to the original account. Then, use SQL Server Configuration Manager to change to the new account. When you do this, SQL Server Configuration Manager adds the new account to the following security group:
Being a member of this security group grants to the new account the required permissions to run the replication agent job.
See the link to "Microsoft event 14151 from source MSSQLServer" for information on this event.
|Private comment: Subscribers only. See example of private comment|
|Links: Microsoft event 14151 from source MSSQLServer|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
Send comments or solutions
- Notify me when updated