Hello--
I'm am having difficulty setting up what I thought would
be something relatively simple to accomplish. I have two
client computers running XP, each using a local copy of
MSDE2000 to store data. I also have a server running
Windows 2000 AS and SQL Server Enterprise.
What I'm trying to do is have the data that's logged on
the client computers replicate to the server. I have run
into a variety of issues, most seem to be related to
security problems. I have all SQL Server instances set up
to use TCP/IP and named pipes, and all set for mixed mode
authentication. I am not using the server as a domain
controller, but I have created matching user accouts with
administrator priviliges on each of the three computers in
question.
When I create a publication on one of the two client
computers, sometimes a snaphot is generated immediately,
sometimes it isn't. When I try to create a pull
subscription on the server, I typically get an error about
being unable to connect to the distributor (I presume
security-releated problems).
I feel as if I'm missing something obvious, because this
seem like a very straightforward setup. What am I doing
wrong?
Thanks in advance for any help.
Chris Langston
exactly how are you connecting to your Publisher? ActiveX, SQM DMO?
If you are using ActiveX controls you have to define the network method you
are using to connect to your publisher/distributor by using
PublisherAddress/PublisherNetwork and DistributorAddress/DistributorNetwork.
If you are pulling a subscription using UNC you will have to ensure that the
SQL Server agent account on the subscriber has rights to the network share
on the publisher. The easiest way to do this is to make sure that the SQL
Server agent account the subscribers run under is the same one that it runs
under on the Publisher and this account is in the local admin group. If you
can't make them the same domain account, give them the same name and
password.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Chris Langston" <clangst@.vectorcorporation.com> wrote in message
news:512901c4807f$6260a7c0$a401280a@.phx.gbl...
> Hello--
> I'm am having difficulty setting up what I thought would
> be something relatively simple to accomplish. I have two
> client computers running XP, each using a local copy of
> MSDE2000 to store data. I also have a server running
> Windows 2000 AS and SQL Server Enterprise.
> What I'm trying to do is have the data that's logged on
> the client computers replicate to the server. I have run
> into a variety of issues, most seem to be related to
> security problems. I have all SQL Server instances set up
> to use TCP/IP and named pipes, and all set for mixed mode
> authentication. I am not using the server as a domain
> controller, but I have created matching user accouts with
> administrator priviliges on each of the three computers in
> question.
> When I create a publication on one of the two client
> computers, sometimes a snaphot is generated immediately,
> sometimes it isn't. When I try to create a pull
> subscription on the server, I typically get an error about
> being unable to connect to the distributor (I presume
> security-releated problems).
> I feel as if I'm missing something obvious, because this
> seem like a very straightforward setup. What am I doing
> wrong?
> Thanks in advance for any help.
> Chris Langston
>
>
Saturday, February 25, 2012
Replication issues with MSDE and SQL Server Enterprise
Labels:
accomplish,
computers,
database,
difficulty,
enterprise,
hello-im,
microsoft,
msde,
mysql,
oracle,
relatively,
replication,
running,
server,
setting,
sql,
twoclient,
wouldbe
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment