May 31, 2013 at 6:51 am
I have a two server configuration where the distribution db is on another server and the publisher is on a second server. I have setup the distribution db just fine (SQL2008R2 SP2) and when I configure the Publisher on SQL2008 SP3 it works but when the replication starts it gets a failed login.....
The login is right and the password is correct. I don't understand why this thinks the password is incorrect. In the Publication I chose the option of RUn under SQL Server Agent Service Account so I didn't have to supply the password....
Message
Replication-Replication Snapshot Subsystem: agent failed. The replication agent had encountered an exception.
Source: Replication
Exception Type: Microsoft.SqlServer.Replication.ConnectionFailureException
Exception Message: Login failed for user
Message Code: 18456
Replication-Replication Snapshot Subsystem: agent failed. Unable to start execution of step 2 (reason: Error authenticating proxy system error: Logon failure: unknown user name or bad password.). The step failed.
May 31, 2013 at 7:10 am
Try starting SQL Server Agent with administrator priviliage and password, I guess your Sql Server Agent is running on Local System Account.
May 31, 2013 at 7:13 am
Bhaskar.Shetty (5/31/2013)
Try starting SQL Server Agent with administrator priviliage and password, I guess your Sql Server Agent is running on Local System Account.
No it is using the service account already. It has admin rights. I don't understand where it thinks the password is bad. It wasn't supplied because I used the option of Run under SQL Server Agent service account... that is what is confusing.
May 31, 2013 at 7:17 am
Sql Server Agent also must be running with user credentials, check whether that credentials are right !!
May 31, 2013 at 7:26 am
These are the rights of the service ID:
Act as Part of the Operating System = SeTcbPrivilege
Bypass Traverse Checking = SeChangeNotify
Lock Pages In Memory = SeLockMemory
Log on as a Batch Job = SeBatchLogonRight
Log on as a Service = SeServiceLogonRight
Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
Increase Quotas = SeIncreaseQuotaPrivilege
Perform Volume Maintenance Tasks
Adjust Memory Quotes for a process
May 31, 2013 at 7:46 am
The odd part of this setup is that both servers are on different domains and use different service IDs to run SQL Server.
I just setup replication between two servers that are on the same domain and both use the same service ID and it works as it should. I am missing one piece of something on my problem child replication but I have no idea what that piece is.
June 3, 2013 at 10:59 am
I figured out the problem. I did not have the service account ID that runs on the distribution sql server as a login/user on the publisher. Stupid oversight on my part.
It is working now. MSFT Support helped me trace it down to that.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply