Virtual SQL Server times out.

#1

Hi everyone,

We have a Windows 2003 Server NLB Cluster getting data from Windows 2003
Server SQL Cluster.
Occasionally we get Connection Timeout Errors when trying to connect to the
Virtual SQL Server.
After restarting SQL Server from Cluster Administrator it gets back to
normal.
I am not sure, but it is possible that it started after changing the
passwords for the Cluster Service,SQL Server Service and SQL Server Agent
Service.
Now we have restored the old passwords, but the problem is still there. We
changed the passwords according to the procedures specified by Microsoft.
Any assistance will be appreciated.

Best regards.

Sezgin Rafed

#2

Easy fix is to put a single retry into the connect. We looked into a
similar problem and it seems to be something in the connection pool, perhaps
a connection not closed correctly from a previous error. An automatic retry
in the connection code seemed to fix almost all of the issues.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

"news.microsoft.com" <anonymous (AT) anonymous (DOT) com> wrote

Quote:

Hi everyone,

We have a Windows 2003 Server NLB Cluster getting data from Windows 2003
Server SQL Cluster.
Occasionally we get Connection Timeout Errors when trying to connect to
the
Virtual SQL Server.
After restarting SQL Server from Cluster Administrator it gets back to
normal.
I am not sure, but it is possible that it started after changing the
passwords for the Cluster Service,SQL Server Service and SQL Server Agent
Service.
Now we have restored the old passwords, but the problem is still there. We
changed the passwords according to the procedures specified by Microsoft.
Any assistance will be appreciated.

Best regards.

Sezgin Rafed

#3

Hi Sezgin Rafed,

Thanks for your post.

First all, I would like to show my gratitude for MVP Geoff N. Hiten's
suggestions about checking your connection pool.

From your descriptions, I understood that when connecting your virtual SQL
Server, it will be randomly timeouts. Have I understood you? Correct me if
I was wrong.

As this is an issue that happens randomly, I would like to set your
expectation that we may spend extensive time to narrow it down since random
issues are always hard to troubleshoot.

For now, here are some questions to collect more information about this
issue
1. Does your SQL Server have a heavy workload and the resource of the
machine is relatively limited? Or does your network have a heavy workload?

2. What application do you used to connect the SQL Server? If you tried
using Query Analyzer connecting the Virtual SQL locally, will it timeout
again? If you are using your own application doing this, please follow MVP
Geoff N. Hiten's suggestions to see whether there is any idle connects in
the connection pool (You could use sp_who2 checking this)

3. You are connecting SQL Server by what? SQL Server IP address or Name
Pipes?

4. How often will this kind of timeout occurs? For example, how many
timeouts will happen in 100 connections?

5. Please paste your SQL Server Error Logs and Event Logs (if there is
anything related SQL Server) here for further troubleshooting.

Additionally, I would like to provide two more documents for your
reference.

How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/default...b;en-us;827422

Support WebCast: Microsoft SQL Server 2000: Troubleshooting Connectivity
http://support.microsoft.com/default...b;en-us;812817

Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!

Sincerely yours,

Mingqing Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

#4

Also, what is your general hardware layout and what SQL server build are you
running?

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

""Mingqing Cheng [MSFT]"" <v-mingqc (AT) online (DOT) microsoft.com> wrote

Quote:

Hi Sezgin Rafed,

Thanks for your post.

First all, I would like to show my gratitude for MVP Geoff N. Hiten's
suggestions about checking your connection pool.

From your descriptions, I understood that when connecting your virtual SQL
Server, it will be randomly timeouts. Have I understood you? Correct me if
I was wrong.

As this is an issue that happens randomly, I would like to set your
expectation that we may spend extensive time to narrow it down since
random
issues are always hard to troubleshoot.

For now, here are some questions to collect more information about this
issue
1. Does your SQL Server have a heavy workload and the resource of the
machine is relatively limited? Or does your network have a heavy workload?

2. What application do you used to connect the SQL Server? If you tried
using Query Analyzer connecting the Virtual SQL locally, will it timeout
again? If you are using your own application doing this, please follow MVP
Geoff N. Hiten's suggestions to see whether there is any idle connects in
the connection pool (You could use sp_who2 checking this)

3. You are connecting SQL Server by what? SQL Server IP address or Name
Pipes?

4. How often will this kind of timeout occurs? For example, how many
timeouts will happen in 100 connections?

5. Please paste your SQL Server Error Logs and Event Logs (if there is
anything related SQL Server) here for further troubleshooting.

Additionally, I would like to provide two more documents for your
reference.

How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/default...b;en-us;827422

Support WebCast: Microsoft SQL Server 2000: Troubleshooting Connectivity
http://support.microsoft.com/default...b;en-us;812817

Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!

Sincerely yours,

Mingqing Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

#5

Many thanks to Geoff and Mingqing for the assistance.

Question to Geoff: "Easy fix is to put a single retry into the connect" -
how do you do it ? Our programmers use VB.Net as far as I know.

Answers to your questions:

1. SQL Server runs on Compac Proliant DL380 G3(Dual Xeon 3.06 GHz,2 GB RAM).
It is a virtual server, running on Windows 2003 Server Enterprise Edition 2
Node Cluster. The databases are on SAN(HP EVA 5000). SQL Server build is
8.00.760

2. Few months ago we had the same setup and did not notice any problems. At
the time the Web Applications connecting to SQL Server were used actively(at
least 1 connection every 5 minutes). Now the project is back for redesign
and the Web Applications are used rarely (let's say few times a day).

3.Once a "Connection Timeout" occurs it is impossible to connect to SQL
Server before Restarting the SQL Server. It is
Success,Success,Success,Failure,Failure,Failure. It is not
Success,Success,Success,Failure,Failure,Success,Fa ilure.

4.At the moment our Servers and Network are under relatively light load.

5. It is possible to connect to the Virtual SQL Server with Query Analyser
from a Client machine after "Connection Timeout" errors start occuring(at
this point it is impossible to connect from our own application)

6. We are connecting to SQL Server using TCP/IP using it's virtual name.

7.There are no errors in the SQL Server or Event Logs.

Below are the error we get and the output of sp_who2 when "Connection
Timeouts" are occuring.

Best regards and thanks for the help again.

Sezgin Rafed

Server Error in '/' Application.
----------------------------------------------------------------------------
----

Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Timeout expired. The
timeout period elapsed prior to completion of the operation or the server is
not responding.

Source Error:

An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException: Timeout expired. The timeout period elapsed prior to
completion of the operation or the server is not responding.]
System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream) +723
System.Data.SqlClient.SqlCommand.ExecuteScalar() +177
BORMES.DatabaseConnection.ExecuteScalar(SqlConnect ion connection,
CommandType commandType, String commandText, SqlParameter[]
commandParameters) in C:\Projects\BORMES\BusinessLogic\Database
Interaction\DatabaseConnection.vb:1254
BORMES.DatabaseConnection.ExecuteScalar(String connectionString,
CommandType commandType, String commandText, SqlParameter[]
commandParameters) in C:\Projects\BORMES\BusinessLogic\Database
Interaction\DatabaseConnection.vb:1175
BORMES.DatabaseConnection.ExecuteScalar(String connectionString, String
spName, Object[] parameterValues) in
C:\Projects\BORMES\BusinessLogic\Database
Interaction\DatabaseConnection.vb:1206
BORMES.Navigation.MES_Session.StartSession() in
C:\Projects\BORMES\BusinessLogic\Authentication And
Navigation\Navigation\MES_Session.vb:67
BORMES.Navigation.MES_Session..ctor(User& Parent) in
C:\Projects\BORMES\BusinessLogic\Authentication And
Navigation\Navigation\MES_Session.vb:82
BORMES.Authentication.User.get_Session() in
C:\Projects\BORMES\BusinessLogic\Authentication And
Navigation\Authentication\User.vb:137
BORMES.Authentication.PageX.AddPage2History() in
C:\Projects\BORMES\BusinessLogic\Authentication And
Navigation\Authentication\PageX.vb:260
BORMES.Authentication.PageX.Page_Load(Object sender, EventArgs e) in
C:\Projects\BORMES\BusinessLogic\Authentication And
Navigation\Authentication\PageX.vb:31
System.EventHandler.Invoke(Object sender, EventArgs e) +0
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +731

----------------------------------------------------------------------------
----

Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
Version:1.1.4322.573

Output of sp_who2:

1 BACKGROUND sa . . NULL LAZY WRITER 0 0
10/13 09:35:18 1
2 RUNNABLE sa . . NULL LOG WRITER 16 0
10/13 09:35:18 2
3 BACKGROUND sa . . master SIGNAL HANDLER 0
0 10/13 09:35:18 3
4 BACKGROUND sa . . NULL LOCK MONITOR 0 0
10/13 09:35:18 4
5 BACKGROUND sa . . master TASK MANAGER 0
0 10/13 09:35:18 5
6 BACKGROUND sa . . master TASK MANAGER 0
124 10/13 09:35:18 6
7 BACKGROUND sa . . master TASK MANAGER 0
24 10/13 09:35:18 7
8 BACKGROUND sa . . master TASK MANAGER 0
0 10/13 09:35:18 8
9 sleeping sa . . NULL CHECKPOINT SLEEP 16
25 10/13 09:35:18 9
10 BACKGROUND sa . . master TASK MANAGER 0
0 10/13 09:35:18 10
11 BACKGROUND sa . . master TASK MANAGER 0
0 10/13 09:35:18 11
12 BACKGROUND sa . . master TASK MANAGER 0
0 10/13 09:35:18 12
13 BACKGROUND sa . . master TASK MANAGER 0
0 10/13 09:35:18 13
14 BACKGROUND sa . . master TASK MANAGER 0
0 10/13 09:35:18 14
15 BACKGROUND sa . . master TASK MANAGER 0
154 10/13 09:35:18 15
16 BACKGROUND sa . . master TASK MANAGER 0
118 10/13 09:35:18 16
51 sleeping BORMES\clsadmin BRCKMESSQL1 .
master AWAITING COMMAND 0 3 10/13 17:03:16 Microsoft® Windows® Operating
System 51
52 sleeping BORMES\clsadmin MESKEN . msdb
AWAITING COMMAND 31 19 10/13 09:35:19 SQLAgent - Generic Refresher
52
53 sleeping BORMES\clsadmin MESKEN . msdb
AWAITING COMMAND 79 5 10/13 17:03:40 SQLAgent - Alert Engine 53
54 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 0 1 10/13 15:39:45 54
55 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 32 0 10/13 16:43:57 55
56 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 30 3 10/13 12:14:04 56
57 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 0 1 10/13 16:39:56 57
58 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 16 0 10/13 16:49:01 58
59 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 0 2 10/13 16:47:14 59
60 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 0 0 10/13 16:26:19 60
61 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 0 1 10/13 16:39:05 61
62 RUNNABLE BORMES\srafed BRCKMESSQL1 . BORMES
SELECT INTO 63 7 10/13 17:03:47 SQL Query Analyzer 62
63 sleeping BORMES\srafed BRCKMESSQL1 . master
AWAITING COMMAND 0 2 10/13 17:02:18 SQL Query Analyzer - Object Browser 63

#6

For the retry, simply trap an immediate connection failure and try again.
We use an abstracted connection object that hides all the connection
security information and either returns a working connection or throws an
exception.

Are you seeing any Access Violations or other major erros in the SQL or
Application logs on the server or the client?

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

"Sezgin Rafed" <anonymous (AT) anonymous (DOT) com> wrote

Quote:

Many thanks to Geoff and Mingqing for the assistance.

Question to Geoff: "Easy fix is to put a single retry into the
onnect" -
how do you do it ? Our programmers use VB.Net as far as I know.

Answers to your questions:

1. SQL Server runs on Compac Proliant DL380 G3(Dual Xeon 3.06 GHz,2 GB
RAM).
It is a virtual server, running on Windows 2003 Server Enterprise Edition
2
Node Cluster. The databases are on SAN(HP EVA 5000). SQL Server build is
8.00.760

2. Few months ago we had the same setup and did not notice any problems.
At
the time the Web Applications connecting to SQL Server were used
actively(at
least 1 connection every 5 minutes). Now the project is back for redesign
and the Web Applications are used rarely (let's say few times a day).

3.Once a "Connection Timeout" occurs it is impossible to connect to SQL
Server before Restarting the SQL Server. It is
Success,Success,Success,Failure,Failure,Failure. It is not
Success,Success,Success,Failure,Failure,Success,Fa ilure.

4.At the moment our Servers and Network are under relatively light load.

5. It is possible to connect to the Virtual SQL Server with Query Analyser
from a Client machine after "Connection Timeout" errors start occuring(at
this point it is impossible to connect from our own application)

6. We are connecting to SQL Server using TCP/IP using it's virtual name.

7.There are no errors in the SQL Server or Event Logs.

Below are the error we get and the output of sp_who2 when "Connection
Timeouts" are occuring.

Best regards and thanks for the help again.

Sezgin Rafed

Server Error in '/' Application.
--------------------------------------------------------------------------
--
----

Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Timeout expired.
The
timeout period elapsed prior to completion of the operation or the server
is
not responding.

Source Error:

An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException: Timeout expired. The timeout period elapsed prior to
completion of the operation or the server is not responding.]
System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream) +723
System.Data.SqlClient.SqlCommand.ExecuteScalar() +177
BORMES.DatabaseConnection.ExecuteScalar(SqlConnect ion connection,
CommandType commandType, String commandText, SqlParameter[]
commandParameters) in C:\Projects\BORMES\BusinessLogic\Database
Interaction\DatabaseConnection.vb:1254
BORMES.DatabaseConnection.ExecuteScalar(String connectionString,
CommandType commandType, String commandText, SqlParameter[]
commandParameters) in C:\Projects\BORMES\BusinessLogic\Database
Interaction\DatabaseConnection.vb:1175
BORMES.DatabaseConnection.ExecuteScalar(String connectionString, String
spName, Object[] parameterValues) in
C:\Projects\BORMES\BusinessLogic\Database
Interaction\DatabaseConnection.vb:1206
BORMES.Navigation.MES_Session.StartSession() in
C:\Projects\BORMES\BusinessLogic\Authentication And
Navigation\Navigation\MES_Session.vb:67
BORMES.Navigation.MES_Session..ctor(User& Parent) in
C:\Projects\BORMES\BusinessLogic\Authentication And
Navigation\Navigation\MES_Session.vb:82
BORMES.Authentication.User.get_Session() in
C:\Projects\BORMES\BusinessLogic\Authentication And
Navigation\Authentication\User.vb:137
BORMES.Authentication.PageX.AddPage2History() in
C:\Projects\BORMES\BusinessLogic\Authentication And
Navigation\Authentication\PageX.vb:260
BORMES.Authentication.PageX.Page_Load(Object sender, EventArgs e) in
C:\Projects\BORMES\BusinessLogic\Authentication And
Navigation\Authentication\PageX.vb:31
System.EventHandler.Invoke(Object sender, EventArgs e) +0
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +731

--------------------------------------------------------------------------
--
----

Version Information: Microsoft .NET Framework Version:1.1.4322.573;
ASP.NET
Version:1.1.4322.573

Output of sp_who2:

1 BACKGROUND sa . . NULL LAZY WRITER 0
0
10/13 09:35:18 1
2 RUNNABLE sa . . NULL LOG WRITER 16
0
10/13 09:35:18 2
3 BACKGROUND sa . . master SIGNAL HANDLER
0
0 10/13 09:35:18 3
4 BACKGROUND sa . . NULL LOCK MONITOR 0
0
10/13 09:35:18 4
5 BACKGROUND sa . . master TASK MANAGER
0
0 10/13 09:35:18 5
6 BACKGROUND sa . . master TASK MANAGER
0
124 10/13 09:35:18 6
7 BACKGROUND sa . . master TASK MANAGER
0
24 10/13 09:35:18 7
8 BACKGROUND sa . . master TASK MANAGER
0
0 10/13 09:35:18 8
9 sleeping sa . . NULL CHECKPOINT SLEEP 16
25 10/13 09:35:18 9
10 BACKGROUND sa . . master TASK MANAGER
0
0 10/13 09:35:18 10
11 BACKGROUND sa . . master TASK MANAGER
0
0 10/13 09:35:18 11
12 BACKGROUND sa . . master TASK MANAGER
0
0 10/13 09:35:18 12
13 BACKGROUND sa . . master TASK MANAGER
0
0 10/13 09:35:18 13
14 BACKGROUND sa . . master TASK MANAGER
0
0 10/13 09:35:18 14
15 BACKGROUND sa . . master TASK MANAGER
0
154 10/13 09:35:18 15
16 BACKGROUND sa . . master TASK MANAGER
0
118 10/13 09:35:18 16
51 sleeping BORMES\clsadmin BRCKMESSQL1 .
master AWAITING COMMAND 0 3 10/13 17:03:16 Microsoft® Windows® Operating
System 51
52 sleeping BORMES\clsadmin MESKEN .
msdb
AWAITING COMMAND 31 19 10/13 09:35:19 SQLAgent - Generic Refresher
52
53 sleeping BORMES\clsadmin MESKEN .
msdb
AWAITING COMMAND 79 5 10/13 17:03:40 SQLAgent - Alert Engine
53
54 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 0 1 10/13 15:39:45 54
55 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 32 0 10/13 16:43:57 55
56 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 30 3 10/13 12:14:04 56
57 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 0 1 10/13 16:39:56 57
58 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 16 0 10/13 16:49:01 58
59 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 0 2 10/13 16:47:14 59
60 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 0 0 10/13 16:26:19 60
61 sleeping ip21dbuser . . BORMES AWAITING
COMMAND 0 1 10/13 16:39:05 61
62 RUNNABLE BORMES\srafed BRCKMESSQL1 .
BORMES
SELECT INTO 63 7 10/13 17:03:47 SQL Query Analyzer
62
63 sleeping BORMES\srafed BRCKMESSQL1 .
master
AWAITING COMMAND 0 2 10/13 17:02:18 SQL Query Analyzer - Object Browser
63

#7

Hi Sezgin Rafed,

Thanks for your detailed answer to my questions and explanation!
Thanks for MVP Geoff N. Hiten's prompt reply and suggestions!

As you said, when it is timeout for your Application, you could still
connect to SQL Server with Query Analyzer, I believe there is something
wrong within your application.

I have noticed the error to be "An unhandled exception occurred during the
execution of the current web request", it is an common error message for
ASP.NET and maybe there is something unreleased.

I think you could post this issue to vb.net newsgroup with some of your
application coding to see whether it could help.

Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!

Sincerely yours,

Mingqing Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

#8

Hi Sezgin,

I am currently standing by for an update from you and would like to know
how things are going there. Should you have any concerns on the recent
information I've posted, please don't hesitate to let me know directly and
I would love to help you on SQL Server side issues. It's my pleasure to be
of assistance

Sincerely yours,

Mingqing Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

#9

Thanks again to Geoff an Mingqing.

I would like to mention few more points. We constructed a separate ASP.NET
application and a ASP 3.0 page connecting to the same Virtual SQL Server. I
also put the complete problematic web site on a different Windows 2003
Server box. The situation is as follows:

Once the "Connection Timeout" Error occurs the code on the NLB Cluster and
the same code on the separate Windows 2003 Server box cannot connect to the
Virtual SQL Server. The ASP.NET application and the ASP 3.0 page connect
without a problem. Once the SQL Server is cycled Offline/Online all of them
can connect.

The Connection String used in the problematic code(with some string
variables in it) is:

CONNECTION_STRING = "data source=" & strDataSource_MES & ";Initial Catalog="
& strCatalog_MES & ";User
ID=businesslogic;Password=abc123ef;Trusted_connect ion=no;Persist Security
Info=True;Max Pool Size=500;Connection Lifetime=10;"

Best regards.

""Mingqing Cheng [MSFT]"" <v-mingqc (AT) online (DOT) microsoft.com> wrote

Quote:

Hi Sezgin,

I am currently standing by for an update from you and would like to know
how things are going there. Should you have any concerns on the recent
information I've posted, please don't hesitate to let me know directly and
I would love to help you on SQL Server side issues. It's my pleasure to be
of assistance

Sincerely yours,

Mingqing Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

#10

Hi Sezgin,

Once the "Connection Timeout" Error occurs, please use sp_who2 to check
whether there is any invisiable connection keep alive in the SQL Server
from problematic application. I guess there must be one.

Moreover, I will try to see whether it is possible to pick up an ASP.NET
Support Professional to give you some instructions on ASP.NET side

Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!

Sincerely yours,

Mingqing Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!