Distribution times out...

Tech-Archive recommends: Speed Up your PC by fixing your registry

I have a transactional replication working fine till to date. I have
the publisher on ServerA and subscriber on ServerB. The transactional
replication is running fine...

I need to get a copy of the subscriber to another server and replicate
the Publisher to that serverC while the replication on ServerB is
running.

ServerA.Publisher ---> ServerB.Subscriber (runs transactional
replication)
ServerA.Publisher ---> ServerC.NewSuscriber (This need to run without
impacting ServerB.Subscription). I cannot resynch the databases as It
will take days to resynch and will also kill some of my data on the
ServerB.subscriber that is not in ServerA.publisher

I went with the way they had explained on MSKB 320499. I stoped the
transactions coming into the publisher and copied a full backup of
publisher to ServerC. I created the new subscription wihout re-synch
option to ServerC. I also copied all the sp's that are needed from
ServerB.Subscriber.

When i try to enable the distribution agent between ServerA and ServerC
i get the following error..

{call sp_MSget_repl_commands(11, ?, 0, 7500000)}
Timeout expired
Timeout expired
(Source: ODBC SQL Server Driver (ODBC); Error number: S1T00)
---------------------------------------------------------------------------------------------------------------

The replication agent from ServerA to ServerB is running fine..! (Thank
God..!)

Can anyone help me figure out how to fix this issue between
ServerA.Publisher to ServerC.Subscriber?

Thanks in advance...!

.

Relevant Pages

  • Re: Publishing Subscriber Incorrect delivery of data to subscribers
    ... When you filter a publication, the filter forms a hard barrier on the data ... which is allowed to exist at the subscriber. ... ServerC contains all data for TX ... The problem i have is that changes made at the central publisher are ...
    (microsoft.public.sqlserver.replication)
  • Re: Publishing Subscriber Incorrect delivery of data to subscribers
    ... it you could force the updates to go through by some method, ... be anything to update on the subscriber since the row wouldn't exist. ... the publisher and subscriber in order to determine changes. ... exist on ServerC. ...
    (microsoft.public.sqlserver.replication)
  • Trasactional Replication Times Out...! - Help!!!!
    ... I have a transactional replication working fine till to date. ... the publisher on ServerA and subscriber on ServerB. ... I need to get a copy of the subscriber to another server and replicate ... publisher to ServerC. ...
    (comp.databases.ms-sqlserver)
  • Re: Transactional Replication 2005
    ... replication from production database as the publisher and subscribe it to ... Create the distributor on the publisher server ... I then create the subscriber, ... the identity NFR property setting has to match between publisher ...
    (microsoft.public.sqlserver.replication)
  • Re: Sp_adjustpublisheridentityrange and resetting identity range
    ... > identity ranges you have set on your publisher. ... > ranges which will work for the lifetime of their replication solution. ... > should apply this value on the subscriber. ... >> restored the published database from a backup. ...
    (microsoft.public.sqlserver.replication)