adding a third subscriber, can't impersonate agent process account

[OceanDeep via SQLMonster.com]

We are using SQL 2008 std 64 bit on windows 2008 64 bit and are using push
transactional replication and distribution db is on the same server as the
publisher. We have been replicating from SQL 2008 to two SQL 2005 boxes for
over 2 years. Recently we added a third SQL 2008 std R2 box as the third
subscription. After setting up the subscrption connection with impersonate
agent process account (windows Authentication) which is how I set up for the
other two SQL 2005 subscriptions, I get the error saying "The process could
not access database 'xxx' on server xxx.'. It wil work if I change it to
connect as a SQL user account which has the dbo or sa right.

I compared this new server with other two servers, they are all on the
domain and have the same local account to start all sql services. On the
other hand, the account that starts the publsher SQL service is a domain
account and I give it the admin right on the third subscriber server.

The only difference in this new subscription is that this third server is SQL
2008 r2 on windows 2008 vs the two SQL 2005 subscribers on windows 2003. Is
there some security setting I need to deal with? Does this box need a
domain account to start its sql services? I don't think so but who knows.

Is it ok to stop the distribution service for this new server so I can reboot
it? The pending transactions from the publisher should be delivered to it
when it is up, right?

ANy help on this is very much appreciated.

od

--
Message posted via http://www.sqlmonster.com

[Ben Thul]

To answer your question about reboots, any server in the replication
topology can be rebooted at any time and not risk data ultimately
arriving at the subscriber(s). This is also true for the replication
agents (log reader and distribution). When they're back up, they'll
pick up where they left off. HTH!
--
Ben