August 1, 2011 at 1:22 pm
Hello. I apologize if there is already something somewhere on this site about this problem, but I have searched and don't see anything that is exactly what I'm dealing with.
I am working with SQL Server 2005 Standard Edition. We have replication set up (all 3 types) on several of our databases, both within the same server and across to a different server.
This past weekend we migrated to a new server (Windows 2008 R2 Enterprice Edition). I had scripted out the replication from our previous server to create it on the new server. I created everything and set up the jobs and was able to successfully generate all the snapshots.
The problem lies with the transactional replication. It will not distribute. I was able to set up the snapshot replication without a problem via the script. I was even able to set up a new publication/subscription to test it out and it worked.
When I generate the snapshot on the transactional replication, both the snapshot and log reader agent statuses show they were successful. But when I go to view the synchronization status on the subscription, I get this message: "The concurrent snapshot for publication 'PublicationName' 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." The message gets cut off.
Does anyone know what could be causing this?? I am desperate. I don't understand why the snapshot replication is working fine. Several articles I read that mentioned the message I got suggested dropping replication, deleting records, dropping the distribution database, etc. I have already tried deleting a publication/subscription, but it didn't make a difference. And besides, the fact that I created two brand new publications and the snapshot one worked and the transactional one didn't tells me that deleting the publications won't do me any good.
Any help anyone can provide would be GREATLY appreciated!
Thanks!
August 4, 2011 at 9:44 am
You are right, Deleting the Publication is not going to help.
As you have stated, the snapshot replication is working fine. It is the transactional replication that is not working. (Snapshot works for it if I am not mistaken). The T Repl is not working since something is not right with the Distributor. This is tough to fix. The easiest would be to tear down the Distributor completely and redo it.
If you are planning to do that, please keep an eye on the security requirements of Replication in SQL 2008.
-Roy
August 4, 2011 at 12:54 pm
Thanks very much. I actually did end up deleting the subscription and publication, disabling publication/distribution, and setting everything up from the beginning again. Then it worked.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply