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:

Future with SSIS

Hi,

We have a NT service built via Visual Basic 6 which fires dts processes on demand according some criteria. Well, on the whole and basically only for the following rule:

-dts process is executed when our service recognize a concrete plain file leaved in a folder. It’s generally generated for a mainframe JCL along with a activator file (.nul file, empty). Each application own a folder and each folder have lots of files as the aforementioned ones. Scheduler for that is an ASP application that lives within a intranet. It also is a monitor and logger

In that schema, keeping on mind that eight out of ten are ETL processes, critical ones and on daily-basis, our question is, how to handle on with this stuff using by sql25k and its powerful SSIS? Migrating such dts packages to SSIS packages is a piece of cake (now no before; thanks Jamie, Michael and other guys for your awesome help) because of its tipology. However our main concern is what the hell to use. Centralized dtsx package running all day long as a service, listening and checking for files? .Net windows application either vb or c#? aspx solution? Set of .vbs interlinked among them?

This is a old post/goal. In spite of we have not defined any deadline for that, what the heck as time goes by is more urgent for us. A restriction: we can’t to programme nothing from our sql25k production cluster physically. Any stuff will be done on workstations.

In terms of cost, no problem at all. We are interested in hear thoughts and point of view about which is the most effective way

Thanks in advance,

I don't like packages running all day, listening for events. The architecture was not designed for that, and we have not tested packages as long running listeners.

I would suggest using SQL Server Agent, with alerts, listening for WMI messages about files arriving. See: http://msdn2.microsoft.com/en-us/library/ms191508.aspx

The alerts can execute SSIS packages using the SQL Agent SSIS subsystem.

Donald

|||Thanks a lot for your answer Donald.sql