Thanks, I had found that article, and also thought that was the answer, but
alas, it did not solve the problem.
I have tried to set the logins in the remote, and the linked servers to all
be the sa account. I thought I got everywhere, but obviously something is
missing. Is it possible that it is not trying to long on a SQL account, but
a Windows account, or that the publisher/distributor is expecting a Windows
account. I am sure from the error message it is trying to logon to the sa
account, but if that is not what the publisher/distributor is expecting,
then it is obviously not a match.
Is there somewhere I can turn up the logging level to get more detail in the
SQL or Event logs?
[quoted text, click to view] "Narayana Vyas Kondreddi" <answer_me@hotmail.com> wrote in message
news:%2334Ito1PDHA.1148@TK2MSFTNGP11.phx.gbl...
> See if you are running into this problem:
>
http://vyaskn.tripod.com/repl_ans4.htm#linkpubl >
> --
> HTH,
> Vyas, MVP (SQL Server)
>
http://vyaskn.tripod.com/ > What hardware is your SQL Server running on?
>
http://vyaskn.tripod.com/poll.htm >
>
>
>
> "cycleguy" <cycleguy@bikerider.com> wrote in message
> news:vg180q41pvn264@corp.supernews.com...
> I have two servers in different domains (W2k and one in NT). The Publisher
> and Distribution server are the same server in Dallas(NT). The subscriber
> server is in London (w2k). Some of the tables need to be updateable from
> London, others are read only and Snapshot replication works for them. For
> the updateable, I set them up as transaction replication with both
immediate
> and queued updating by the subscriber. Replication for all tables works as
> expected from Dallas to London, but on the updatable tables, I get an ODBC
> error that it can't log into the sa account. The sa account has the same
> password on both ends. Both are set up for Windows and SQL authentication.
>
> What am I doing wrong.
>
>
>
>
