William
Thu Oct 30 11:12:47 CST 2003
When SQL Server is restarted or in some cases the ISA server or a network
firewall, the "pointer" to the live connection stored in the connection pool
is made invalid. When the application tries to reference these "damaged"
connections, it throws an exception, but the pooling mechanism drops this
bad connection from the pool. However, this assumes that the application
(process) was running the whole time and the pool was being maintained.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
MVP, hRD
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Kevin Burton" <rkevinburton@charter.net> wrote in message
news:%23FA8DeqnDHA.684@TK2MSFTNGP09.phx.gbl...
> I am seeing it where there is no firewall and the "only" network component
> is the NIC's separating the machines. Would you mind elaborating on when
you
> see it when the server restarts? I am not seeing it when the server
restarts
> but there are some services involved when I install the application and
that
> is when I see it mostly, when I install the application (completely
replace
> one version with another).
>
> Kevin
>
> --
>
>
> ---------------------------------------------------------------------
> "Are you still wasting your time with spam?...
> There is a solution!"
>
> Protected by GIANT Company's Spam Inspector
> The most powerful anti-spam software available.
>
http://mail.spaminspector.com
>
>
> "William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message
> news:eKbGNnlnDHA.1960@TK2MSFTNGP12.phx.gbl...
> > When I see this error it sometimes means that the pooled connection is
> > damaged or not pointing to a valid connection on the server. This can
> occur
> > if the application corrupts the connection (rare) or the server restarts
> > (typically). I've also seen this when the hardware is intermittent or
when
> > the IT people restart a firewall or other network hardware component.
> >
> > hth
> >
> > --
> > ____________________________________
> > William (Bill) Vaughn
> > Author, Mentor, Consultant
> > MVP, hRD
> > www.betav.com
> > Please reply only to the newsgroup so that others can benefit.
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > __________________________________
> >
> > "Kevin Burton" <anonymous@discussions.microsoft.com> wrote in message
> > news:0df101c39e3f$8d061460$a601280a@phx.gbl...
> > > As an adendem to this message. I tried to get more
> > > information about the exception and I get:
> > >
> > > Class: 20
> > > Number: 11
> > > State: 0
> > > Server:
> > > Source: .Net SqlClient Data Provider
> > > Procedure: ConnectionRead (recv()).
> > > Message: General network error. Check your network
> > > documentation.
> > >
> > > Maybe this helps.
> > >
> > > Kevin
> > >
> > > >-----Original Message-----
> > > >I am getting the following SQL exception:
> > > >
> > > >Error: ReadSessionData: Error 1 - Type:
> > > >System.Data.SqlClient.SqlException
> > > >Source: .Net SqlClient Data Provider
> > > >Target Site: System.Data.SqlClient.SqlInternalConnection
> > > >GetConnection(Boolean ByRef)
> > > >Description: General network error. Check your network
> > > >documentation.
> > > >Stack Trace: at
> > > >System.Data.SqlClient.ConnectionPool.GetConnection
> > > >(Boolean& isInTransaction)
> > > > at
> > > >System.Data.SqlClient.SqlConnectionPoolManager.GetPooledCo
> > > n
> > > >nection(SqlConnectionString options, Boolean&
> > > >isInTransaction)
> > > > at System.Data.SqlClient.SqlConnection.Open()
> > > > at visa.dps.ppc.data.SessionInfoRequest.Execute()
> > > >
> > > >The root seems to be a General network error. Does anyone
> > > >know the cause? I can connect with the database with
> > > >Enterprise Manager and the database seems intact. I can't
> > > >figure out why I am getting this error. It seems to occur
> > > >the most when I install a new version of my application.
> > > >Once the application runs once without error it seems
> > > that
> > > >this error goes away. Any ideas?
> > > >
> > > >Thank you.
> > > >
> > > >Kevin
> > > >
> > > >.
> > > >
> >
> >
>
>