general network error

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
responding.
   at System.Data.SqlClient.SqlCommand. ExecuteReader(Comman
dBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()


After getting a fair number of these errors I get this one also:

System.Data.SqlClient.SqlException: General network error.  Check your
network documentation.
   at System.Data.SqlClient.SqlCommand. ExecuteReader(Comman
dBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()


SQL connection pooling is turned off. All sql parameters passed to the
stored procedure and all the data types are correct.










*** Sent via Developersdex http://www.droptable.com ***

Assuming that that there are no basic network connectivity issues,
there are several articles in the MS Knowledge Base about specific
errors or bugs which might produce that error message, so you should
also go through them to see if they might apply to your situation (eg.
827452, 826829 and others).

Simon

I checked all the articles i can find with no avail...

*** Sent via Developersdex http://www.droptable.com ***

Maybe it's the SQL statement that is timing out. In how many
seconds approximately do you get the timeout message?


> 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
> responding.
>    at System.Data.SqlClient.SqlCommand. ExecuteReader(Comman
dBehavior
> cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
>    at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
>
>
> After getting a fair number of these errors I get this one also:
>
> System.Data.SqlClient.SqlException: General network error.  Check your
> network documentation.
>    at System.Data.SqlClient.SqlCommand. ExecuteReader(Comman
dBehavior
> cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
>    at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
>
>
> SQL connection pooling is turned off. All sql parameters passed to the
> stored procedure and all the data types are correct.

It only happends a couple times a day, so it is intermittent error - it
is not timing out every time the sql is called. It can run for hours or
even days without a problem and then suddenly it starts getting these
timeouts...

*** Sent via Developersdex http://www.droptable.com ***

Like Simon pointed out, you should also search the MS KB.
A quick search lead me to this:

http://support.microsoft.com/defaul...kb;en-us;827393

I don't know what SQL statement is causing you this error but
I suggest what the KB article says, which is to check for any
Locks in SQL EM when you get the error.
You could also run the SQL Profiler the whole day and see
on which statement you are getting the Timeout error.
At least you might see a SQL Statement that is running for
a long period in the SQL Profiler.

"Additionally, when you view the current locks in SQL Server
Enterprise Manager (expand Management, expand Current
Activity, and then expand Locks/Process ID), you may find
that the  sps_rCheckTreeForDel
ete object is blocking other
connections."

There are a ton of posts on others experiencing the same error:

http://groups-beta.google.com/group... />
ut+expired

Maybe you could find some hints when you go through those
posts.

> It only happends a couple times a day, so it is intermittent error - it
> is not timing out every time the sql is called. It can run for hours or
> even days without a problem and then suddenly it starts getting these
> timeouts...

Guys, there is nothing on KB I did not read about this error and none of
the cases apply to me. As for the statement - I know exactly what stored
procedure it is timing out on and it is the same procedure that's
working just fine the rest of the time. I am really at the end of my
wits. I posted this question on several discussion groups via Google and
all. So far I did not get anything I did not think of before. I looked
at the locks, I did the profiling - I can't profile all day since it's a
production server, but I can get a 5 minutes or so when the errors are
going on and there is nothing - except that the duration of the request
goes way up and then times out after about 30000.... I see that lots of
people experiencing the same error (general network error)- there are
explanations to it though like the variable passed to the stored proc
are not the correct size or SSL encription, or connection timeout set to
zero - things like that. I am thinking about switching from the sql
server to something more robust...

*** Sent via Developersdex http://www.droptable.com ***

NotAGuru (notaguru@hotmail.com)  writes:
> Guys, there is nothing on KB I did not read about this error and none of
> the cases apply to me. As for the statement - I know exactly what stored
> procedure it is timing out on and it is the same procedure that's
> working just fine the rest of the time. I am really at the end of my
> wits. I posted this question on several discussion groups via Google and
> all. So far I did not get anything I did not think of before. I looked
> at the locks, I did the profiling - I can't profile all day since it's a
> production server, but I can get a 5 minutes or so when the errors are
> going on and there is nothing - except that the duration of the request
> goes way up and then times out after about 30000.... I see that lots of
> people experiencing the same error (general network error)- there are
> explanations to it though like the variable passed to the stored proc
> are not the correct size or SSL encription, or connection timeout set to
> zero - things like that. I am thinking about switching from the sql
> server to something more robust...

Have you checked the SQL Server error log?

"General Network Error" means that the connection with SQL Server
was severed in some unexpected way. This can be as simple as a dropped
network conection. But it also be due to a crash in the SQL Server process.
In this case, the SQL Server log will contain a stack dump.

From your description, it sounds that first you get these timeouts, and
then you get these network errors. It sounds as if SQL Server comes under
stress for some reason.

Could you post the output of "SELECT @@version"?

When this starts to happen, does it happen to all users that are
running this procedure? Do other processes also experience problems,
or is everything else working OK? What does this procedure do? Plain
SELECT? Updates? Access to linked servers? Would it be possible for you
to post the code?
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Could you post the output of "SELECT @@version"?

When this starts to happen, does it happen to all users that are
running this procedure?

The account it runs under is the only account that uses it,so i don't
really know, but i think it would error for all users.

Do other processes also experience problems,
or is everything else working OK?

Everything else is working, there are no errors in the event log on sql
server.

What does this procedure do? Plain
SELECT? Updates?

Updates


Access to linked servers? nope


Would it be possible for you
to post the code? no, it's production code but it is an update on the
database.


*** Sent via Developersdex http://www.droptable.com ***

NotAGuru (notaguru@hotmail.com)  writes: 

You couldn't?
 
>
> Everything else is working, there are no errors in the event log on sql
> server.

Note that I asked you to look for stack dumps in the SQL Server
error log. That is not the event log. The error log is in
C:\Program Files\Microsoft SQL  Server\MSSQL\Log\Err
ror. (Replace MSSQL
if on named instance.)
 
>
> no, it's production code but it is an update on the database.

OK. Since you don't share much information, I don't think we will
be able to help you here. I would suggest that you open a case with
Microsoft. That is likely to cost you some sum of money, but I would
assume that condition also costs you money when you tracking it down.
Having a support professional to look at it, could be more cost-
effective.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp