Post reply

snapshot is complete, but subscriber status says it isn't

  • October 9, 2009 at 2:19 pm

    #205439

    We have a transactional publication that fell behind and semed to be hung (could not bring down latency) We decided to recreate the whole publication and subscription. While creating the subscription, I specified – Initialize immediately, with new snapshot, generate snapshot now.

    The state I am currently in is that

    when I select the publication and select “view snapshot agent status” I see  “ [100%] A snapshot of 17 article(s) was generated.”

    But when I select the subscription and select “view synchronization status” I see “The concurrent snapshot for publication 'pubName' 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 public”

    It seems as if the subscription is not talking to the publication. Have you seen this before? This also happens often when we try to reinitialize a subscription.

    Any help is greatly appreciated.

  • October 26, 2009 at 11:20 am

    #1070834

    I have the same situation. I have deleted the subscription, regenerated the snapshot numerous times, checked the permissions and even deleted the database and restored it from a backup. The snapshot is being created, but the subscription is not seeing it. I have even shutdown the log reader agent, stopped the subscription agent, ran the snapshot agent on the publisher, restarted the log reader agent and then restarted the subscriber agent with no difference in out come. I could really use some help too.

    If this is an issue with old or stale distribution command is there a manual command to run that will remove the stale commands? What else could this be?

    Thanks in advance.

  • October 28, 2009 at 9:26 am

    #1071835

    I had this issue when my @sync_type was set to 'replication support only'. I scripted the old replication which was created without sending a snapshot, so when I reran the publication creation scripts the @sync_type remained.

    Not sure if this might be your issue, but it's worth a look.

    Actually now that I think about it, my issue was that the snapshot agent kept saying that 'no subscribers were out of sync' and it wouldn't create a snapshot. Probably a totally different issue.

  • October 28, 2009 at 1:42 pm

    #1072041

    Here is the Solution to the issue I had:

    1. Removed all Subscribers from the Publication.

    2. Delete the Publication.

    3. Recreate the Publication.

    4. Add back the Subscribers.

    I also made sure the security settings were correct on both the publisher and subscriber. I know this sounds like a very general solution, but it is what worked for me in the end.

  • October 28, 2009 at 2:28 pm

    #1072071

    I have had to do the same thing in the past.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply