Groups | Blog | Home
all groups > sql server replication > april 2004 >

sql server replication : The process could not connect to Subscriber 'Server2'


Ajit
4/7/2004 10:25:29 AM
Hi,

I am trying to replicate my database in SQL-Server on Server1 to Server2
Its a Transactional Replication using push method.

I am getting the following error and unable to figure out why.

Can anyone help me out with this ?

----------------------------------------------------------------------------
-----------------------------------
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
(Source: Server2 (Data source); Error number: 18452)
----------------------------------------------------------------------------
-----------------------------------

Ajit
4/7/2004 11:29:50 AM
Paul,

I am very sorry if am asking any lame q as am a new to replication.
i am using mixed authentication(SQL Server and Windows)
and i have updatable subscriber.

to get it working i also tried using snapshot method and it gives the same
error.

I don't know if this has to do something with replication but my SQL-Server
Startup Service account is administrator.

rgds,

Ajit.

[quoted text, click to view]


Ajit
4/7/2004 2:59:18 PM
Paul,

Thank you very much it worked.
I appreciate all your help.

best regards,

Ajit.

[quoted text, click to view]

Paul Ibison
4/7/2004 7:00:35 PM
Ajit,
normally this means that you are trying to use SQL Server security and the
server is set up to only allow Windows logins. If this is the case, you can
make your agent impersonate the SQL Server agent account or alternatively
switch the server to allow mixed authentication. If you have updatable
subscribers it would mean something different - that you have to use
sp_link_publication.
HTH,
Paul Ibison

Paul Ibison
4/7/2004 8:21:27 PM
Ajit,
replication agents are jobs run by the sql server agent service. This
service needs to be a domain user and have the correct rights on the
databases involved (see BOL replication, security). As an easy way, you can
set the publisher/distributor and subscriber sql server services to all use
the same domain user which needs to be a local administrator on the boxes
involved.
HTH,
Paul Ibison

AddThis Social Bookmark Button