SQL Server 2005 tranactional replication

I have become totally frustrated trying to setup a transactional replication between 2 SQL servers.  Currently, I have the publication pushing to the secondary machine with only 1 small table.  When I view the Relication Monitor, the message "The concurrent snapshot for publication 'trsmain' 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."  That's as far as I can get.  I have rebooted both servers multiple times with the same results.

Where am I going wrong?
LVL 1
shagemanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rob_farleyCommented:
Transactional replication needs a snapshot of the article as a starting point for the subscription (which it can then apply the transactions to). It sounds like your snapshot hasn't been made correctly. Can you go into your publication and tell it to make a new snapshot?

Rob
0
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
Kindly take a Full backup of your database followed by a transactional log backup in your publisher and then apply it in Subscription in the same order to make it work.
0
rob_farleyCommented:
So...

On the publisher, go to the Local Publications folder (under Replication), and right-click on the publication you're after. Choose "Reinitialize all subscriptions".

You then get a dialog box that includes an option to "Use a new snapshot". Choose this one, and tick the "Generate the new snapshot now" checkbox too. Then hit the "Mark for reinitialization" button, and see how it goes.

Alternatively, open the Replication Monitor. Drill down to the publication you're after, right-click on it and choose "Generate snapshot".

Either of these methods should generate a snapshot of the table being replicated, so that the subscriber can pick it up and apply it.

You should also be able to right-click on the publication and choose "View snapshot agent status" to see if it's reporting any errors.

Rob
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

rob_farleyCommented:
rrjegan17,

This isn't mirroring, it's replication. A snapshot of the article being replicated is what's required, not a full database backup.

Rob
0
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
Oops.. Typed in a hurry and haven't read the question completely.
0
shagemanAuthor Commented:
Rob,

Great, followed your advice, first Reinitialized all Subscriptions and chose to create a new snapshot.  Then, just to make sure, I launched the Replication Monitor and chose my subscription, just to make sure I clicked Generate Snapshot.  Did all that, when to the publication which should be receiving the transactions (as I am pushing the publication), and the same message appears when I choose, "View Synchronization Status."

The concurrent snapshot for publication 'trsmain' 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 publicat
0
rob_farleyCommented:
Ok. Can you view the Log Reader status?
0
shagemanAuthor Commented:
3 transaction(s) with 4 command(s) were delivered..  But, still the Row Count on the target machine is 0.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rob_farleyCommented:
If you use Snapshot replication, does it get the snapshot across okay?

I find it strange that the article is empty on the subscriber - makes me think the filter isn't right or something.

Rob
0
Guy Hengel [angelIII / a3]Billing EngineerCommented:
question: did you schedule the replication agents accordingly?
check in the article settings => scheduling, or in the sql agent's job folder, you will see the replication jobs.
if you see "your" job, check if it is set to run in regular intervals.

otherwise, replication won't "run".
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.