snapshot is not applied to both of the two subscribers RRS feed

  • Question

  • We have six publications that have a shared distribution agent.  When articles are added to one of the six publications and the snapshot is created, the snapshot is not applied to both of the two subscribers.  It is sometimes applied to one subscriber but not the other, sometimes both, sometime neither.

    The agent has this message:
    The concurrent snapshot for publication 'EnterpriseToDist04' 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 t


    Tuesday, October 29, 2019 12:54 PM

All replies

  • The snapshot should be applied to both subscribers. The shared distribution agent is slower than independent agents. I suggest you rework your subscription for this.

    The message you get most commonly relates to the snapshot agent not completing, or the log reader agent not reading the watermark saying the snapshot is complete. Sometimes a reinitialization will be necessary to force the snapshot to be applied. The reinitialziation will not require a full snapshot generation.

    Tuesday, October 29, 2019 2:06 PM
  • Hi juniorkiran,

    A shared agent services multiple subscriptions; if multiple subscriptions using the same shared agent need to synchronize, by default they wait in a queue, and the shared agent services them one at a time. It will have a time latency. But it will still synchronize all subscribers. For your agent message, please try to stop all the replication jobs, reinitialize subscription, start snapshot replication job wait to complete snapshot job then run log reader and distribution. 

    Best regard,

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact

    Wednesday, October 30, 2019 8:57 AM
  • Turns out this occurred because of blocking on the publisher.  We had to create and apply the snapshot at very low activity times.  

    David z

    Tuesday, November 5, 2019 2:49 PM