sql server replication: Joe
there is an article about troubleshooting these errors
http://support.microsoft.com/?kbid=834124 that you might like to look at
The relevant section explains

The following list describes two possible causes for this problem

The SQL Server service uses an account that does not have sufficient administrative credentials on the Windows domain. In this situation, the xp_logininfo system stored procedure is run by using the security context of the SQL Server service. Because the account does not have sufficient administrative credentials to enumerate the properties of the user in the domain, the xp_logininfo system stored procedure fails, and you receive the 8198 error
To resolve this problem, change the startup account of the SQL Server service to a Windows domain account

The SQL Server services and the SQL Server Agent services on the Publisher and on the Subscriber use security contexts of different Windows domains
To resolve this problem, use either of the following two methods.
Use the same Windows domain user account to run the SQL Server services and the SQL Server Agent services
Create a Windows domain user account on the Publisher and on the Subscriber that have identical user names and passwords

If you try the recommended solutions and have no success there is a known issue and hotfix available
http://support.microsoft.com/default.aspx?kbid=830596
HTH
Paul Ibiso

Joe
try making the replication job owner 'sa' - in that way the lookup won't be performed
HTH

After I successful ran the snapshot agent and create the snapshot for a
Published Northwind database, the merge agent still not run with the error
shown below. How do I fix this problem and get the merge agent to start
merge replication with subscriber? Please list the steps to take.

ERROR MESSAGE:
The job failed. Unable to determine if the owner (MyDomain\administrator)
of job Replication agents checkup has server access (reason: Could not
obtain information about Windows NT group/user 'MyDomain\administrator'.
[SQLSTATE 42000] (Error 8198)).

This is insane, I wanted to setup replication across two
non-trusted(completely different) domains that's why I setup SQL server upon
Windows 2000 application Servers (without Active Directory). Then I setup
up a Windows Local Account (.\SQLAdmin) on the Distributor SQL server to
start the SQL Service and SQL Agent as .\SQLAdmin. It had successfully
create the initial snapshot of the published database. But the merge agent
will not run because of the ERROR MESSAGE.
I've intentionally used Windows Local Account (and avoid using a Windows
DOMAIN ACCOUNT) so that I could setup the same pass-through
account(.\SQLAdmin) in two different domains so that I could use SQL
authentication to replicate between the two different non-trusted domains.
Now people are telling me that I must use a Windows Domain Account to avoid
error 8198. This is driving me in circles........
What must I do to get the Merge Agent to run under the Windows LOCAL
ACCOUNT????? Please list the steps. Thanks.


[quoted text, click to view]

Paul,

This is insane, I wanted to setup replication across two
non-trusted(completely different) domains that's why I setup SQL server upon
Windows 2000 application Servers (without Active Directory). Then I setup
up a Windows Local Account (.\SQLAdmin) on the Distributor SQL server to
start the SQL Service and SQL Agent as .\SQLAdmin. It had successfully
create the initial snapshot of the published database. But the merge agent
will not run because of the ERROR MESSAGE.
I've intentionally used Windows Local Account (and avoid using a Windows
DOMAIN ACCOUNT) so that I could setup the same pass-through
account(.\SQLAdmin) in two different domains so that I could use SQL
authentication to replicate between the two different non-trusted domains.
Now people are telling me that I must use a Windows Domain Account to avoid
error 8198. This is driving me in circles........
What must I do to get the Merge Agent to run under the Windows LOCAL
ACCOUNT????? Please list the steps. Thanks.
[quoted text, click to view]
administrative credentials on the Windows domain. In this situation, the
xp_logininfo system stored procedure is run by using the security context of
the SQL Server service. Because the account does not have sufficient
administrative credentials to enumerate the properties of the user in the
domain, the xp_logininfo system stored procedure fails, and you receive the
8198 error.
[quoted text, click to view]