Transactional Replication - Snapshot is not getting applied to subscriber

  • Hemant Korde

    Mr or Mrs. 500

    Points: 532

    Need Help:

    I have looked everywhere but I cannot find help for this specific topic. Any help to pinpoint the problem and how to fix it will be highly appreciated:

    We are running SQL Server 2005. I have created a trans replication on a single subscriber. Both servers are in the same network (no MPLS required for data transfer). When I looked at the snapshot agent, it shows sucessfully completed status. I can also see the snapshot folder. Logreader is running and shows number of articles transferred. Distributor shows it is running sfor over 9 hours since I initially created the replication. However, nothing is getting applied to the subscriber.

    Can anyone gone through the same problem, list out what I need to check and how to fix this problem. I am unable to find exact answer anywhere on the internet.

    Thanks.

    HK

  • David Benoit

    SSC-Dedicated

    Points: 34562

    In SSMS connected to the Publisher, expand Replication, Local Publications, Select the publication you are referring to and expand, right click on the subscription select "View Synchronization Status" and let me know what you see. Also right click on the publication and select "View Snapshot Agent Status" and provide that information.

    Thanks.

    David

    @SQLTentmaker

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • Hemant Korde

    Mr or Mrs. 500

    Points: 532

    Thank you for your quick response. I appreciate your help.

    I looked at the Replication in question. The snapshot Agent is showing that the snapshot was generated (in 4:02 minutes). Aslo, the syncronization status is showing in progress and shoeing transactions being processed. No error anywhere, not even in Replication Monitor which shows status excellent.

  • David Benoit

    SSC-Dedicated

    Points: 34562

    Ok, since you are not seeing anything on the subscriber, we need to make sure that you are indeed sending it to the correct subscriber. You will need to expand the publication and right click on the subscription and select Properties. Please verify the Subscriber is the correct server and the Subscription database is correct as well. Check the Status also and let me know what you see.

    David

    @SQLTentmaker

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • Hemant Korde

    Mr or Mrs. 500

    Points: 532

    David, thank you so much. You solved my probelm. I did find that the publisher was sending it to the wrong subscriber. I had checked this erlier but must have missed the name, we have several subscribers with similar names. After your email, I rechecked and found the error.

    Greatly appreiate it.

    Hemant

  • David Benoit

    SSC-Dedicated

    Points: 34562

    Great. Glad that worked. If that wasn't the issue I was going to be hitting the "stumped" button pretty quickly. 🙂

    David

    @SQLTentmaker

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • Hemant Korde

    Mr or Mrs. 500

    Points: 532

    dave,

    Sorry, I take that back. I was looking at the wrong subscription propertiers this morning. Meaning, the correct subscription property is showing correct publisher and subscriber. However, the syncronization is showing below message, if you can explain what that means..

    The concurrent snapshot for publication 'ADT_Tables_For_100.60' 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 fo[/b]

    Thanks again,

    Hemant

  • bodadheeraj

    SSC Enthusiast

    Points: 148

    Check the Publication Properties-->Snapshot-->Location of snapshot Files-- Make sure put files in the default folder is checked, in my case it was't check marked instead put files in the following folder was checked with a location address(C:\REPL) but i had my distributor in a different server other than publisher and the location address was misleading to distributor agent .

Viewing 8 posts - 1 through 8 (of 8 total)

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