September 27, 2010 at 9:35 pm
Hey all,
I am attempting to test setting up transactional replication on two computers on a network. One has Windows XP and the other Vista. Both are running SQL 2008.
So I enabled distribution on both computers, with them both storing information on one computer. I enabled the database to be replicated to publish on both servers, ran subscriptions, publications, etc. I also mapped my username to be able to access both databases as a dbo (the computers are on a domain).
I also permissioned all system processes (System, SQLAgent, etc.) to access the database on Blue (although I'm not clear on how to permission it to access on the computer without the distribution database, since they're not showing up in the Logins on that computer even though SQL Agent is running on both computers.
Let's call one computer Blue, another Green. The distribution database is on Blue. I look in replication monitor, and the distribution agent on both are errored out (even before there are any commands to be distributed). The Green log just says that it's retrying a step after an error.
The Blue log, however, says "The process could not connect to Green" and "Login failed for user 'TheDomain\Blue$'. This message confuses me, because I don't see a user that's named after my computer on the domain. I tried adding it as a user to one of the databases, and it couldn't find it.
Does anyone have any insight into what this login could be referring to (i.e. the name of the domain-backslash-name of the machine-dollar sign). I thought that maybe this was referring to the username the SQL Server Agent uses but it's not listed by the same name under Logins and I already thought I permissioned that login to have access).
I would appreciate any advice anyone can give.
September 27, 2010 at 10:14 pm
Question deleted, as I had mis-read the post.
September 28, 2010 at 6:57 pm
Hey all,
A colleague of mine helped me resolve this issue. I'm sorry if my description of the problem wasn't clear. I usually like to follow up on my posts to describe a solution if I find one so that it may be useful to someone in the future.
The issue was the credentials the SQL Agent service was using, as specified in services.msc. Thus, it wasn't an issue of specifying the permissions in SQL Server Management Studio, but services.msc on the two computers.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply