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

sql server replication

group:

Merge Replication Error


Merge Replication Error SAL
8/14/2007 9:20:47 AM
sql server replication: Hello,
I have a publiction on my development box using SQL Server 2005 developer
edition. I created a subscription for my test box, sitting next to me,
intialized and synchronized with the subscriber. I also have SQL Server
Express installed on my development box. I created a subscription for this
server and tried to initialize and sychronize with that subscriber. However,
the subscription never appears in that servers Local Subscriptions list.
The SQL Server Agent is running under a domain account that we use for
replication and this account has the neccessary permissions on each
subcribers machines including my dev box. However, I get the error:

The job failed. Unable to determine if the owner (domain\username) of job
MachineName\SQL2005-Weed-WeedMerge-MachineName\SQLEXPRESS-14 has server
access (reason: Could not obtain information about Windows NT group/user
'domain\username', error code 0xea. [SQLSTATE 42000] (Error 15404) The
statement has been terminated. [SQLSTATE 01000] (Error 3621)).

When I view the job history.
Can anyone help me with this?

S

Re: Merge Replication Error Hilary Cotter
8/15/2007 12:00:00 AM
You might also want to consider using a SQL account for the merge agent.

--
relevantNoise - dedicated to mining blogs for business intelligence.

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 Error Paul Ibison
8/15/2007 2:42:01 AM
Just changing the job owner to sa should do it.
Cheers,
Paul Ibison
Re: Merge Replication Error SAL
8/15/2007 9:58:28 AM
Hi Paul,
I did try that but what finally worked was changing the account that SQL
Server runs under to the account that it couldn't determine if it had access
rights.

So, event though the owner of the job was the domain replication account,
SQL Server Express was running under a different account and the job was
actually running under my acccount. I change SQL Server Expresses log on
account to me and it started working. This only seemed to be a problem on my
dev server for some reason.

Thanks again.
S

[quoted text, click to view]

AddThis Social Bookmark Button