November 1, 2012 at 1:02 pm
Greetings all,
I'm having an issue with transactional replication between two SQL2008R2 servers. I keep getting login failed for the snapshot agent. The replication agent starts up fine, but the Snapshot agent consistently fails to even log in.
I have tried a domain service account with: Permission to the folder, admin on the box and DBO on the database containing the replicated tables on both publisher and subscriber sides.
I have also tried my own domain credentials that have admin rights on literally everything, all servers as well as every SQL instance and database, just to see if it worked and no dice...
Error messages:
Message: Login failed for user 'DOMAIN\USERID'.
Stack: at Microsoft.SqlServer.Replication.ServerConnectionEmulator.Connect()
at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.EstablishPublisherConnection()
at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot()
at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun()
at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: MSSQLServer, Error number: 18456)
Get help: http://help/18456
Server SQL*****\*****, Level 14, State 1, Procedure , Line 65536
Login failed for user 'DOMAIN\USERID'. (Source: MSSQLServer, Error number: 18456)
Get help: http://help/18456
Any and all help is greatly appreciated.
November 5, 2012 at 4:06 pm
Thanks much for the link. I was able to get it to work using the Agent... Not exactly best practice, but it's going. I just found it really odd that the rep agent was ok, but the snapshot agent wouldn't go, even when using the same creds for both.
The link you provided will get me going when I'm able to revisit this. Unfortunately I don't really have the time right now. I'm the new and only DBA in a 30 server 300 database environment that hasn't had a full time DBA for several months. Fun times.
Again, really appreciate the help. Thank you.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply