General network error. Check your network documentation

From: Nuno Higgs (nunohiggs_at_hotmail.com)
Date: 09/07/04


Date: Tue, 7 Sep 2004 10:22:49 -0700

I've a merge replication over a ISDN router between two
SQL Server 2000 databases.
The job for synchronize always run at 0:00h every day.
Sometimes i'll get this errors messages:

The process could not make a generation at
the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error
number: -2147200994)
----------------------------------------------------------
General network error. Check your network documentation.
(Source: MAILVXE (Data source); Error number: 11)
----------------------------------------------------------
Communication link failure
(Source: MAILVXE (Data source); Error number: 0)
----------------------------------------------------------

The merge process could not perform retention-based meta
data cleanup in database 'WinSGS'.
(Source: Merge Replication Provider (Agent); Error
number: -2147199467)
----------------------------------------------------------
General network error. Check your network documentation.
(Source: MAILVXE (Data source); Error number: 11)
----------------------------------------------------------

I've already set the agent profile for a slow link
connection, can someone help qith this?



Relevant Pages

  • SA hungs on starting state (re post)
    ... Connecting to directory service on server osiris. ... The replication generated an error: ... A full synchronization is in progress ... Please restore the databases from a ...
    (microsoft.public.exchange2000.admin)
  • Re: Need Help with Error 37000
    ... This issue could occur if articles in the publication have the character ... Microsoft Online Partner Support ... |>> is one-way transactional replication environment. ... |>> I've just recently setup a number of databases for replication. ...
    (microsoft.public.sqlserver.replication)
  • Central Subscriber with updates to subscriber possible?
    ... I am trying to set up a central subscriber topology (seven small databases ... My biggest problem is that only merge replication seems to be able to handle ...
    (microsoft.public.sqlserver.replication)
  • Re: Restore
    ... sp_restartrepl or sp_resetrepl to let the replication continue even database ... > unless you can kick all of your users off both databases you can't. ... > restore it to the lab publisher and lab subscriber and re-run the ... My question is in which order I should backup databases to ...
    (microsoft.public.sqlserver.replication)
  • Re: Restore
    ... > unless you can kick all of your users off both databases you can't. ... > restore it to the lab publisher and lab subscriber and re-run the ... > Looking for a SQL Server replication book? ... My question is in which order I should backup databases to ...
    (microsoft.public.sqlserver.replication)