Re: General Network Error occurs Randomly

Tech-Archive recommends: Fix windows errors by optimizing your registry

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" <MarkC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5700CFA1-2C25-44FA-8AAF-AFC275017F69@xxxxxxxxxxxxxxxx
> 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" <MarkC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:E38683CF-EF55-4810-BA61-AFA73DC6FA3F@xxxxxxxxxxxxxxxx
>> > 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?
>>
>>
>>


.

Quantcast