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

general network error almost always means that the connection has been
broken - its a network failure problem not a problem with SQL Server or
replication.

--
Hilary Cotter
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

"Rob Kraft" <robkraft@xxxxxxx> wrote in message
news:%23Q6xWBJ7FHA.2012@xxxxxxxxxxxxxxxxxxxxxxx
>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

  • General network error. Check your network documentation
    ... I've a merge replication over a ISDN router between two ... SQL Server 2000 databases. ... General network error. ... (Source: MAILVXE (Data source); Error number: 11) ...
    (microsoft.public.sqlserver.replication)
  • Monitoring replication
    ... We're suffering from SQL replication issues - every now and again, ... replication dies, citing "General Network Error" as the cause. ... idea which performace counters to watch - there doesn't seem to be a handy ...
    (comp.databases.ms-sqlserver)
  • Monitoring Replication
    ... We're suffering from SQL replication issues - every now and again, ... replication dies, citing "General Network Error" as the cause. ... idea which performance counters to watch - there doesn't seem to be a handy ...
    (microsoft.public.sqlserver.replication)
  • Merge replication - Check network document
    ... I have an continuously merge replication across internet and VPN. ... The process could not check existence of generation at the 'Publisher'. ... General network error. ... Sometime the merge agent can overcome the error in next run, ...
    (microsoft.public.sqlserver.replication)
  • Re: Transactional replication from SQL Server 2005 to SQL Server 7 - how?
    ... SQL Server 7.0 from the SQL2005 management tools but I would encourage to ... primary keys are replicated as unique indexes if you ... configure replication using the SQL2000 Enterprise Manager. ... If you plan to reinitialize your SQL2000->SQL2005 subscription in the ...
    (microsoft.public.sqlserver.replication)