General network error. Check your network documentation

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?
These errors are likely to be transitory. Schedule your job to run every 10
minutes or have the job loop back to step one on failuer.
See if this clears the problem.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Nuno Higgs" <nunohiggs@.hotmail.com> wrote in message
news:00a601c494ff$4c705ca0$a401280a@.phx.gbl...
> 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?
|||General Network Error often occurs when your CPU(s) are all pinned,
and the db won't accept any more connections.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:<#Dn7BgQlEHA.1476@.tk2msftngp13.phx.gbl>...[vbcol=seagreen]
> These errors are likely to be transitory. Schedule your job to run every 10
> minutes or have the job loop back to step one on failuer.
> See if this clears the problem.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Nuno Higgs" <nunohiggs@.hotmail.com> wrote in message
> news:00a601c494ff$4c705ca0$a401280a@.phx.gbl...
|||my experience is that you get the general network error when there is a
network problem. When the server is pegged I normally get timeout error
messages.
I could be wrong here, are you quite sure about this?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Douglas Tarr" <douglas.tarr@.gmail.com> wrote in message
news:c33eac8b.0409080834.686d0d43@.posting.google.c om...
> General Network Error often occurs when your CPU(s) are all pinned,
> and the db won't accept any more connections.
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:<#Dn7BgQlEHA.1476@.tk2msftngp13.phx.gbl>...[vbcol=seagreen]
10[vbcol=seagreen]
|||I often get both. It depends on "how pegged" the CPU is. If its at
99%, there's usually enough CPU to obtain new connections. The
timeouts happen when the query itself is run. However, if it is
totally pegged (to the point where i can't even access the box), i get
a general network error.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:<eSg3
$XtlEHA.2224@.tk2msftngp13.phx.gbl>...[vbcol=seagreen]
> my experience is that you get the general network error when there is a
> network problem. When the server is pegged I normally get timeout error
> messages.
> I could be wrong here, are you quite sure about this?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Douglas Tarr" <douglas.tarr@.gmail.com> wrote in message
> news:c33eac8b.0409080834.686d0d43@.posting.google.c om...
> news:<#Dn7BgQlEHA.1476@.tk2msftngp13.phx.gbl>...
> 10

General network error

Hi,
I am working on sql server 2000.
We have a job that runs every 30 mins every day. It has
been behaving very well. The only time it failed was
yesterday at 10:00am. When I viewed the job history, it
showed the following message:
Executed as user: blahblah\sql_admin. ConnectionRead (recv
()). [SQLSTATE 01000] (Message 10054) General network
error. Check your network documentation. [SQLSTATE 08S01]
(Error 11). The step failed.
General network error usually indicate that there is a
network connection failure. But this specific job/stored
procedure is not pulling data from any other server but
from local table. (Message 10054) indicating BCP overflow
certain column definition, but we are not doing BCP
either.
Could this message mean that there are too many disk I/O
going on at that time, and this job was waiting too long
in idle and failed?
Or could that be a logon info issue?
Any suggestion will be greatly appreciated.
JJHi JJ,
You might want to check SQL errorrlog and make sure that there is no error
occurred during that time.
Sincerely,
Yih-Yoon Lee [Microsoft]
Microsoft SQL Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Garbage in, Garbage out

Here are a few gems I just found in out JobTitle table, which stores contact
job titles in our database. If we have a job title, it's because it came in
a bulk-insert data file from a client.
The best
the big dawg
the boss
the man
The Master Himself
THE ONLY PERSON IN IT DEPARTMENT
The Simpsons
The Veritable Bugeater
ROFL!
Peace & happy computing,
Mike Labosh, MCSD
"When you kill a man, you're a murderer.
Kill many, and you're a conqueror.
Kill them all and you're a god." -- Dave Mustane"Mike Labosh" <mlabosh@.hotmail.com> wrote in message
news:emwFdG2zFHA.904@.tk2msftngp13.phx.gbl...
> The Veritable Bugeater
I'd like to hear the story behind this one.
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
--|||"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:e8znzZ2zFHA.664@.tk2msftngp13.phx.gbl...
> "Mike Labosh" <mlabosh@.hotmail.com> wrote in message
> news:emwFdG2zFHA.904@.tk2msftngp13.phx.gbl...
>
> I'd like to hear the story behind this one.
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.datamanipulation.net
> --
>
>
Probably not the real story, but anyway:
http://mynptv.org/sportsFeat/pionee..._lessplan1.html|||What a nightmare (it annoys me when I find data like this in a database.
Why the heck even have a column if you allow stuff like this, obviously more
annoyed by the original people to enter the data. I know if you get the
data there is probably an expectation that it is right (which is obviously
false :). I wonder if any ETL product would catch this sort of thing and
exception it out before it was entered into the database?
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
"Mike Labosh" <mlabosh@.hotmail.com> wrote in message
news:emwFdG2zFHA.904@.tk2msftngp13.phx.gbl...
> Here are a few gems I just found in out JobTitle table, which stores
> contact job titles in our database. If we have a job title, it's because
> it came in a bulk-insert data file from a client.
> The best
> the big dawg
> the boss
> the man
> The Master Himself
> THE ONLY PERSON IN IT DEPARTMENT
> The Simpsons
> The Veritable Bugeater
> ROFL!
> --
> Peace & happy computing,
> Mike Labosh, MCSD
> "When you kill a man, you're a murderer.
> Kill many, and you're a conqueror.
> Kill them all and you're a god." -- Dave Mustane
>|||> What a nightmare (it annoys me when I find data like this in a database.
> Why the heck even have a column if you allow stuff like this, obviously
> more annoyed by the original people to enter the data. I know if you get
> the data there is probably an expectation that it is right (which is
> obviously false :). I wonder if any ETL product would catch this sort of
> thing and exception it out before it was entered into the database?
heh.
If you worked here, you would hurt someone.
I could list snips from all the databases in the company that are all
similarly stupid. They don't want any automation, either: "Don't program
anything, we don't have the time. Just hurry up and copy/paste these 700
values into this Word template."
A homeless dude off the street could do this work. Why hire a guy that can
write code in 6 languages?!?
[bonking head on desk]
Anybody need a MCSD MCT? I'll be there in the morning!
Peace & happy computing,
Mike Labosh, MCSD
"When you kill a man, you're a murderer.
Kill many, and you're a conqueror.
Kill them all and you're a god." -- Dave Mustane|||Mike, I'll follow you :-)