I've been working with Microsoft support for over 3 weeks now on an
intermittent General Network Error we're seeing in our production
environment between our ASP.NET application and SQL Server 2000. They are
continuing to work on the issue, but it seems as if our progress is grinding
to a halt. I asked this question on the newsgroups before going to MS but
figured I'd give it another shot now that I have more information.
The problem occurs intermittently (maybe 10 to 15 times per day). It seems
to be related to queries that return "large" amounts of data from SQL. The
problem started after we made an equipment change. We went from a single
server hosting both our ASP.NET application and SQL Server 2000, to one
server hosting IIS and another machine running SQL. An example of the
exception thrown appears at the bottom of this post.
MS had us perform 3 data captures initially: MPSRPT_MDAC on the IIS machine,
MPSRPT_MDAC on the SQL machine, and SQLDIAG on the database server. The MS
rep found nothing too out of the ordinary with our configuration, so he
asked me to do a network capture on both machines while the error occurred.
I was able to get a good capture in a small window and sent it off to MS.
The verdict is that IIS is basically halting the request. It is resetting
the database connection partway through retrieving the results of the stored
proc. IIS attempts to close the connection for some reason, SQL ignores and
keeps pumping back data, then IIS raises a reset. MS confirmed that there
is no packet loss. MS has not determined why this is happening and has not
advised me to capture any additional data.
If someone has any ideas, I am willing to provide as much detail as
possible. I wanted to keep this initial post as concise as possible.
Thanks for any assistance you can provide,
-joe
EXCEPTION:
System.Data.SqlClient.SqlException: General network error. Check your
network documentation.
at System.Data.SqlClient.SqlConnection.OnError(SqlExc eption exception,
TdsParserState state)
at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, TdsParserState state)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning()
at System.Data.SqlClient.TdsParser.ReadNetlib(Int32 bytesExpected)
at System.Data.SqlClient.TdsParser.ReadBuffer()
at System.Data.SqlClient.TdsParser.ReadByteArray(Byte[] buff, Int32
offset, Int32 len)
at System.Data.SqlClient.TdsParser.ReadEncodingChar(I nt32 length,
Encoding encoding)
at System.Data.SqlClient.TdsParser.ReadSqlValue(_SqlM etaData md, Int32
length)
at System.Data.SqlClient.TdsParser.ProcessRow(_SqlMet aData[] columns,
Object[] buffer, Int32[] map, Boolean useSQLTypes)
at System.Data.SqlClient.SqlDataReader.PrepareSQLReco rd(Int32 i)
at System.Data.SqlClient.SqlDataReader.GetSqlString(I nt32 i)
at System.Data.SqlClient.SqlDataReader.GetString(Int3 2 i)
7  1873 
Have you eliminated hardware or installed software issues by trying to run
this on a different pair of machines?
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Joe Ross" <jo********@hotmail.com> wrote in message
news:u5**************@TK2MSFTNGP12.phx.gbl... I've been working with Microsoft support for over 3 weeks now on an
intermittent General Network Error we're seeing in our production
environment between our ASP.NET application and SQL Server 2000. They are
continuing to work on the issue, but it seems as if our progress is
grinding to a halt. I asked this question on the newsgroups before going to MS but
figured I'd give it another shot now that I have more information.
The problem occurs intermittently (maybe 10 to 15 times per day). It
seems to be related to queries that return "large" amounts of data from SQL.
The problem started after we made an equipment change. We went from a single
server hosting both our ASP.NET application and SQL Server 2000, to one
server hosting IIS and another machine running SQL. An example of the
exception thrown appears at the bottom of this post.
MS had us perform 3 data captures initially: MPSRPT_MDAC on the IIS
machine, MPSRPT_MDAC on the SQL machine, and SQLDIAG on the database server. The
MS rep found nothing too out of the ordinary with our configuration, so he
asked me to do a network capture on both machines while the error
occurred.
I was able to get a good capture in a small window and sent it off to MS.
The verdict is that IIS is basically halting the request. It is resetting
the database connection partway through retrieving the results of the
stored proc. IIS attempts to close the connection for some reason, SQL ignores
and keeps pumping back data, then IIS raises a reset. MS confirmed that there
is no packet loss. MS has not determined why this is happening and has
not advised me to capture any additional data.
If someone has any ideas, I am willing to provide as much detail as
possible. I wanted to keep this initial post as concise as possible.
Thanks for any assistance you can provide,
-joe
EXCEPTION:
System.Data.SqlClient.SqlException: General network error. Check your
network documentation.
at System.Data.SqlClient.SqlConnection.OnError(SqlExc eption exception,
TdsParserState state)
at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, TdsParserState state)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning()
at System.Data.SqlClient.TdsParser.ReadNetlib(Int32 bytesExpected)
at System.Data.SqlClient.TdsParser.ReadBuffer()
at System.Data.SqlClient.TdsParser.ReadByteArray(Byte[] buff, Int32
offset, Int32 len)
at System.Data.SqlClient.TdsParser.ReadEncodingChar(I nt32 length,
Encoding encoding)
at System.Data.SqlClient.TdsParser.ReadSqlValue(_SqlM etaData md, Int32
length)
at System.Data.SqlClient.TdsParser.ProcessRow(_SqlMet aData[] columns,
Object[] buffer, Int32[] map, Boolean useSQLTypes)
at System.Data.SqlClient.SqlDataReader.PrepareSQLReco rd(Int32 i)
at System.Data.SqlClient.SqlDataReader.GetSqlString(I nt32 i)
at System.Data.SqlClient.SqlDataReader.GetString(Int3 2 i)
Unforunately, we're a small company and don't have the "luxury" of
duplicating the environment. However, there is plenty of horsepower there
to meet our needs. The web server is a Dell PowerEdge 1750 and the database
server is a Dell PowerEdge 2650 hooked into a PowerVault 220. Usage is
quite light.
I would love to be able to do what you say and I appreciate the value it
would bring to solving the problem, unfortunately, it's not realistic for us
at this time.
Thanks
-joe
"Kevin Spencer" <ke***@takempis.com> wrote in message
news:OV**************@tk2msftngp13.phx.gbl... Have you eliminated hardware or installed software issues by trying to run
this on a different pair of machines?
--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Joe Ross" <jo********@hotmail.com> wrote in message
news:u5**************@TK2MSFTNGP12.phx.gbl... I've been working with Microsoft support for over 3 weeks now on an
intermittent General Network Error we're seeing in our production
environment between our ASP.NET application and SQL Server 2000. They
are continuing to work on the issue, but it seems as if our progress is
grinding to a halt. I asked this question on the newsgroups before going to MS
but figured I'd give it another shot now that I have more information.
The problem occurs intermittently (maybe 10 to 15 times per day). It
seems to be related to queries that return "large" amounts of data from SQL.
The problem started after we made an equipment change. We went from a
single server hosting both our ASP.NET application and SQL Server 2000, to one
server hosting IIS and another machine running SQL. An example of the
exception thrown appears at the bottom of this post.
MS had us perform 3 data captures initially: MPSRPT_MDAC on the IIS
machine, MPSRPT_MDAC on the SQL machine, and SQLDIAG on the database server. The
MS rep found nothing too out of the ordinary with our configuration, so he
asked me to do a network capture on both machines while the error
occurred.
I was able to get a good capture in a small window and sent it off to
MS. The verdict is that IIS is basically halting the request. It is
resetting the database connection partway through retrieving the results of the
stored proc. IIS attempts to close the connection for some reason, SQL ignores
and keeps pumping back data, then IIS raises a reset. MS confirmed that
there is no packet loss. MS has not determined why this is happening and has
not advised me to capture any additional data.
If someone has any ideas, I am willing to provide as much detail as
possible. I wanted to keep this initial post as concise as possible.
Thanks for any assistance you can provide,
-joe
EXCEPTION:
System.Data.SqlClient.SqlException: General network error. Check your
network documentation.
at System.Data.SqlClient.SqlConnection.OnError(SqlExc eption
exception, TdsParserState state)
at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, TdsParserState state)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning()
at System.Data.SqlClient.TdsParser.ReadNetlib(Int32 bytesExpected)
at System.Data.SqlClient.TdsParser.ReadBuffer()
at System.Data.SqlClient.TdsParser.ReadByteArray(Byte[] buff, Int32
offset, Int32 len)
at System.Data.SqlClient.TdsParser.ReadEncodingChar(I nt32 length,
Encoding encoding)
at System.Data.SqlClient.TdsParser.ReadSqlValue(_SqlM etaData md,
Int32 length)
at System.Data.SqlClient.TdsParser.ProcessRow(_SqlMet aData[] columns,
Object[] buffer, Int32[] map, Boolean useSQLTypes)
at System.Data.SqlClient.SqlDataReader.PrepareSQLReco rd(Int32 i)
at System.Data.SqlClient.SqlDataReader.GetSqlString(I nt32 i)
at System.Data.SqlClient.SqlDataReader.GetString(Int3 2 i)
If it does turn out to be a hardware or installed software issue, I believe
you will have spent more than the cost of 2 machines in salaries trying to
find it.
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Joe Ross" <jo********@hotmail.com> wrote in message
news:O1**************@TK2MSFTNGP12.phx.gbl... Unforunately, we're a small company and don't have the "luxury" of
duplicating the environment. However, there is plenty of horsepower there
to meet our needs. The web server is a Dell PowerEdge 1750 and the
database server is a Dell PowerEdge 2650 hooked into a PowerVault 220. Usage is
quite light.
I would love to be able to do what you say and I appreciate the value it
would bring to solving the problem, unfortunately, it's not realistic for
us at this time.
Thanks
-joe
"Kevin Spencer" <ke***@takempis.com> wrote in message
news:OV**************@tk2msftngp13.phx.gbl... Have you eliminated hardware or installed software issues by trying to
run this on a different pair of machines?
--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Joe Ross" <jo********@hotmail.com> wrote in message
news:u5**************@TK2MSFTNGP12.phx.gbl... I've been working with Microsoft support for over 3 weeks now on an
intermittent General Network Error we're seeing in our production
environment between our ASP.NET application and SQL Server 2000. They are continuing to work on the issue, but it seems as if our progress is
grinding to a halt. I asked this question on the newsgroups before going to MS but figured I'd give it another shot now that I have more information.
The problem occurs intermittently (maybe 10 to 15 times per day). It
seems to be related to queries that return "large" amounts of data from SQL.
The problem started after we made an equipment change. We went from a single server hosting both our ASP.NET application and SQL Server 2000, to
one server hosting IIS and another machine running SQL. An example of the
exception thrown appears at the bottom of this post.
MS had us perform 3 data captures initially: MPSRPT_MDAC on the IIS
machine, MPSRPT_MDAC on the SQL machine, and SQLDIAG on the database server.
The MS rep found nothing too out of the ordinary with our configuration, so
he asked me to do a network capture on both machines while the error
occurred.
I was able to get a good capture in a small window and sent it off to MS. The verdict is that IIS is basically halting the request. It is resetting the database connection partway through retrieving the results of the
stored proc. IIS attempts to close the connection for some reason, SQL
ignores and keeps pumping back data, then IIS raises a reset. MS confirmed that there is no packet loss. MS has not determined why this is happening and
has not advised me to capture any additional data.
If someone has any ideas, I am willing to provide as much detail as
possible. I wanted to keep this initial post as concise as possible.
Thanks for any assistance you can provide,
-joe
EXCEPTION:
System.Data.SqlClient.SqlException: General network error. Check your
network documentation.
at System.Data.SqlClient.SqlConnection.OnError(SqlExc eption
exception, TdsParserState state)
at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, TdsParserState state)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning()
at System.Data.SqlClient.TdsParser.ReadNetlib(Int32 bytesExpected)
at System.Data.SqlClient.TdsParser.ReadBuffer()
at System.Data.SqlClient.TdsParser.ReadByteArray(Byte[] buff, Int32
offset, Int32 len)
at System.Data.SqlClient.TdsParser.ReadEncodingChar(I nt32 length,
Encoding encoding)
at System.Data.SqlClient.TdsParser.ReadSqlValue(_SqlM etaData md, Int32 length)
at System.Data.SqlClient.TdsParser.ProcessRow(_SqlMet aData[]
columns, Object[] buffer, Int32[] map, Boolean useSQLTypes)
at System.Data.SqlClient.SqlDataReader.PrepareSQLReco rd(Int32 i)
at System.Data.SqlClient.SqlDataReader.GetSqlString(I nt32 i)
at System.Data.SqlClient.SqlDataReader.GetString(Int3 2 i)
I respectfully disagree. Thank you for your overly helpful advice.
-joe
"Kevin Spencer" <ke***@takempis.com> wrote in message
news:uW**************@TK2MSFTNGP12.phx.gbl... If it does turn out to be a hardware or installed software issue, I
believe you will have spent more than the cost of 2 machines in salaries trying to
find it.
--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Joe Ross" <jo********@hotmail.com> wrote in message
news:O1**************@TK2MSFTNGP12.phx.gbl... Unforunately, we're a small company and don't have the "luxury" of
duplicating the environment. However, there is plenty of horsepower
there to meet our needs. The web server is a Dell PowerEdge 1750 and the database server is a Dell PowerEdge 2650 hooked into a PowerVault 220. Usage is
quite light.
I would love to be able to do what you say and I appreciate the value it
would bring to solving the problem, unfortunately, it's not realistic
for us at this time.
Thanks
-joe
"Kevin Spencer" <ke***@takempis.com> wrote in message
news:OV**************@tk2msftngp13.phx.gbl... Have you eliminated hardware or installed software issues by trying to
run this on a different pair of machines?
--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Joe Ross" <jo********@hotmail.com> wrote in message
news:u5**************@TK2MSFTNGP12.phx.gbl...
> I've been working with Microsoft support for over 3 weeks now on an
> intermittent General Network Error we're seeing in our production
> environment between our ASP.NET application and SQL Server 2000.
They are > continuing to work on the issue, but it seems as if our progress is
grinding
> to a halt. I asked this question on the newsgroups before going to
MS but > figured I'd give it another shot now that I have more information.
>
> The problem occurs intermittently (maybe 10 to 15 times per day).
It seems
> to be related to queries that return "large" amounts of data from
SQL. The
> problem started after we made an equipment change. We went from a
single > server hosting both our ASP.NET application and SQL Server 2000, to
one > server hosting IIS and another machine running SQL. An example of
the > exception thrown appears at the bottom of this post.
>
> MS had us perform 3 data captures initially: MPSRPT_MDAC on the IIS
machine,
> MPSRPT_MDAC on the SQL machine, and SQLDIAG on the database server. The MS
> rep found nothing too out of the ordinary with our configuration, so he > asked me to do a network capture on both machines while the error
occurred.
>
> I was able to get a good capture in a small window and sent it off
to MS. > The verdict is that IIS is basically halting the request. It is
resetting > the database connection partway through retrieving the results of
the stored
> proc. IIS attempts to close the connection for some reason, SQL
ignores and
> keeps pumping back data, then IIS raises a reset. MS confirmed that
there > is no packet loss. MS has not determined why this is happening and has not
> advised me to capture any additional data.
>
> If someone has any ideas, I am willing to provide as much detail as
> possible. I wanted to keep this initial post as concise as
possible. >
> Thanks for any assistance you can provide,
> -joe
>
> EXCEPTION:
> System.Data.SqlClient.SqlException: General network error. Check
your > network documentation.
> at System.Data.SqlClient.SqlConnection.OnError(SqlExc eption
exception, > TdsParserState state)
> at
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException > exception, TdsParserState state)
> at System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning()
> at System.Data.SqlClient.TdsParser.ReadNetlib(Int32
bytesExpected) > at System.Data.SqlClient.TdsParser.ReadBuffer()
> at System.Data.SqlClient.TdsParser.ReadByteArray(Byte[] buff,
Int32 > offset, Int32 len)
> at System.Data.SqlClient.TdsParser.ReadEncodingChar(I nt32 length,
> Encoding encoding)
> at System.Data.SqlClient.TdsParser.ReadSqlValue(_SqlM etaData md,
Int32 > length)
> at System.Data.SqlClient.TdsParser.ProcessRow(_SqlMet aData[] columns, > Object[] buffer, Int32[] map, Boolean useSQLTypes)
> at System.Data.SqlClient.SqlDataReader.PrepareSQLReco rd(Int32 i)
> at System.Data.SqlClient.SqlDataReader.GetSqlString(I nt32 i)
> at System.Data.SqlClient.SqlDataReader.GetString(Int3 2 i)
>
>
> I respectfully disagree. Thank you for your overly helpful advice.
You stated originally that you had already spent 3 weeks on this problem
without a resolution. I don't know what your salaries are like, but 3 weeks
is a lot of man-hours, and Microsoft support is expensive. Maybe you should
disagree later, when and if you get it fixed.
Thank you for your overly defensive reply.
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Joe Ross" <jo********@hotmail.com> wrote in message
news:Oa*************@TK2MSFTNGP10.phx.gbl... I respectfully disagree. Thank you for your overly helpful advice.
-joe
"Kevin Spencer" <ke***@takempis.com> wrote in message
news:uW**************@TK2MSFTNGP12.phx.gbl... If it does turn out to be a hardware or installed software issue, I believe you will have spent more than the cost of 2 machines in salaries trying
to find it.
--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Joe Ross" <jo********@hotmail.com> wrote in message
news:O1**************@TK2MSFTNGP12.phx.gbl... Unforunately, we're a small company and don't have the "luxury" of
duplicating the environment. However, there is plenty of horsepower there to meet our needs. The web server is a Dell PowerEdge 1750 and the
database server is a Dell PowerEdge 2650 hooked into a PowerVault 220. Usage
is quite light.
I would love to be able to do what you say and I appreciate the value
it would bring to solving the problem, unfortunately, it's not realistic for us at this time.
Thanks
-joe
"Kevin Spencer" <ke***@takempis.com> wrote in message
news:OV**************@tk2msftngp13.phx.gbl...
> Have you eliminated hardware or installed software issues by trying
to run > this on a different pair of machines?
>
> --
> HTH,
> Kevin Spencer
> .Net Developer
> Microsoft MVP
> Big things are made up
> of lots of little things.
>
> "Joe Ross" <jo********@hotmail.com> wrote in message
> news:u5**************@TK2MSFTNGP12.phx.gbl...
> > I've been working with Microsoft support for over 3 weeks now on
an > > intermittent General Network Error we're seeing in our production
> > environment between our ASP.NET application and SQL Server 2000.
They are
> > continuing to work on the issue, but it seems as if our progress
is > grinding
> > to a halt. I asked this question on the newsgroups before going
to MS but
> > figured I'd give it another shot now that I have more information.
> >
> > The problem occurs intermittently (maybe 10 to 15 times per day). It > seems
> > to be related to queries that return "large" amounts of data from SQL. > The
> > problem started after we made an equipment change. We went from a
single
> > server hosting both our ASP.NET application and SQL Server 2000,
to one > > server hosting IIS and another machine running SQL. An example of the > > exception thrown appears at the bottom of this post.
> >
> > MS had us perform 3 data captures initially: MPSRPT_MDAC on the
IIS > machine,
> > MPSRPT_MDAC on the SQL machine, and SQLDIAG on the database
server. The > MS
> > rep found nothing too out of the ordinary with our configuration,
so he > > asked me to do a network capture on both machines while the error
> occurred.
> >
> > I was able to get a good capture in a small window and sent it off to MS.
> > The verdict is that IIS is basically halting the request. It is
resetting
> > the database connection partway through retrieving the results of the > stored
> > proc. IIS attempts to close the connection for some reason, SQL
ignores > and
> > keeps pumping back data, then IIS raises a reset. MS confirmed
that there
> > is no packet loss. MS has not determined why this is happening
and has > not
> > advised me to capture any additional data.
> >
> > If someone has any ideas, I am willing to provide as much detail
as > > possible. I wanted to keep this initial post as concise as
possible. > >
> > Thanks for any assistance you can provide,
> > -joe
> >
> > EXCEPTION:
> > System.Data.SqlClient.SqlException: General network error. Check your > > network documentation.
> > at System.Data.SqlClient.SqlConnection.OnError(SqlExc eption
exception,
> > TdsParserState state)
> > at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException > > exception, TdsParserState state)
> > at System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning()
> > at System.Data.SqlClient.TdsParser.ReadNetlib(Int32 bytesExpected) > > at System.Data.SqlClient.TdsParser.ReadBuffer()
> > at System.Data.SqlClient.TdsParser.ReadByteArray(Byte[] buff, Int32 > > offset, Int32 len)
> > at System.Data.SqlClient.TdsParser.ReadEncodingChar(I nt32
length, > > Encoding encoding)
> > at System.Data.SqlClient.TdsParser.ReadSqlValue(_SqlM etaData
md, Int32
> > length)
> > at System.Data.SqlClient.TdsParser.ProcessRow(_SqlMet aData[]
columns, > > Object[] buffer, Int32[] map, Boolean useSQLTypes)
> > at System.Data.SqlClient.SqlDataReader.PrepareSQLReco rd(Int32
i) > > at System.Data.SqlClient.SqlDataReader.GetSqlString(I nt32 i)
> > at System.Data.SqlClient.SqlDataReader.GetString(Int3 2 i)
> >
> >
>
>
Joe -
At the risk of being 'overly' helpful, I would suggest that you may be
making too many assumptions about the operational data, for example the MS
assertion that no packets are being lost. The monitoring tools are not
infallible and they may in fact be wrong ( it even happened to me once long
ago ;-).
It sounds like MS is looking primarily at configuration data and not
performance data. Interaction under load between IIS and .NET may be
creating contention for resources or devices. If the queries are returning
'large' amounts of data, then the workload is not light, it's heavy and
there may well be a performance bottleneck in the server or network. It
could even be caused by a bad driver for a network device. Find every error
log and run every monitor on the system. There may be a lower level problem
within the apparent problem.
I'd also look very closely at application level performance, particularly
the heavy hitters, to see if you can reduce sudden bursts of demand. If the
heavy hitters are not critical, slow them down and spread out the demand.
If your delivery date is in extreme unction, you may even need to redesign
the queries to work around it.
In any case, I think you may need to fully instrument your server, collect
all the configuration and operation data available and do a more complete
analysis of your system. I've run across problems with complex interactions
in the past and a strictly analytic approach was the only way out.
For what it's worth ....
- Bill Breitmayer
"Joe Ross" <jo********@hotmail.com> wrote in message
news:Oa*************@TK2MSFTNGP10.phx.gbl... I respectfully disagree. Thank you for your overly helpful advice.
-joe
"Kevin Spencer" <ke***@takempis.com> wrote in message
news:uW**************@TK2MSFTNGP12.phx.gbl... If it does turn out to be a hardware or installed software issue, I believe you will have spent more than the cost of 2 machines in salaries trying
to find it.
--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Joe Ross" <jo********@hotmail.com> wrote in message
news:O1**************@TK2MSFTNGP12.phx.gbl... Unforunately, we're a small company and don't have the "luxury" of
duplicating the environment. However, there is plenty of horsepower there to meet our needs. The web server is a Dell PowerEdge 1750 and the
database server is a Dell PowerEdge 2650 hooked into a PowerVault 220. Usage
is quite light.
I would love to be able to do what you say and I appreciate the value
it would bring to solving the problem, unfortunately, it's not realistic for us at this time.
Thanks
-joe
"Kevin Spencer" <ke***@takempis.com> wrote in message
news:OV**************@tk2msftngp13.phx.gbl...
> Have you eliminated hardware or installed software issues by trying
to run > this on a different pair of machines?
>
> --
> HTH,
> Kevin Spencer
> .Net Developer
> Microsoft MVP
> Big things are made up
> of lots of little things.
>
> "Joe Ross" <jo********@hotmail.com> wrote in message
> news:u5**************@TK2MSFTNGP12.phx.gbl...
> > I've been working with Microsoft support for over 3 weeks now on
an > > intermittent General Network Error we're seeing in our production
> > environment between our ASP.NET application and SQL Server 2000.
They are
> > continuing to work on the issue, but it seems as if our progress
is > grinding
> > to a halt. I asked this question on the newsgroups before going
to MS but
> > figured I'd give it another shot now that I have more information.
> >
> > The problem occurs intermittently (maybe 10 to 15 times per day). It > seems
> > to be related to queries that return "large" amounts of data from SQL. > The
> > problem started after we made an equipment change. We went from a
single
> > server hosting both our ASP.NET application and SQL Server 2000,
to one > > server hosting IIS and another machine running SQL. An example of the > > exception thrown appears at the bottom of this post.
> >
> > MS had us perform 3 data captures initially: MPSRPT_MDAC on the
IIS > machine,
> > MPSRPT_MDAC on the SQL machine, and SQLDIAG on the database
server. The > MS
> > rep found nothing too out of the ordinary with our configuration,
so he > > asked me to do a network capture on both machines while the error
> occurred.
> >
> > I was able to get a good capture in a small window and sent it off to MS.
> > The verdict is that IIS is basically halting the request. It is
resetting
> > the database connection partway through retrieving the results of the > stored
> > proc. IIS attempts to close the connection for some reason, SQL
ignores > and
> > keeps pumping back data, then IIS raises a reset. MS confirmed
that there
> > is no packet loss. MS has not determined why this is happening
and has > not
> > advised me to capture any additional data.
> >
> > If someone has any ideas, I am willing to provide as much detail
as > > possible. I wanted to keep this initial post as concise as
possible. > >
> > Thanks for any assistance you can provide,
> > -joe
> >
> > EXCEPTION:
> > System.Data.SqlClient.SqlException: General network error. Check your > > network documentation.
> > at System.Data.SqlClient.SqlConnection.OnError(SqlExc eption
exception,
> > TdsParserState state)
> > at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException > > exception, TdsParserState state)
> > at System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning()
> > at System.Data.SqlClient.TdsParser.ReadNetlib(Int32 bytesExpected) > > at System.Data.SqlClient.TdsParser.ReadBuffer()
> > at System.Data.SqlClient.TdsParser.ReadByteArray(Byte[] buff, Int32 > > offset, Int32 len)
> > at System.Data.SqlClient.TdsParser.ReadEncodingChar(I nt32
length, > > Encoding encoding)
> > at System.Data.SqlClient.TdsParser.ReadSqlValue(_SqlM etaData
md, Int32
> > length)
> > at System.Data.SqlClient.TdsParser.ProcessRow(_SqlMet aData[]
columns, > > Object[] buffer, Int32[] map, Boolean useSQLTypes)
> > at System.Data.SqlClient.SqlDataReader.PrepareSQLReco rd(Int32
i) > > at System.Data.SqlClient.SqlDataReader.GetSqlString(I nt32 i)
> > at System.Data.SqlClient.SqlDataReader.GetString(Int3 2 i)
> >
> >
>
>
Bill-
I appreciate you taking the time to make such a detailed response. We are
going to take your advice and look at better instrumenting our application
to collect more meaningful data. We've realized that although we'll keep
working with MS on the issue, the solution will probably come from within.
I'll respond back to these groups when we make progress.
Thanks
-joe
"Bill Breitmayer" <bi************@worldnet.att.net> wrote in message
news:pM*********************@bgtnsc05-news.ops.worldnet.att.net... Joe -
At the risk of being 'overly' helpful, I would suggest that you may be
making too many assumptions about the operational data, for example the MS
assertion that no packets are being lost. The monitoring tools are not
infallible and they may in fact be wrong ( it even happened to me once
long ago ;-).
It sounds like MS is looking primarily at configuration data and not
performance data. Interaction under load between IIS and .NET may be
creating contention for resources or devices. If the queries are
returning 'large' amounts of data, then the workload is not light, it's heavy and
there may well be a performance bottleneck in the server or network. It
could even be caused by a bad driver for a network device. Find every
error log and run every monitor on the system. There may be a lower level
problem within the apparent problem.
I'd also look very closely at application level performance, particularly
the heavy hitters, to see if you can reduce sudden bursts of demand. If
the heavy hitters are not critical, slow them down and spread out the demand.
If your delivery date is in extreme unction, you may even need to redesign
the queries to work around it.
In any case, I think you may need to fully instrument your server, collect
all the configuration and operation data available and do a more complete
analysis of your system. I've run across problems with complex
interactions in the past and a strictly analytic approach was the only way out.
For what it's worth ....
- Bill Breitmayer
"Joe Ross" <jo********@hotmail.com> wrote in message
news:Oa*************@TK2MSFTNGP10.phx.gbl... I respectfully disagree. Thank you for your overly helpful advice.
-joe
"Kevin Spencer" <ke***@takempis.com> wrote in message
news:uW**************@TK2MSFTNGP12.phx.gbl... If it does turn out to be a hardware or installed software issue, I believe you will have spent more than the cost of 2 machines in salaries
trying to find it.
--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Joe Ross" <jo********@hotmail.com> wrote in message
news:O1**************@TK2MSFTNGP12.phx.gbl...
> Unforunately, we're a small company and don't have the "luxury" of
> duplicating the environment. However, there is plenty of horsepower there > to meet our needs. The web server is a Dell PowerEdge 1750 and the
database
> server is a Dell PowerEdge 2650 hooked into a PowerVault 220. Usage is > quite light.
>
> I would love to be able to do what you say and I appreciate the
value it > would bring to solving the problem, unfortunately, it's not
realistic for us
> at this time.
>
> Thanks
> -joe
>
>
> "Kevin Spencer" <ke***@takempis.com> wrote in message
> news:OV**************@tk2msftngp13.phx.gbl...
> > Have you eliminated hardware or installed software issues by
trying to run
> > this on a different pair of machines?
> >
> > --
> > HTH,
> > Kevin Spencer
> > .Net Developer
> > Microsoft MVP
> > Big things are made up
> > of lots of little things.
> >
> > "Joe Ross" <jo********@hotmail.com> wrote in message
> > news:u5**************@TK2MSFTNGP12.phx.gbl...
> > > I've been working with Microsoft support for over 3 weeks now on an > > > intermittent General Network Error we're seeing in our
production > > > environment between our ASP.NET application and SQL Server 2000. They > are
> > > continuing to work on the issue, but it seems as if our progress
is > > grinding
> > > to a halt. I asked this question on the newsgroups before going to MS > but
> > > figured I'd give it another shot now that I have more
information. > > >
> > > The problem occurs intermittently (maybe 10 to 15 times per
day). It > > seems
> > > to be related to queries that return "large" amounts of data
from SQL. > > The
> > > problem started after we made an equipment change. We went from
a > single
> > > server hosting both our ASP.NET application and SQL Server 2000,
to one
> > > server hosting IIS and another machine running SQL. An example
of the > > > exception thrown appears at the bottom of this post.
> > >
> > > MS had us perform 3 data captures initially: MPSRPT_MDAC on the IIS > > machine,
> > > MPSRPT_MDAC on the SQL machine, and SQLDIAG on the database server. The
> > MS
> > > rep found nothing too out of the ordinary with our
configuration, so he
> > > asked me to do a network capture on both machines while the
error > > occurred.
> > >
> > > I was able to get a good capture in a small window and sent it
off to > MS.
> > > The verdict is that IIS is basically halting the request. It is
> resetting
> > > the database connection partway through retrieving the results
of the > > stored
> > > proc. IIS attempts to close the connection for some reason, SQL
ignores
> > and
> > > keeps pumping back data, then IIS raises a reset. MS confirmed that > there
> > > is no packet loss. MS has not determined why this is happening and has
> > not
> > > advised me to capture any additional data.
> > >
> > > If someone has any ideas, I am willing to provide as much detail as > > > possible. I wanted to keep this initial post as concise as
possible. > > >
> > > Thanks for any assistance you can provide,
> > > -joe
> > >
> > > EXCEPTION:
> > > System.Data.SqlClient.SqlException: General network error.
Check your > > > network documentation.
> > > at System.Data.SqlClient.SqlConnection.OnError(SqlExc eption
> exception,
> > > TdsParserState state)
> > > at
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException > > > exception, TdsParserState state)
> > > at System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning()
> > > at System.Data.SqlClient.TdsParser.ReadNetlib(Int32
bytesExpected) > > > at System.Data.SqlClient.TdsParser.ReadBuffer()
> > > at System.Data.SqlClient.TdsParser.ReadByteArray(Byte[] buff,
Int32 > > > offset, Int32 len)
> > > at System.Data.SqlClient.TdsParser.ReadEncodingChar(I nt32
length, > > > Encoding encoding)
> > > at System.Data.SqlClient.TdsParser.ReadSqlValue(_SqlM etaData md, > Int32
> > > length)
> > > at System.Data.SqlClient.TdsParser.ProcessRow(_SqlMet aData[]
columns,
> > > Object[] buffer, Int32[] map, Boolean useSQLTypes)
> > > at System.Data.SqlClient.SqlDataReader.PrepareSQLReco rd(Int32 i) > > > at System.Data.SqlClient.SqlDataReader.GetSqlString(I nt32 i)
> > > at System.Data.SqlClient.SqlDataReader.GetString(Int3 2 i)
> > >
> > >
> >
> >
>
>
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: stanley j Mroczek |
last post by:
Every thing is on one machine, Programs and sql. Sql is up
and running(can test with query analyzer). No changes
where made! This was working fine. How do you track this
error? What network...
|
by: SteveS |
last post by:
Hello all. This problem is stumping me.... I run a page called
"default.aspx". For some reason when I execute this page, I get the error
below. It seems to run through the entire code behind...
|
by: stan |
last post by:
I have .net 2003 and SQL 2000 setup on one system. All I
have is one computer (no network). I am able to get to
the internet that works. I can run SQL Query Analyzer and
it works. The program was...
|
by: David Sworder |
last post by:
Hi there,
I am using the SQL managed provider in ADO.NET to fill a dataset with a large number of records. I periodically get an exception with the description "General Network Error" when trying...
|
by: galina betz |
last post by:
Please help!
Getting this error intermittently:
System.Data.SqlClient.SqlException: Timeout expired. The timeout period
elapsed prior to completion of the operation or the server is not...
|
by: Yong |
last post by:
I get a general network error when I try to make asynchronously call
ExecuteNonQuery on long sql statements that run in parallel.
Here is the background info on what I'm trying to accomplish:
I...
|
by: Yong |
last post by:
I'm not getting any reply to my previous thread so I'm stating a new one.
I get a General Network Error due to my SqlCommand object not having a big
enough CommandTimeout to complete very long...
|
by: johnkamal |
last post by:
Hi,
Some times while opening a page, I am getting the following error message, Please help me to rectify the problem.
Server Error in '/' Application.
General network error. Check your...
|
by: Naresh1 |
last post by:
What is WebLogic Admin Training?
WebLogic Admin Training is a specialized program designed to equip individuals with the skills and knowledge required to effectively administer and manage Oracle...
|
by: WisdomUfot |
last post by:
It's an interesting question you've got about how Gmail hides the HTTP referrer when a link in an email is clicked. While I don't have the specific technical details, Gmail likely implements measures...
|
by: Oralloy |
last post by:
Hello Folks,
I am trying to hook up a CPU which I designed using SystemC to I/O pins on an FPGA.
My problem (spelled failure) is with the synthesis of my design into a bitstream, not the C++...
|
by: Carina712 |
last post by:
Setting background colors for Excel documents can help to improve the visual appeal of the document and make it easier to read and understand. Background colors can be used to highlight important...
|
by: BLUEPANDA |
last post by:
At BluePanda Dev, we're passionate about building high-quality software and sharing our knowledge with the community. That's why we've created a SaaS starter kit that's not only easy to use but also...
|
by: Ricardo de Mila |
last post by:
Dear people, good afternoon...
I have a form in msAccess with lots of controls and a specific routine must be triggered if the mouse_down event happens in any control.
Than I need to discover what...
|
by: Johno34 |
last post by:
I have this click event on my form. It speaks to a Datasheet Subform
Private Sub Command260_Click()
Dim r As DAO.Recordset
Set r = Form_frmABCD.Form.RecordsetClone
r.MoveFirst
Do
If...
|
by: DizelArs |
last post by:
Hi all)
Faced with a problem, element.click() event doesn't work in Safari browser.
Tried various tricks like emulating touch event through a function:
let clickEvent = new Event('click', {...
|
by: F22F35 |
last post by:
I am a newbie to Access (most programming for that matter). I need help in creating an Access database that keeps the history of each user in a database. For example, a user might have lesson 1 sent...
| |
