When I attempt to set up replication on my local box, I receive the error -'SQLServer Agent uses the Systems Account, which causes replication betweem servers to fail'.
Why does this happen? And can I overcome this?
Thanks :)
BiancaStart SQLServerAgent service using a domain account. This account must have the appropriate rights on teh Publisher, Distributor and Subscriber computers (depending on the replication type)
Originally posted by Bianca_J
When I attempt to set up replication on my local box, I receive the error -'SQLServer Agent uses the Systems Account, which causes replication betweem servers to fail'.
Why does this happen? And can I overcome this?
Thanks :)
Bianca|||Thank you for your post :)
What is a Domain Account?
Is this set up in Windows 2000? And if I set up a Domain Account in my local Windows 2000 box - how do I have right over a remore server?
Thanks
Bianca
Showing posts with label systems. Show all posts
Showing posts with label systems. Show all posts
Friday, March 9, 2012
Saturday, February 25, 2012
Replication
We have two systems one that has a domain setup and the other is a workgroup. We have them connected over a non-trusted internet connection. We are using SQL Server 2005 Enterprise version, for Peer-to-Peer transactional replication, the server that hasa domain, is called EXT-FRMAC1 and the other one is FRMAC_DC. FRMAC_DC can subscribe to EXT-FRMAC1's publication, but EXT-FRMAC1 can't subscribe to FRMAC_DC, and the error that we get on FRMAC_DC, is that FRMAC_DC\admin - username or password does not exist. admin exists on FRMAC_DC, I am not sure if we should try and put it on a domain or not.
Thanks.
Have you tried to setup with a SQL server account instead of Windows account?
Gary
Labels:
connected,
connection,
database,
domain,
internet,
microsoft,
mysql,
non-trusted,
oracle,
replication,
server,
setup,
sql,
systems,
workgroup
Subscribe to:
Posts (Atom)