I have a SQL Server 2008 database, and I need a merge replication because I want to sync with mobile devices afterwards.

So I created a replication but when it comes to start the snapshot agent, the agent tries to start for about 20 minutes and then it shows the message:

The replication agent has not logged a progress message in 10
minutes. This might indicate an unresponsive agent or high system
activity. Verify that records are being replicated to the destination
and that connections to the Subscriber, Publisher, and Distributor are
still active.

There aren't any other error messages, neither in the snapshot-agent-status-window nor in the agent-log-window.

I don't have the administrator of the domain, but the local administrator and a domain user with admin-privileges. Both have all rights to database, are in the access-list of the replication.

The server agent runs on the local administrator-account and there are *3 Merge Replications working on the server *

The job runs also under the local administrator.

  • I found a entry in the Log: [298] SQLServer Error: 15404, Could not obtain information about Windows NT group/user 'DOMAIN\Administrator', error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin) Does this problem has something to do with my initial problem?
    – abc
    Commented Jul 31, 2012 at 12:04
  • DOMAIN\Administrator is likely the domain admin account and error code 5 is usually an access denied error. While I can't say it's related to the replication problem, it certainly seems like an issue to resolve.
    – Jon Seigel
    Commented Jul 31, 2012 at 16:08

1 Answer 1


So it works again...

Maybe someone else has got the same issue one day, so i post the solution here:

I researched on the server and found out, the sql server service is running under a local user. The reason for this is, that there were problems with the backupsystem, used by our customers and so they changed it years ago.

Because of the local user account the 15404-Error occures.

Knowing, that i mustn't use domain-accounts, I also solved the initial problem with my snapshot-agent. I searched for hours (nearly days ;) ) and it was just this little change:

When the Replication is created, the job is created too. The job has three steps. The Job-owner is the local-admin, also for the server-agent-service. But the second step of my job (replictionsnapshot) has one setting: run as. And by default this isn't the job-owner but the user running the creation, in my case my domain-account.

Now, that I set it to the local-administrator as well everything works fine again.

Thanks, Karl

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.