Merge Replication works then fails, works then fails, and so on

Tech-Archive recommends: Fix windows errors by optimizing your registry

I have a merge replication environment with one central
publisher/distributor and 35 clients. The merge uses continuous
replication. At the moment, 31 of the 35 subscriptions have error this
error:
The process could not check existence of generation at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147201003)
----------------------------------------------------------------------------
-----------------------------------
General network error. Check your network documentation.
(Source: SERVER002 (Data source); Error number: 11)
----------------------------------------------------------------------------
-----------------------------------

Occasionally some will start working again; and then later fail again. I'm
sure that all permissions must be correct because they work 70 to 80 % of
the time. I don't understand why so many fail so frequently though, and
then why they start working again. Also, there are 2 that NEVER fail with
this message.

Any ideas? I do have a separate schedule to restart all the replication
jobs every hour just in case they are not running - but that is a band-aid.

Thanks,

Rob Kraft


.

Relevant Pages

  • Re: Distribution Cleanup Job Fails
    ... No it would not cause replication to fail, ... Make sure that xp_cmdshell is enabled and the SQL Serer agent account has ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: [ANNOUNCE] Ramback: faster than a speeding bullet
    ... disk must be ordered, other it's going to be too unreliable in practice. ... So "perfectly reliable if UPS power does not fail" seems a bit over the ... I was trying to prod you into writing the ordered flushing. ... If you think this is like replication then you have the wrong idea ...
    (Linux-Kernel)
  • Error 21060 w/Rep. Between Access and SQL Server
    ... can choose options for "Immediate Updating" or "Queued ... establish replication both with and without the option ... >between a SQL Server DB and an Access database. ... >push subscriptions for the following Subscribers: ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge replication / non-convergence
    ... replication (dropped distribution database, dropped subscriptions, dropped ... is related to the replication getting messed up when the metadata clean up ... "Subscriptions never expire" option on; ... publications with 12 subscribers. ...
    (microsoft.public.sqlserver.replication)
  • RE: Disable merge publication
    ... Welcome to Microsoft MSDN Managed Newsgroups Services. ... changes will be replicated to your subscriptions and they will be also ... Controlling Constraints, Identities, and Triggers with NOT FOR REPLICATION ... Microsoft Online Community Support ...
    (microsoft.public.sqlserver.replication)