Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After subscription had been marked for reinitialize, a new snapshot was generated.
Log reader and queue reader agents are running.

But when we try to turn on the synchronizing, we're getting the following error:
The concurrent snapshot for publication 'DBName' is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent for the publication.

Once we got it synchronizing well(no idea how it was, it just started working without our participation), but because of foreign keys(and unsynchronised part of data) we had to reinit it all from start.

Here is our publication properties: publication properties

How to get it synchronising well?

share|improve this question
We found a message in LogFileViewer: Replication-Replication Transaction-Log Reader Subsystem: agent Computer-Name-DBName-1 scheduled for retry. The process could not execute 'sp_replcmds' on 'Computer-Name'. – arena-ru Nov 30 '10 at 12:34
up vote 0 down vote accepted

We've figured out the problem and this is a solution

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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