Timeouts can be caused by several different things. When the problem occurs, connect to the SQL Server with Enterprise Manager and
look at the Management folder/Current Activity. It is possible that something else has an exclusive lock on the resource you're trying to
access and the lock isn't released before your query times out.
If the problem occurs when connecting to SQL Server, it's a login timeout. Login timeouts can be caused by network issues. If you use
Windows NT authentication to connect to SQL Server, the account has to be validated by a domain controller before SQL will let you
connect. Problems connecting to the domain controller can affect your SQL connectivity.
Shirley Kelly, MCSE, MCDBA
SQL Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
I connect to a MS SQL Server 2000 with SqlConnection (ADO.NET & C#) with
this connection string.
Server=SUN; Database=master; User ID=sa; Password=test; Connect
And Submit these statements.
1- ALTER DATABASE [MyDB] SET SINGLE_USER WITH ROLLBACK IMMEDIATE
2- RESTORE DATABASE [MyDB] FROM DISK='c:\backup\mydb.bak' WITH RECOVERY
3- ALTER DATABASE [MyDB] SET MULTI_USER
I get this error message.
Timeout expired. the timeout period elapsed prior to completion of the
operation or the server is not responding.
And database set to "Loading" state and can not connect to it.
After this, When I restore Database with SQL Server Enterprise Manager ,All
Why I get this error with ADO.NET.
13. Timeout Errors