General Network Error occurs Randomly

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

During the past 4-5 weeks, I've been experiencing General Network Errors
randomly.
I can go a day or two without any or I can receive up to 10 of them on a
single day.
The general error is:

Source: System.Web

Target Site: Boolean HandleError(System.Exception)

Message: Exception of type System.Web.HttpUnhandledException was thrown.

Inner exception Source: .Net SqlClient Data Provider

Inner exception Message: General network error. Check your network
documentation.

Stack trace:
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at WebClasses.Files.serveFile(String strCommands)
at D0410.Site.Tables.PotentialSites.view.serveFile(Object sender,
CommandEventArgs e)
at System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs e)
at
System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
at System.Web.UI.Page.ProcessRequestMain()


A bit of background:

1) IIS server running Windows 2003 Standard (no SP1)
2) SQL Server 2000 running Windows 20003 Standard (no SP1)


My connection string looks something like:

value="Network Library=DBMSSOCN;
Data Source=xxx.xxx.xxx.xxx;
Initial Catalog=Test;
Persist Security Info=True;
Pooling=True;
Min Pool Size=5;
Max Pool Size=75000;
Connection Reset=False;
Integrated Security=SSPI;";


After a user is validated, the connection string is modified by adding the
"Application Name" [I guess my question here is, is connection pooling turned
off by adding this piece?]

Here's some code which occasionally causes the error:

SqlConnection cnx = new SqlConnection(
System.Configuration.ConfigurationSettings.AppSettings["dbConnection"]+"Application Name="+strUsername+";" );
cnx.Open();
SqlCommand cmd = new SqlCommand("sp_insertAuditDocuments", cnx);
cmd.CommandType = CommandType.StoredProcedure;
SqlParameter prm;

prm = new SqlParameter("@strUsername",SqlDbType.VarChar,15);
prm.Direction = ParameterDirection.Input;
prm.Value = strUsername;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFilePath",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileDirectory;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFileName",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileName;
cmd.Parameters.Add(prm);

cmd.ExecuteNonQuery();
cnx.Close();


Any ideas?
 
General Network Errors are usually just that and not really a function of
your code. Stuff like a bad network card (or one going bad) or other
network related issues are usually the culprit.

Here are a few links though that may help you track it down:

http://support.microsoft.com/default.aspx?scid=kb;en-us;826829
http://codebetter.com/blogs/darrell.norton/archive/2004/03/04/8454.aspx

--
W.G. Ryan, MVP

www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
Mark C said:
During the past 4-5 weeks, I've been experiencing General Network Errors
randomly.
I can go a day or two without any or I can receive up to 10 of them on a
single day.
The general error is:

Source: System.Web

Target Site: Boolean HandleError(System.Exception)

Message: Exception of type System.Web.HttpUnhandledException was thrown.

Inner exception Source: .Net SqlClient Data Provider

Inner exception Message: General network error. Check your network
documentation.

Stack trace:
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at WebClasses.Files.serveFile(String strCommands)
at D0410.Site.Tables.PotentialSites.view.serveFile(Object sender,
CommandEventArgs e)
at System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs e)
at
System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
at System.Web.UI.Page.ProcessRequestMain()


A bit of background:

1) IIS server running Windows 2003 Standard (no SP1)
2) SQL Server 2000 running Windows 20003 Standard (no SP1)


My connection string looks something like:

value="Network Library=DBMSSOCN;
Data Source=xxx.xxx.xxx.xxx;
Initial Catalog=Test;
Persist Security Info=True;
Pooling=True;
Min Pool Size=5;
Max Pool Size=75000;
Connection Reset=False;
Integrated Security=SSPI;";


After a user is validated, the connection string is modified by adding the
"Application Name" [I guess my question here is, is connection pooling
turned
off by adding this piece?]

Here's some code which occasionally causes the error:

SqlConnection cnx = new SqlConnection(
System.Configuration.ConfigurationSettings.AppSettings["dbConnection"]+"Application
Name="+strUsername+";" );
cnx.Open();
SqlCommand cmd = new SqlCommand("sp_insertAuditDocuments", cnx);
cmd.CommandType = CommandType.StoredProcedure;
SqlParameter prm;

prm = new SqlParameter("@strUsername",SqlDbType.VarChar,15);
prm.Direction = ParameterDirection.Input;
prm.Value = strUsername;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFilePath",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileDirectory;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFileName",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileName;
cmd.Parameters.Add(prm);

cmd.ExecuteNonQuery();
cnx.Close();


Any ideas?
Click to expand...
 
Thanks for the response, W.G. Unfortunately, I don't think either of those
links help me [the traffic between the IIS box and SQL box is not encrypted].
I will try updating MDAC though.

The IIS box hosts 4 different websites, 3 done in classic ASP and one in
ASP.NET.
There is no problem with any of the classic ASP sites in communicating to
the SQL Server [can one get General Network Errors in classic ASP?]

I also have a test IIS and test SQL box which will exhibit the same behavior
randomly.

The strange thing is that a lot of the procs have the exact same code that
the ASP classic site calls and they've been bullet proof for 3 years.

Unfortunately, my live site is being impacted pretty heavily by these errors.
General Network Errors are usually just that and not really a function of
your code. Stuff like a bad network card (or one going bad) or other
network related issues are usually the culprit.

Here are a few links though that may help you track it down:

http://support.microsoft.com/default.aspx?scid=kb;en-us;826829
http://codebetter.com/blogs/darrell.norton/archive/2004/03/04/8454.aspx

--
W.G. Ryan, MVP

www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
Mark C said:
During the past 4-5 weeks, I've been experiencing General Network Errors
randomly.
I can go a day or two without any or I can receive up to 10 of them on a
single day.
The general error is:

Source: System.Web

Target Site: Boolean HandleError(System.Exception)

Message: Exception of type System.Web.HttpUnhandledException was thrown.

Inner exception Source: .Net SqlClient Data Provider

Inner exception Message: General network error. Check your network
documentation.

Stack trace:
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at WebClasses.Files.serveFile(String strCommands)
at D0410.Site.Tables.PotentialSites.view.serveFile(Object sender,
CommandEventArgs e)
at System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs e)
at
System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
at System.Web.UI.Page.ProcessRequestMain()


A bit of background:

1) IIS server running Windows 2003 Standard (no SP1)
2) SQL Server 2000 running Windows 20003 Standard (no SP1)


My connection string looks something like:

value="Network Library=DBMSSOCN;
Data Source=xxx.xxx.xxx.xxx;
Initial Catalog=Test;
Persist Security Info=True;
Pooling=True;
Min Pool Size=5;
Max Pool Size=75000;
Connection Reset=False;
Integrated Security=SSPI;";


After a user is validated, the connection string is modified by adding the
"Application Name" [I guess my question here is, is connection pooling
turned
off by adding this piece?]

Here's some code which occasionally causes the error:

SqlConnection cnx = new SqlConnection(
System.Configuration.ConfigurationSettings.AppSettings["dbConnection"]+"Application
Name="+strUsername+";" );
cnx.Open();
SqlCommand cmd = new SqlCommand("sp_insertAuditDocuments", cnx);
cmd.CommandType = CommandType.StoredProcedure;
SqlParameter prm;

prm = new SqlParameter("@strUsername",SqlDbType.VarChar,15);
prm.Direction = ParameterDirection.Input;
prm.Value = strUsername;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFilePath",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileDirectory;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFileName",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileName;
cmd.Parameters.Add(prm);

cmd.ExecuteNonQuery();
cnx.Close();


Any ideas?
Click to expand...
Click to expand...
 
I wonder if this might be caused by an Ethernet collapse? IIRC Martin says
that Ethernet is far more robust than most, but when it reaches saturation,
the protocol breaks down suddenly (it has a sharp performance knee). This
would be manifested by a "General Network Error". Ethernet collapse can be
caused by malfunctioning network hardware but also by too much traffic. Do
you have anyone downloading bulk data on a continuous basis? Listening to or
watching media over the wire? Microsoft campus had that problem when its
backbone was 10-based T.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
www.sqlreportingservices.net
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________


Mark C said:
Thanks for the response, W.G. Unfortunately, I don't think either of
those
links help me [the traffic between the IIS box and SQL box is not
encrypted].
I will try updating MDAC though.

The IIS box hosts 4 different websites, 3 done in classic ASP and one in
ASP.NET.
There is no problem with any of the classic ASP sites in communicating to
the SQL Server [can one get General Network Errors in classic ASP?]

I also have a test IIS and test SQL box which will exhibit the same
behavior
randomly.

The strange thing is that a lot of the procs have the exact same code that
the ASP classic site calls and they've been bullet proof for 3 years.

Unfortunately, my live site is being impacted pretty heavily by these
errors.
General Network Errors are usually just that and not really a function of
your code. Stuff like a bad network card (or one going bad) or other
network related issues are usually the culprit.

Here are a few links though that may help you track it down:

http://support.microsoft.com/default.aspx?scid=kb;en-us;826829
http://codebetter.com/blogs/darrell.norton/archive/2004/03/04/8454.aspx

--
W.G. Ryan, MVP

www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
Mark C said:
During the past 4-5 weeks, I've been experiencing General Network
Errors
randomly.
I can go a day or two without any or I can receive up to 10 of them on
a
single day.
The general error is:

Source: System.Web

Target Site: Boolean HandleError(System.Exception)

Message: Exception of type System.Web.HttpUnhandledException was
thrown.

Inner exception Source: .Net SqlClient Data Provider

Inner exception Message: General network error. Check your network
documentation.

Stack trace:
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at WebClasses.Files.serveFile(String strCommands)
at D0410.Site.Tables.PotentialSites.view.serveFile(Object sender,
CommandEventArgs e)
at System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs e)
at
System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection
postData)
at System.Web.UI.Page.ProcessRequestMain()


A bit of background:

1) IIS server running Windows 2003 Standard (no SP1)
2) SQL Server 2000 running Windows 20003 Standard (no SP1)


My connection string looks something like:

value="Network Library=DBMSSOCN;
Data Source=xxx.xxx.xxx.xxx;
Initial Catalog=Test;
Persist Security Info=True;
Pooling=True;
Min Pool Size=5;
Max Pool Size=75000;
Connection Reset=False;
Integrated Security=SSPI;";


After a user is validated, the connection string is modified by adding
the
"Application Name" [I guess my question here is, is connection pooling
turned
off by adding this piece?]

Here's some code which occasionally causes the error:

SqlConnection cnx = new SqlConnection(
System.Configuration.ConfigurationSettings.AppSettings["dbConnection"]+"Application
Name="+strUsername+";" );
cnx.Open();
SqlCommand cmd = new SqlCommand("sp_insertAuditDocuments", cnx);
cmd.CommandType = CommandType.StoredProcedure;
SqlParameter prm;

prm = new SqlParameter("@strUsername",SqlDbType.VarChar,15);
prm.Direction = ParameterDirection.Input;
prm.Value = strUsername;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFilePath",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileDirectory;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFileName",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileName;
cmd.Parameters.Add(prm);

cmd.ExecuteNonQuery();
cnx.Close();


Any ideas?
Click to expand...
Click to expand...
Click to expand...
 
Thanks for the response, Bill.

There isn't that much traffic being generated by my site (I'm at an academic
institution where we do medical research and collect data via the web: the
largest files we distribute are PDFs which may be at most 600k. On top of
that, at most, we may support 30 concurrent users.)

It's strange that I see this behavior happening randomly in both of my web
servers and only on the .NET sites. I could try using the other NICs that
are on board each server and see if that helps in anyway.

I'm one of those lucky guys who is the administrator, backup guy, security
guy, dba, programmer, etc of these 6 servers I have to maintain...


William (Bill) Vaughn said:
I wonder if this might be caused by an Ethernet collapse? IIRC Martin says
that Ethernet is far more robust than most, but when it reaches saturation,
the protocol breaks down suddenly (it has a sharp performance knee). This
would be manifested by a "General Network Error". Ethernet collapse can be
caused by malfunctioning network hardware but also by too much traffic. Do
you have anyone downloading bulk data on a continuous basis? Listening to or
watching media over the wire? Microsoft campus had that problem when its
backbone was 10-based T.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
www.sqlreportingservices.net
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________


Mark C said:
Thanks for the response, W.G. Unfortunately, I don't think either of
those
links help me [the traffic between the IIS box and SQL box is not
encrypted].
I will try updating MDAC though.

The IIS box hosts 4 different websites, 3 done in classic ASP and one in
ASP.NET.
There is no problem with any of the classic ASP sites in communicating to
the SQL Server [can one get General Network Errors in classic ASP?]

I also have a test IIS and test SQL box which will exhibit the same
behavior
randomly.

The strange thing is that a lot of the procs have the exact same code that
the ASP classic site calls and they've been bullet proof for 3 years.

Unfortunately, my live site is being impacted pretty heavily by these
errors.
General Network Errors are usually just that and not really a function of
your code. Stuff like a bad network card (or one going bad) or other
network related issues are usually the culprit.

Here are a few links though that may help you track it down:

http://support.microsoft.com/default.aspx?scid=kb;en-us;826829
http://codebetter.com/blogs/darrell.norton/archive/2004/03/04/8454.aspx

--
W.G. Ryan, MVP

www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
During the past 4-5 weeks, I've been experiencing General Network
Errors
randomly.
I can go a day or two without any or I can receive up to 10 of them on
a
single day.
The general error is:

Source: System.Web

Target Site: Boolean HandleError(System.Exception)

Message: Exception of type System.Web.HttpUnhandledException was
thrown.

Inner exception Source: .Net SqlClient Data Provider

Inner exception Message: General network error. Check your network
documentation.

Stack trace:
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at WebClasses.Files.serveFile(String strCommands)
at D0410.Site.Tables.PotentialSites.view.serveFile(Object sender,
CommandEventArgs e)
at System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs e)
at
System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection
postData)
at System.Web.UI.Page.ProcessRequestMain()


A bit of background:

1) IIS server running Windows 2003 Standard (no SP1)
2) SQL Server 2000 running Windows 20003 Standard (no SP1)


My connection string looks something like:

value="Network Library=DBMSSOCN;
Data Source=xxx.xxx.xxx.xxx;
Initial Catalog=Test;
Persist Security Info=True;
Pooling=True;
Min Pool Size=5;
Max Pool Size=75000;
Connection Reset=False;
Integrated Security=SSPI;";


After a user is validated, the connection string is modified by adding
the
"Application Name" [I guess my question here is, is connection pooling
turned
off by adding this piece?]

Here's some code which occasionally causes the error:

SqlConnection cnx = new SqlConnection(
System.Configuration.ConfigurationSettings.AppSettings["dbConnection"]+"Application
Name="+strUsername+";" );
cnx.Open();
SqlCommand cmd = new SqlCommand("sp_insertAuditDocuments", cnx);
cmd.CommandType = CommandType.StoredProcedure;
SqlParameter prm;

prm = new SqlParameter("@strUsername",SqlDbType.VarChar,15);
prm.Direction = ParameterDirection.Input;
prm.Value = strUsername;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFilePath",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileDirectory;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFileName",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileName;
cmd.Parameters.Add(prm);

cmd.ExecuteNonQuery();
cnx.Close();


Any ideas?
Click to expand...
Click to expand...
Click to expand...
 
We also saw this kind of failure when cars left the parking garage under the
MSU building. It seems that the car antennas were hitting the false ceiling
and the RG8 Ethernet cable was being bumped which disconnected the taps...
Virtually anything can disrupt the network so you might dig around in the
subfloor... ;)

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
www.sqlreportingservices.net
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________


Mark C said:
Thanks for the response, Bill.

There isn't that much traffic being generated by my site (I'm at an
academic
institution where we do medical research and collect data via the web: the
largest files we distribute are PDFs which may be at most 600k. On top of
that, at most, we may support 30 concurrent users.)

It's strange that I see this behavior happening randomly in both of my web
servers and only on the .NET sites. I could try using the other NICs that
are on board each server and see if that helps in anyway.

I'm one of those lucky guys who is the administrator, backup guy, security
guy, dba, programmer, etc of these 6 servers I have to maintain...


William (Bill) Vaughn said:
I wonder if this might be caused by an Ethernet collapse? IIRC Martin
says
that Ethernet is far more robust than most, but when it reaches
saturation,
the protocol breaks down suddenly (it has a sharp performance knee). This
would be manifested by a "General Network Error". Ethernet collapse can
be
caused by malfunctioning network hardware but also by too much traffic.
Do
you have anyone downloading bulk data on a continuous basis? Listening to
or
watching media over the wire? Microsoft campus had that problem when its
backbone was 10-based T.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
www.sqlreportingservices.net
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no
rights.
__________________________________


Mark C said:
Thanks for the response, W.G. Unfortunately, I don't think either of
those
links help me [the traffic between the IIS box and SQL box is not
encrypted].
I will try updating MDAC though.

The IIS box hosts 4 different websites, 3 done in classic ASP and one
in
ASP.NET.
There is no problem with any of the classic ASP sites in communicating
to
the SQL Server [can one get General Network Errors in classic ASP?]

I also have a test IIS and test SQL box which will exhibit the same
behavior
randomly.

The strange thing is that a lot of the procs have the exact same code
that
the ASP classic site calls and they've been bullet proof for 3 years.

Unfortunately, my live site is being impacted pretty heavily by these
errors.

General Network Errors are usually just that and not really a function
of
your code. Stuff like a bad network card (or one going bad) or other
network related issues are usually the culprit.

Here are a few links though that may help you track it down:

http://support.microsoft.com/default.aspx?scid=kb;en-us;826829
http://codebetter.com/blogs/darrell.norton/archive/2004/03/04/8454.aspx

--
W.G. Ryan, MVP

www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
During the past 4-5 weeks, I've been experiencing General Network
Errors
randomly.
I can go a day or two without any or I can receive up to 10 of them
on
a
single day.
The general error is:

Source: System.Web

Target Site: Boolean HandleError(System.Exception)

Message: Exception of type System.Web.HttpUnhandledException was
thrown.

Inner exception Source: .Net SqlClient Data Provider

Inner exception Message: General network error. Check your network
documentation.

Stack trace:
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at WebClasses.Files.serveFile(String strCommands)
at D0410.Site.Tables.PotentialSites.view.serveFile(Object sender,
CommandEventArgs e)
at System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs
e)
at
System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection
postData)
at System.Web.UI.Page.ProcessRequestMain()


A bit of background:

1) IIS server running Windows 2003 Standard (no SP1)
2) SQL Server 2000 running Windows 20003 Standard (no SP1)


My connection string looks something like:

value="Network Library=DBMSSOCN;
Data Source=xxx.xxx.xxx.xxx;
Initial Catalog=Test;
Persist Security Info=True;
Pooling=True;
Min Pool Size=5;
Max Pool Size=75000;
Connection Reset=False;
Integrated Security=SSPI;";


After a user is validated, the connection string is modified by
adding
the
"Application Name" [I guess my question here is, is connection
pooling
turned
off by adding this piece?]

Here's some code which occasionally causes the error:

SqlConnection cnx = new SqlConnection(
System.Configuration.ConfigurationSettings.AppSettings["dbConnection"]+"Application
Name="+strUsername+";" );
cnx.Open();
SqlCommand cmd = new SqlCommand("sp_insertAuditDocuments",
cnx);
cmd.CommandType = CommandType.StoredProcedure;
SqlParameter prm;

prm = new SqlParameter("@strUsername",SqlDbType.VarChar,15);
prm.Direction = ParameterDirection.Input;
prm.Value = strUsername;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFilePath",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileDirectory;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFileName",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileName;
cmd.Parameters.Add(prm);

cmd.ExecuteNonQuery();
cnx.Close();


Any ideas?
Click to expand...
Click to expand...
Click to expand...
 
Digging around in the subflooring should prove interesting, I'll need to
leave a trail of breadcrumbs to find my way back.

The thing that I don't get with this is the fact that it only happens on my
..NET app, my classic ASP pages experience absolutely no interruption -- they
have been running fine these past few weeks (and years for that matter).

William (Bill) Vaughn said:
We also saw this kind of failure when cars left the parking garage under the
MSU building. It seems that the car antennas were hitting the false ceiling
and the RG8 Ethernet cable was being bumped which disconnected the taps...
Virtually anything can disrupt the network so you might dig around in the
subfloor... ;)

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
www.sqlreportingservices.net
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________


Mark C said:
Thanks for the response, Bill.

There isn't that much traffic being generated by my site (I'm at an
academic
institution where we do medical research and collect data via the web: the
largest files we distribute are PDFs which may be at most 600k. On top of
that, at most, we may support 30 concurrent users.)

It's strange that I see this behavior happening randomly in both of my web
servers and only on the .NET sites. I could try using the other NICs that
are on board each server and see if that helps in anyway.

I'm one of those lucky guys who is the administrator, backup guy, security
guy, dba, programmer, etc of these 6 servers I have to maintain...


William (Bill) Vaughn said:
I wonder if this might be caused by an Ethernet collapse? IIRC Martin
says
that Ethernet is far more robust than most, but when it reaches
saturation,
the protocol breaks down suddenly (it has a sharp performance knee). This
would be manifested by a "General Network Error". Ethernet collapse can
be
caused by malfunctioning network hardware but also by too much traffic.
Do
you have anyone downloading bulk data on a continuous basis? Listening to
or
watching media over the wire? Microsoft campus had that problem when its
backbone was 10-based T.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
www.sqlreportingservices.net
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no
rights.
__________________________________


Thanks for the response, W.G. Unfortunately, I don't think either of
those
links help me [the traffic between the IIS box and SQL box is not
encrypted].
I will try updating MDAC though.

The IIS box hosts 4 different websites, 3 done in classic ASP and one
in
ASP.NET.
There is no problem with any of the classic ASP sites in communicating
to
the SQL Server [can one get General Network Errors in classic ASP?]

I also have a test IIS and test SQL box which will exhibit the same
behavior
randomly.

The strange thing is that a lot of the procs have the exact same code
that
the ASP classic site calls and they've been bullet proof for 3 years.

Unfortunately, my live site is being impacted pretty heavily by these
errors.

General Network Errors are usually just that and not really a function
of
your code. Stuff like a bad network card (or one going bad) or other
network related issues are usually the culprit.

Here are a few links though that may help you track it down:

http://support.microsoft.com/default.aspx?scid=kb;en-us;826829
http://codebetter.com/blogs/darrell.norton/archive/2004/03/04/8454.aspx

--
W.G. Ryan, MVP

www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
During the past 4-5 weeks, I've been experiencing General Network
Errors
randomly.
I can go a day or two without any or I can receive up to 10 of them
on
a
single day.
The general error is:

Source: System.Web

Target Site: Boolean HandleError(System.Exception)

Message: Exception of type System.Web.HttpUnhandledException was
thrown.

Inner exception Source: .Net SqlClient Data Provider

Inner exception Message: General network error. Check your network
documentation.

Stack trace:
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at WebClasses.Files.serveFile(String strCommands)
at D0410.Site.Tables.PotentialSites.view.serveFile(Object sender,
CommandEventArgs e)
at System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs
e)
at
System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection
postData)
at System.Web.UI.Page.ProcessRequestMain()


A bit of background:

1) IIS server running Windows 2003 Standard (no SP1)
2) SQL Server 2000 running Windows 20003 Standard (no SP1)


My connection string looks something like:

value="Network Library=DBMSSOCN;
Data Source=xxx.xxx.xxx.xxx;
Initial Catalog=Test;
Persist Security Info=True;
Pooling=True;
Min Pool Size=5;
Max Pool Size=75000;
Connection Reset=False;
Integrated Security=SSPI;";


After a user is validated, the connection string is modified by
adding
the
"Application Name" [I guess my question here is, is connection
pooling
turned
off by adding this piece?]

Here's some code which occasionally causes the error:

SqlConnection cnx = new SqlConnection(
System.Configuration.ConfigurationSettings.AppSettings["dbConnection"]+"Application
Name="+strUsername+";" );
cnx.Open();
SqlCommand cmd = new SqlCommand("sp_insertAuditDocuments",
cnx);
cmd.CommandType = CommandType.StoredProcedure;
SqlParameter prm;

prm = new SqlParameter("@strUsername",SqlDbType.VarChar,15);
prm.Direction = ParameterDirection.Input;
prm.Value = strUsername;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFilePath",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileDirectory;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFileName",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileName;
cmd.Parameters.Add(prm);

cmd.ExecuteNonQuery();
cnx.Close();


Any ideas?
Click to expand...
Click to expand...
Click to expand...
 
I didn't realize Porsche 911's and Ferrari's and Bentleys had antennas that
high ;-)

--
W.G. Ryan, MVP

www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
William (Bill) Vaughn said:
We also saw this kind of failure when cars left the parking garage under
the MSU building. It seems that the car antennas were hitting the false
ceiling and the RG8 Ethernet cable was being bumped which disconnected the
taps... Virtually anything can disrupt the network so you might dig around
in the subfloor... ;)

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
www.sqlreportingservices.net
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no
rights.
__________________________________


Mark C said:
Thanks for the response, Bill.

There isn't that much traffic being generated by my site (I'm at an
academic
institution where we do medical research and collect data via the web:
the
largest files we distribute are PDFs which may be at most 600k. On top
of
that, at most, we may support 30 concurrent users.)

It's strange that I see this behavior happening randomly in both of my
web
servers and only on the .NET sites. I could try using the other NICs
that
are on board each server and see if that helps in anyway.

I'm one of those lucky guys who is the administrator, backup guy,
security
guy, dba, programmer, etc of these 6 servers I have to maintain...


William (Bill) Vaughn said:
I wonder if this might be caused by an Ethernet collapse? IIRC Martin
says
that Ethernet is far more robust than most, but when it reaches
saturation,
the protocol breaks down suddenly (it has a sharp performance knee).
This
would be manifested by a "General Network Error". Ethernet collapse can
be
caused by malfunctioning network hardware but also by too much traffic.
Do
you have anyone downloading bulk data on a continuous basis? Listening
to or
watching media over the wire? Microsoft campus had that problem when its
backbone was 10-based T.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
www.sqlreportingservices.net
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no
rights.
__________________________________


Thanks for the response, W.G. Unfortunately, I don't think either of
those
links help me [the traffic between the IIS box and SQL box is not
encrypted].
I will try updating MDAC though.

The IIS box hosts 4 different websites, 3 done in classic ASP and one
in
ASP.NET.
There is no problem with any of the classic ASP sites in communicating
to
the SQL Server [can one get General Network Errors in classic ASP?]

I also have a test IIS and test SQL box which will exhibit the same
behavior
randomly.

The strange thing is that a lot of the procs have the exact same code
that
the ASP classic site calls and they've been bullet proof for 3 years.

Unfortunately, my live site is being impacted pretty heavily by these
errors.

General Network Errors are usually just that and not really a
function of
your code. Stuff like a bad network card (or one going bad) or other
network related issues are usually the culprit.

Here are a few links though that may help you track it down:

http://support.microsoft.com/default.aspx?scid=kb;en-us;826829
http://codebetter.com/blogs/darrell.norton/archive/2004/03/04/8454.aspx

--
W.G. Ryan, MVP

www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
During the past 4-5 weeks, I've been experiencing General Network
Errors
randomly.
I can go a day or two without any or I can receive up to 10 of them
on
a
single day.
The general error is:

Source: System.Web

Target Site: Boolean HandleError(System.Exception)

Message: Exception of type System.Web.HttpUnhandledException was
thrown.

Inner exception Source: .Net SqlClient Data Provider

Inner exception Message: General network error. Check your network
documentation.

Stack trace:
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at WebClasses.Files.serveFile(String strCommands)
at D0410.Site.Tables.PotentialSites.view.serveFile(Object sender,
CommandEventArgs e)
at
System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs e)
at
System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection
postData)
at System.Web.UI.Page.ProcessRequestMain()


A bit of background:

1) IIS server running Windows 2003 Standard (no SP1)
2) SQL Server 2000 running Windows 20003 Standard (no SP1)


My connection string looks something like:

value="Network Library=DBMSSOCN;
Data Source=xxx.xxx.xxx.xxx;
Initial Catalog=Test;
Persist Security Info=True;
Pooling=True;
Min Pool Size=5;
Max Pool Size=75000;
Connection Reset=False;
Integrated Security=SSPI;";


After a user is validated, the connection string is modified by
adding
the
"Application Name" [I guess my question here is, is connection
pooling
turned
off by adding this piece?]

Here's some code which occasionally causes the error:

SqlConnection cnx = new SqlConnection(
System.Configuration.ConfigurationSettings.AppSettings["dbConnection"]+"Application
Name="+strUsername+";" );
cnx.Open();
SqlCommand cmd = new SqlCommand("sp_insertAuditDocuments",
cnx);
cmd.CommandType = CommandType.StoredProcedure;
SqlParameter prm;

prm = new SqlParameter("@strUsername",SqlDbType.VarChar,15);
prm.Direction = ParameterDirection.Input;
prm.Value = strUsername;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFilePath",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileDirectory;
cmd.Parameters.Add(prm);

prm = new SqlParameter("@strFileName",SqlDbType.VarChar,300);
prm.Direction = ParameterDirection.Input;
prm.Value = strFileName;
cmd.Parameters.Add(prm);

cmd.ExecuteNonQuery();
cnx.Close();


Any ideas?
Click to expand...
Click to expand...
Click to expand...
 
Mark,

I remember me a failures like this. Nobody did believe the first.

There was a bulb in a room next to the computer room, that was not so good
anymore. It flashed sometimes, however it was a room that was seldom used.

We had three days the mainsystem down because there was investigation where
the failure came from. Than I replaced that bulb and the failure was gone.

Another one more recently, was when somebody had connected a "hub" to a
light switch of a central room. At the end of the day that "hub" went down
when the people using that room went home and people in an other room, who
where working in the evening had problems. In the morning the failure was of
course gone.

The last was of course a complete stupidity, however those happens as well.

Therefore it is searching for logic. I don't know if Bill was kidding,
however in my opinion can what he wrote be true.

Cor
 
While the Porsche antennas were too short to hit, the Bentley and Rolls
Royce antennas were tall enough. I was driving a Ford explorer with a CB
antenna at the time...
The light-switch story was great. I'll have to use that next time I give a
talk...

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
www.sqlreportingservices.net
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
 
Mark,

This is a .. umm .. kind of a "Catch All" error - which is bad I agree, but
much improved in .NET 2.0
(http://blogs.msdn.com/dataaccess/archive/2005/06.aspx).

The first issue I see is, you have an ultra huge connection pool size. I bet
if you can leave that to defaults, this error will occur much less
frequently.

What is your database config? Are you using a cluster? Do databases go up
and down frequently that cause this error?

- Sahil Malik [MVP]
Upcoming ADO.NET 2.0 book - http://tinyurl.com/9bync
----------------------------------------------------------------------------
---------------

Mark C said:
During the past 4-5 weeks, I've been experiencing General Network Errors
randomly.
I can go a day or two without any or I can receive up to 10 of them on a
single day.
The general error is:

Source: System.Web

Target Site: Boolean HandleError(System.Exception)

Message: Exception of type System.Web.HttpUnhandledException was thrown.

Inner exception Source: .Net SqlClient Data Provider

Inner exception Message: General network error. Check your network
documentation.

Stack trace:
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at WebClasses.Files.serveFile(String strCommands)
at D0410.Site.Tables.PotentialSites.view.serveFile(Object sender,
CommandEventArgs e)
at System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs e)
at
Click to expand...
System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.Rai
sePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
at System.Web.UI.Page.ProcessRequestMain()


A bit of background:

1) IIS server running Windows 2003 Standard (no SP1)
2) SQL Server 2000 running Windows 20003 Standard (no SP1)


My connection string looks something like:

value="Network Library=DBMSSOCN;
Data Source=xxx.xxx.xxx.xxx;
Initial Catalog=Test;
Persist Security Info=True;
Pooling=True;
Min Pool Size=5;
Max Pool Size=75000;
Connection Reset=False;
Integrated Security=SSPI;";


After a user is validated, the connection string is modified by adding the
"Application Name" [I guess my question here is, is connection pooling turned
off by adding this piece?]

Here's some code which occasionally causes the error:

SqlConnection cnx = new SqlConnection(
Click to expand...
System.Configuration.ConfigurationSettings.AppSettings["dbConnection"]+"Appl
ication Name="+strUsername+";" );
 
Back
Top