MSSQL Replication (Type Merge)

Hello, i have this 2 errors. Pleas for help.
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: SERWER (Data source); Error number: 11)
Access to internet is ok.
On Firewall all is allow.
Greeting Huryn Adrian.
You are having one of two issues.
1. Network connectivity
2. You are having blocking issues within the merge metadata tables which
means you are probably carrying around too much tracking information.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Adrian Huryn" <ahuryn@.ist.net.pl> wrote in message
news:20060210100829.af82c9a0.ahuryn@.ist.net.pl...
> Hello, i have this 2 errors. Pleas for help.
> 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: SERWER (Data source); Error number: 11)
> Access to internet is ok.
> On Firewall all is allow.
> Greeting Huryn Adrian.
|||On Fri, 10 Feb 2006 12:43:22 -0600
"Michael Hotek" <mike@.solidqualitylearning.com> wrote:

> You are having one of two issues.
> 1. Network connectivity
I have this check, pings/tracerouts are good. On bouth sites all work fine.

> 2. You are having blocking issues within the merge metadata tables which
> means you are probably carrying around too much tracking information.
What i can make here ?
Greeting, Huryn Adrian.
|||You need to validate that you get make a connect from your Subscriber to your
Publisher. If you can make a SQL connection then look at adjusting the
Subscriber Merge Agent Profile to a Slow Link Profile because this your
subscriber might have a slow connection and you need to lengthen the timeout
settings.
The blocking issues and/or large number of records in the merge replication
tables. I have used the following process successfully but I have one
replication which makes this process easier to implement.
Look up in BOL: sp_mergecleanupmetadata
"Adrian Huryn" wrote:

> On Fri, 10 Feb 2006 12:43:22 -0600
> "Michael Hotek" <mike@.solidqualitylearning.com> wrote:
> I have this check, pings/tracerouts are good. On bouth sites all work fine.
> What i can make here ?
> Greeting, Huryn Adrian.
>