Prev: The job step improperly defined error
Next: Cannot Subscribe Using Windows Synchronization Manager
From: Oliver Graeser on 8 Feb 2007 11:04
Hi everyone,

hopefully someone here can shed light on this, I've run out of ideas....

I'm running two SQL2005 SP1 servers here, Windows authentication only,
so far everything works fine. I'm managing them either through the
Management studio on my laptop as well as directly.

I want them to replicate data using a transactional replication with
updateable subscriptions. I followed the steps lined out in the online
help, works fine so far for the publication. Then I start the wizard for
the subscription. I've tried either ways push or pull subscription, both
ways I get to the point where the wizard asks about the login for
updateable subscriptions. It offers me the choice to set up a linked
server for this purpose, but this would require a SQL Server Login and I
want to use Windows Authentication only. So I figure I have to go with
the option 'Use a linked server or remote server that you have already
specified'. So, I set up linked servers, activated the capability to use
rpc, so far so good. However, the 'Security' page of the linked server
was something I didn't understand. At this point, however, I'm clueless
how to tell the server which authentication to use. To me it seems as if
I should redirect a local account to a remote account. However, both
servers are part of the same domain, so I've just added the process
login (which currently is dbowner for all databases, just to exclude any
issue here), which should be impersonated. When the system tries to
establish the subscription, I always get the same error message:

TITLE: New Subscription Wizard
------------------------------

Unable to set the Publisher login for the updatable subscription. You
may have to set this up directly on the Subscriber machine using
sp_link_publication.

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)

------------------------------

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Changed database context to 'RPK_testdb'. (Microsoft SQL Server, Error:
18456)

For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------



Any ideas, comments or hints are thankfully appreciated...

Regards,

Oliver
 | 
Pages: 1
Prev: The job step improperly defined error
Next: Cannot Subscribe Using Windows Synchronization Manager