all groups > sql server replication > may 2007 >
You're in the

sql server replication

group:

merge replication - user (null)


merge replication - user (null) Darin
5/30/2007 2:27:09 PM
sql server replication: I have customer that is setup for merge replication (SQL 2000) and
everything WAS working fine. Now, they are receiving an error in the
error details of the merge agent:

Login failed for user '(null)'. Reason: not associated with a trusted
SQL Server connection.


I need to get it setup so all of the data can get replicated because the
two sites have been working for a while without it replicating.

How can I change the replication connection to use SQL security since I
can use an SQL login that we have setup?

I tried changing the Remote Servers setting for the remote server to Map
all remote logins to sql_login, but that made no difference.

Thanks for you prompt assistance.

Darin

Re: merge replication - user (null) Hilary Cotter
5/30/2007 11:09:55 PM
Confirm that the account that you are logging into the publisher is in the
PAL and that the account you use to login to the distributor is in the
dbo_role in the distribution database. You can edit the job to make these
changes.

It is possible that you were using sql authentication and someone changed
the publisher to use windows authentication only.

--
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
[quoted text, click to view]

Re: merge replication - user (null) Darin
5/31/2007 4:11:15 AM
the sql user is the same on both the publisher and the subscriber, and
on both it has dbo and sys admin properties.

What is the PAL? If that is the publication access list, then the sql
login is listed.

Would I change the distributorsecuritymode to something other than 1?
And is that how it accesses the distributor or the subscriber?

Darin

AddThis Social Bookmark Button