Re: URGENT-- Replication blown up.
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Sat, 27 May 2006 06:44:24 -0400
Reboot both boxes. Starting with the publisher. There is a condition where
the log reader hangs on start. It sounds like you have hit it.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ChrisR" <ChrisR@xxxxxxxxxxx> wrote in message
news:uVwgVyUgGHA.3756@xxxxxxxxxxxxxxxxxxxxxxx
More info...
When I try to configure replication on the Publisher, I get a message that
it cant connect to the distributor. I have made certain though that these
two boxes can communicate.
"ChrisR" <ChrisR@xxxxxxxxxxx> wrote in message
news:esN6FzRgGHA.4196@xxxxxxxxxxxxxxxxxxxxxxx
Pull Subscription, Remote Distributor (on the Subscriber), not Immidatethem
Updating, Tranascactioal Replication with both boxes SQL2K SP4.
I have no idea what to do here. I highlight Log Reader Agent and all of
simply say "The step did not generate any output. The step failed". IRClick
and start and it delivers the awaiting transactions, but then the above
message appears again.
Any ideas???
TIA, Chris
.
- Follow-Ups:
- Re: URGENT-- Replication blown up.
- From: ChrisR
- Re: URGENT-- Replication blown up.
- References:
- URGENT-- Replication blown up.
- From: ChrisR
- Re: URGENT-- Replication blown up.
- From: ChrisR
- URGENT-- Replication blown up.
- Prev by Date: Re: URGENT-- Replication blown up.
- Next by Date: Re: Anonymous Merge in 2005
- Previous by thread: Re: URGENT-- Replication blown up.
- Next by thread: Re: URGENT-- Replication blown up.
- Index(es):
Relevant Pages
|