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 with a merge Replication and a pull Subscription on demand from
the client
I'am getting this message error from a vb.net Windows Application
DATE=2006-03-15 15:18:34
ERROR=SyncJMI.CDatabaseUtils.LoadDataTable failed.
System.Data.SqlClient.SqlException: General network error. Check your
network documentation.
at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior behavior)
at
System.Data.SqlClient.SqlCommand.System.Data.IDbCo mmand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillFromCommand(O bject data, Int32
startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable, IDbCommand
command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at SyncJMI.CDatabaseUtils.LoadDataTable(SqlCommand cmd, DataTable& dt,
Boolean verifyDb)
This is the first time a get this error
After doing some research on the Web, Ifind that if i put Polling=False in
my connection string this error dont appear anymore.
I'am not very confortable to deactivate the pooling for performance reason
Is this solution the real solution ?
Also by deactivating the pooling, does this deactivationis done on the
client side or server side?
It is a better idea to maximise the size of the pool instead of turn it off?
Thanks in advance!
I'm interested in any articles you can provide which show the connection
between General network error and connection pooling - haven't heard of this
as a solution myself before. Usually these issues concern breaks in
connectivity. If persistant then the network needs to be investigated. If
not, then simply restarting the merge agent suffices.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||My understanding is that connection pooling has advantages for other
connections using the same connection string properties, ie uid, pwd, or
trusted authentication. So the first connection in will spin up the min pool
size connections (default 1) and after it has complete its work subsequenct
connections with the same connection string can use that open connection.
What puzzles me is why are you using ado.net as opposed to the activex merge
replication objects? Its not clear to me that this is replication related or
ADO related. It seems to be barfing on LoadDataTable which doesn't sound
replication related.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"GC" <GC@.discussions.microsoft.com> wrote in message
news:93AF91D3-59F6-4F1A-8DB3-A91C38DEDD57@.microsoft.com...
> Hi,
> I'am working with a merge Replication and a pull Subscription on demand
> from
> the client
> I'am getting this message error from a vb.net Windows Application
> DATE=2006-03-15 15:18:34
> ERROR=SyncJMI.CDatabaseUtils.LoadDataTable failed.
> System.Data.SqlClient.SqlException: General network error. Check your
> network documentation.
> at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior
> cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior
> behavior)
> at
> System.Data.SqlClient.SqlCommand.System.Data.IDbCo mmand.ExecuteReader(CommandBehavior
> behavior)
> at System.Data.Common.DbDataAdapter.FillFromCommand(O bject data, Int32
> startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
> CommandBehavior behavior)
> at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable, IDbCommand
> command, CommandBehavior behavior)
> at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
> at SyncJMI.CDatabaseUtils.LoadDataTable(SqlCommand cmd, DataTable& dt,
> Boolean verifyDb)
>
> This is the first time a get this error
> After doing some research on the Web, Ifind that if i put Polling=False
> in
> my connection string this error dont appear anymore.
> I'am not very confortable to deactivate the pooling for performance reason
> Is this solution the real solution ?
> Also by deactivating the pooling, does this deactivationis done on the
> client side or server side?
> It is a better idea to maximise the size of the pool instead of turn it
> off?
> Thanks in advance!
>
>
>
>
>
|||Let me explain,
We use a vb.Net application that execute some script,copy files,update
version of my vb.net application and so on.
After all update are up to date I call the pull subscription that update all
the records in the database
My application is there for maintenance purpose and for synchronisation of
the database
So the General Network error could arrive during an the execution of a
script like a store procedure etc... that have nothing to do with the
replication.
Still have the problem with the pooling
We have develop many application for customer and it is the first time i got
this error.
Hope this help you
"Hilary Cotter" wrote:

> My understanding is that connection pooling has advantages for other
> connections using the same connection string properties, ie uid, pwd, or
> trusted authentication. So the first connection in will spin up the min pool
> size connections (default 1) and after it has complete its work subsequenct
> connections with the same connection string can use that open connection.
> What puzzles me is why are you using ado.net as opposed to the activex merge
> replication objects? Its not clear to me that this is replication related or
> ADO related. It seems to be barfing on LoadDataTable which doesn't sound
> replication related.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> 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
>
> "GC" <GC@.discussions.microsoft.com> wrote in message
> news:93AF91D3-59F6-4F1A-8DB3-A91C38DEDD57@.microsoft.com...
>
>
|||did you monitor your connection pooling objects? This will reveal what if
your pool is exhausted.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"GC" <GC@.discussions.microsoft.com> wrote in message
news:AE292989-2D5B-4A66-B8CF-EFD222B48808@.microsoft.com...[vbcol=seagreen]
> Let me explain,
> We use a vb.Net application that execute some script,copy files,update
> version of my vb.net application and so on.
> After all update are up to date I call the pull subscription that update
> all
> the records in the database
> My application is there for maintenance purpose and for synchronisation of
> the database
> So the General Network error could arrive during an the execution of a
> script like a store procedure etc... that have nothing to do with the
> replication.
> Still have the problem with the pooling
> We have develop many application for customer and it is the first time i
> got
> this error.
> Hope this help you
>
>
>
>
> "Hilary Cotter" wrote:

General network error

I used push merge replication over internet.
I got the this error log at end of applying both schema and data to the subscriber.
General network error. Check your network documentation.
(Source: internet_ip_address\MSDE1 (Data source); Error number: 11)
The data were repliacted to subscriber.
Then, I deleted the subscription and re-created again, but selected
"the Subscriber already has the schema and data".
I got the following error:
The remote server is not defined as a subscription server
(Source: internet_ip_address\MSDE1 (Data source); Error number: 14010)
on your publisher go to Tools-Replication-Configure Publishers,
Distributors, and Subscribers, click on the Subscriber tab, and locate your
subscriber and click on the three dots (the browse button) to the right of
the subscriber and ensure that you are using the impersonate the SQL Server
account on the publisher.
Then restart your distribution agent.
"Ming Cheng" <mccheng@.msn.com> wrote in message
news:B0FA6FEE-D918-49D3-AA1F-1EDBBB36AF8F@.microsoft.com...
> I used push merge replication over internet.
> I got the this error log at end of applying both schema and data to the
subscriber.
> General network error. Check your network documentation.
> (Source: internet_ip_address\MSDE1 (Data source); Error number: 11)
> The data were repliacted to subscriber.
> Then, I deleted the subscription and re-created again, but selected
> "the Subscriber already has the schema and data".
> I got the following error:
> The remote server is not defined as a subscription server
> (Source: internet_ip_address\MSDE1 (Data source); Error number: 14010)
>
sql

Future Maintenance of SQL 2005 Merge Replication

I have remote offices that are entering data into their local database, then
using merge replication to "upload" their changes to a publisher on my web
server, and then possibly download any changes made on my web server. My
Web server is running SQL 2005 Standard, and the local offices are running
SQL 2005 Express. I've got it working via https/replisapi.dll, and once
it's started, it works very nicely.
Typically when a new office once to get started, they'll backup their
(never-before-replicated) database to a .bak file, send me that file, and
I'll restore their (new) database onto my server, and create a publication.
Then I'll send them instructions on how to start a subscription. This
causes the data they just send me to come back down, as a snapshot is
applied to init the subscription. I realize that I could start a no-sync
initialization, but if any changes were made from when they made the backup
to when they start/init the subscripion, I believe the two-databases would
be out of sync. Am I right?
I understand that once a subscription is started, that if a backup is
restored (on either the subscription side or publisher side) that as long as
you're within the retention period, merge replication will correctly bring
over the changes that have occurred since the backup. With this in mind...
Would it be possible on the soon-to-be subscriber database to get the
replication triggers installed and working (tracking all changes) before the
backup is made, so that if any changes occur on the subscriber side (from
the time the backup was made to when it's applied to the publisher database
to when the subscription is started), these changes will be applied to the
publisher when the new subscription is initialized?
--Troy
Unfortunately you cannot enable change tracking before setting up the
subscription. So you would have to track the subscriber side changes
yourself while the subscription is being setup and update those rows that
changed in that interval so that it triggers a replication upload.
“This posting is provided "AS IS" with no warranties, and confers no rights.”
"Troy Wolbrink" wrote:

> I have remote offices that are entering data into their local database, then
> using merge replication to "upload" their changes to a publisher on my web
> server, and then possibly download any changes made on my web server. My
> Web server is running SQL 2005 Standard, and the local offices are running
> SQL 2005 Express. I've got it working via https/replisapi.dll, and once
> it's started, it works very nicely.
> Typically when a new office once to get started, they'll backup their
> (never-before-replicated) database to a .bak file, send me that file, and
> I'll restore their (new) database onto my server, and create a publication.
> Then I'll send them instructions on how to start a subscription. This
> causes the data they just send me to come back down, as a snapshot is
> applied to init the subscription. I realize that I could start a no-sync
> initialization, but if any changes were made from when they made the backup
> to when they start/init the subscripion, I believe the two-databases would
> be out of sync. Am I right?
> I understand that once a subscription is started, that if a backup is
> restored (on either the subscription side or publisher side) that as long as
> you're within the retention period, merge replication will correctly bring
> over the changes that have occurred since the backup. With this in mind...
> Would it be possible on the soon-to-be subscriber database to get the
> replication triggers installed and working (tracking all changes) before the
> backup is made, so that if any changes occur on the subscriber side (from
> the time the backup was made to when it's applied to the publisher database
> to when the subscription is started), these changes will be applied to the
> publisher when the new subscription is initialized?
> --Troy
>
>
|||Thanks for confirming that. I'm considering setting the database to
read-only during the interim to keep the user from making any changes that
will get discarded. Or atleast just give the user a warning that any
changes during the interim will be ignored.
--Troy
"Vijay TS" <VijayTS@.discussions.microsoft.com> wrote in message
news:FF785F35-E3BA-4966-953F-69B58A30F057@.microsoft.com...[vbcol=seagreen]
> Unfortunately you cannot enable change tracking before setting up the
> subscription. So you would have to track the subscriber side changes
> yourself while the subscription is being setup and update those rows that
> changed in that interval so that it triggers a replication upload.
> --
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."
>
> "Troy Wolbrink" wrote:

Function sequence error - Merge Replication

We are replicating from 7 publishers to 1 subscriber all running MS SQL
Server 2000 SP3 using Merge Replication.
We are in the process of upgrading our application and due to that we had to
make
some changes to the database schema like add some columns, create a few new
tables, and triggers. We did all this through a script using stored
procedures on 2 of the publisher databases and then ran the snapshot agent.
That's when we started seeing the error.
Error Message: The process could not bulk copy out of table '[dbo].[Invoice]'.
Error details: Function sequence error
(Source: ODBC SQL Server Driver (ODBC); Error number: 0)
------
Does anyone know how to resolve this?
Do we need to do anything on the subscriber database because of the schema
change done on the publisher database ?
Thanks in advance,
I wish I could tell you how to solve this one. The good news is that it
seems to be transient.
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
"Vikram" <Vikram@.discussions.microsoft.com> wrote in message
news:E1A11B74-CE85-4C1B-87F5-248919A882CE@.microsoft.com...
> We are replicating from 7 publishers to 1 subscriber all running MS SQL
> Server 2000 SP3 using Merge Replication.
> We are in the process of upgrading our application and due to that we had
to
> make
> some changes to the database schema like add some columns, create a few
new
> tables, and triggers. We did all this through a script using stored
> procedures on 2 of the publisher databases and then ran the snapshot
agent.
> That's when we started seeing the error.
> Error Message: The process could not bulk copy out of table
'[dbo].[Invoice]'.
> Error details: Function sequence error
> (Source: ODBC SQL Server Driver (ODBC); Error number: 0)
> ----
--
> Does anyone know how to resolve this?
> Do we need to do anything on the subscriber database because of the schema
> change done on the publisher database ?
>
> Thanks in advance,
>