SQL Server 2005 DB Replication

[mishbaker]

I am currently trying to setup Replication between two Servers.

I completed the Wizard for my Publication and my Subscription.

The Publication Type: Transactional (w/ Updateable Subscriptions)

So I make a change to the publication server and sure enough it propagated to the subscribing server...pretty fast too. But when I try it from the subscriber server I get this error.

The RPC security information for the Publisher is missing or invalid.  Use sp_link_publication to specify it.

So I used the example at MSDN and ...

-- Execute this batch at the Subscriber.
DECLARE @publication AS sysname;
DECLARE @publicationDB AS sysname;
DECLARE @publisher AS sysname;
DECLARE @login AS sysname;
DECLARE @password AS nvarchar(512);
SET @publication = N'POLRPub';
SET @publicationDB = N'ProjectOLR';
SET @publisher = 'KAFSERV';
SET @login = 'ARSC\Administrator';
SET @password = 'password';

-- At the subscription database, create a pull subscription to a transactional 
-- publication using immediate updating with queued updating as a failover.
EXEC sp_addpullsubscription 
    @publisher = @publisher, 
    @publication = @publication, 
    @publisher_db = @publicationDB, 
    @update_mode = N'failover', 
	@subscription_type = N'pull';

-- Add an agent job to synchronize the pull subscription, 
-- which uses Windows Authentication when connecting to the Distributor.
EXEC sp_addpullsubscription_agent 
    @publisher = @publisher, 
    @publisher_db = @publicationDB, 
    @publication = @publication,
    @job_login = @login,
    @job_password = @password; 
 
-- Add a Windows Authentication-based linked server that enables the 
-- Subscriber-side triggers to make updates at the Publisher. 
EXEC sp_link_publication 
    @publisher = @publisher, 
    @publication = @publication,
    @publisher_db = @publicationDB, 
    @security_mode = 0,
    @login = @login,
    @password = @password;
GO

The account used is the domain administrator and I assigned that account to have DB Owner access. But it fails with Login Failed for user 'ARSC\Administrator'.

I'm new to this and it is my first attempt at replication. Any help, no matter how trivial it seems to you, may be helpful. Who knows what I've overlooked.

Thanks,

All lessons learned from the School of Hard Knocks........at least tuition is cheap.

 

[ptheriault]

Why are you using Transactional w/ Updateable Subscriptions.
Generally you don't want to update the subscriber. IF you do need to update the subscriber why not use merge replication?

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[mishbaker]

I was under the impression, after reading several articles, that merge replication could be iffy and screw up timedatestamp fields, etc..

If that is not the case I'll give it a shot next. That's pretty much where I was heading anyway....too bad I can't use Perr-to-Peer on SQL Server 2005 Standard.


All lessons learned from the School of Hard Knocks........at least tuition is cheap.

 

[ptheriault]

I've never had any problems with Merge replication and I've used it a lot.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[mishbaker]

I'm using merge and it works well. So far...

Thank you.

All lessons learned from the School of Hard Knocks........at least tuition is cheap.

 

[mishbaker]

Ok, so my subscriber now has the database tables. It even added a rowguid to the table. But now I cant add data to those tables on the subscriber. Am I missing something?

All lessons learned from the School of Hard Knocks........at least tuition is cheap.