Posted by serge on 07/29/05 06:49

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

http://support.microsoft.com/default.aspx?scid=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_rCheckTreeForDelete object is blocking other
connections."

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

http://groups-beta.google.com/groups?q=System.Data.SqlClient.SqlException%3A+Timeout+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...

[Back to original message]