Just installed SQL Server 2K5 SP1-default install-using local acct-copied new
db from another server-configured snapshot and merge agent using impersonate
SQL settings ok-ran snapshot ok-ran merge agent and saw this in Monitor
details
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'-error 18456.
Why are snapshot and merge different w/ regard to security?
What am I doing wrong?

Can you ensure that the SQL Server Service accounts and SQL Agent accounts
run under a local admin or a domain admin account. It seems like you have
configured the replication components to impersonate the accounts that SQL
Server and SQL Server Agent runs under and these accounts run under the
local system account which don't have the rights necessary for replication.

--
Hilary Cotter

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]

I have setup an Admin accessible acct. under services for SQL Server and SQL
Agent
In Snapshot security settings, I use SQL Server Agent service acct for
Snapshot Agent process and SQL Server login acct. for connect to Publisher.
In Merge security settings,I use SQL Server Agent service acct for Merge
Agent process and SQL Server login acct. for Subscriber connection.
still getting NT Authority/Anonymous login failure when run Merge, but I do
not know where this is coming from.

running a merge (push) publication

Continuing on w/ the replication saga:
still getting NT Authority/Anonymous login failure when run Merge, but I do
not know where this is coming from.
One concern I had: the db I am creating a PUB on was once used in
replication as the MSmerge_PAL object still exists-the only way I can figure
to remove is script out the db tables, sp, etc. needed and re-create new
db-start over w/ replication.

I would like to know if anyone has the following issue:
I have a tablet PC setup as WORKGROUP-this will be the PUB
I have a stand-alone server on WORKGROUP-this will be SUB
Now the Merge security allows for domain or machine name. However, when
enter machine\username (where machine is the computer name) I get invalid
Windows user, but this user has Admin rights and is the db owner.


[quoted text, click to view]