merge Agent-login failure

I have 2 servers running on workgroups; merge replication
running SQL Server 2005 on each, snapshot running ok, start merge agent and
get this.
Error messages:
The merge process could not connect to the Publisher 'XXUSSHU18UT:Process'.
Check to ensure that the server is running. (Source: MSSQL_REPL, Error
number: MSSQL_REPL-2147198719)
Get help: http://help/MSSQL_REPL-2147198719
The process could not connect to Publisher 'XXUSSHU18UT'. (Source:
MSSQL_REPL, Error number: MSSQL_REPL20084)
Get help: http://help/MSSQL_REPL20084
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (Source: MSSQLServer,
Error number: 18456)
Get help: http://help/18456
The easiest solution if you don't want to investigate the trust issue is to
switch the merge agent to be running under a SQL Server Login.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi,
I had similar problem few years ago when I was new to merge replication on
SQL Server 2000.
Create same windows account on both servers with same user name and same
password, run sql server end sql server agent on it and use this security
option for merge agent:
1. Run under SQL Server Agent service account
2. By impersonating the process account.
"bt7403" wrote:

> I have 2 servers running on workgroups; merge replication
> running SQL Server 2005 on each, snapshot running ok, start merge agent and
> get this.
> Error messages:
> The merge process could not connect to the Publisher 'XXUSSHU18UT:Process'.
> Check to ensure that the server is running. (Source: MSSQL_REPL, Error
> number: MSSQL_REPL-2147198719)
> Get help: http://help/MSSQL_REPL-2147198719
> The process could not connect to Publisher 'XXUSSHU18UT'. (Source:
> MSSQL_REPL, Error number: MSSQL_REPL20084)
> Get help: http://help/MSSQL_REPL20084
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (Source: MSSQLServer,
> Error number: 18456)
> Get help: http://help/18456
|||connect to the publisher in SQL Server Management Studio, expand the local
publication folder, expand your publication, right click on the Subscriber
and select properties. In the Security Agent process account section click
on the three ellipses and enter a windows account which has in the dbo role
on the publication database or is in the PAL.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"bt7403" <bt7403@.discussions.microsoft.com> wrote in message
news:717FD769-249F-40EC-9425-116738AA1740@.microsoft.com...
>I have 2 servers running on workgroups; merge replication
> running SQL Server 2005 on each, snapshot running ok, start merge agent
> and
> get this.
> Error messages:
> The merge process could not connect to the Publisher
> 'XXUSSHU18UT:Process'.
> Check to ensure that the server is running. (Source: MSSQL_REPL, Error
> number: MSSQL_REPL-2147198719)
> Get help: http://help/MSSQL_REPL-2147198719
> The process could not connect to Publisher 'XXUSSHU18UT'. (Source:
> MSSQL_REPL, Error number: MSSQL_REPL20084)
> Get help: http://help/MSSQL_REPL20084
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (Source:
> MSSQLServer,
> Error number: 18456)
> Get help: http://help/18456
|||Problem solved:
under SQL Security, I had to create a GUEST acct. and map this user to the
PUB db. Under Subscription Properties-Removed use of SQL Server Agent
service acct. and used Windows acct-maintained SQL Server Auth for Subscriber
connection.
Merge ran fine.
A side note:
Snapshot security settings do not require fine-tuning like Merge does.
I run this under SQL Server Agent service acct. and use SQL Server login for
connection to PUB.
thx. for your replies.
"Hilary Cotter" wrote:

> connect to the publisher in SQL Server Management Studio, expand the local
> publication folder, expand your publication, right click on the Subscriber
> and select properties. In the Security Agent process account section click
> on the three ellipses and enter a windows account which has in the dbo role
> on the publication database or is in the PAL.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> 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
>
> "bt7403" <bt7403@.discussions.microsoft.com> wrote in message
> news:717FD769-249F-40EC-9425-116738AA1740@.microsoft.com...
>
>
sql