Re: SQL Server timeouts

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

From: Mingqing Cheng [MSFT] (v-mingqc_at_online.microsoft.com)
Date: 06/22/04 

Date: Tue, 22 Jun 2004 12:43:12 GMT

Hi Ben

Thanks for you prompt updates and sorry for my poor understanding.

I understood sometimes your asp pages will timeout with the error 80004005.
However, it is not often so that you could not reporduce this error as you
wanted, could you? I am afraid it's an ODBC issue instead of SQL Server:)
It's an common error in ODBC

First and formost, when there are many connections connected to the server
with asp, it's response time will be longer so that it may lead to such
timeout error. In this way, I strongly recommand you set timeout attribute
in connection object to be 60 instead of 30. Would you please have a try to
see whether it will have a better performance? Is this kind of timeout
happened when there are many connections to your server?

Secondly, would you please confirm that you have make the latest upgrates
for SQL Server and MDAC 2.8?

Thirdly, could you find the following information in your client
machine or server machine in system event log? If you could, it means there
is something wrong with authority in SQL Server.

Error num 80004005 (Native error : 17), error msg [Microsoft][ODBC SQL
Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

Last but not the least, If you think it's an issue internal SQL Server, I
would like to introduce your sp_who2 and sp_lock2, which could be found in
the following documents, to determine what is blocked

INF: sp_lock2 Returns Additional Locking Details

Thank you for your patience and cooperation. 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
Microsoft Developer Community Support
---------------------------------------------------------------
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!

Relevant Pages

  • Re: VB app connect THROUGH proxy to a remote SQL database
    ... The whole "HTTP proxy is way more secure than allowing outgoing ... the client app and the SQL server are on ... incoming connections to the SQL server are not the problem - it's ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... If I cut the maximum number of connections to for ... SQL Server simply blocks any further try to open another table until I close ... This doesn't happen with the SQL Server 2000 but with SQL Server ... No, I think ms-sql-s means that SQL 2000 is using port 1433, which is ...
    (microsoft.public.sqlserver.connect)
  • Re: timeout expired on View
    ... Hitchhiker’s Guide to Visual Studio and SQL Server ... timeout from 60 to 300. ... But it still not resolve the problem with MS SQL Server Management Studio. ... Where I can change that query timeout on that client ...
    (microsoft.public.sqlserver.tools)
  • Re: Problems all of a sudden
    ... The timeout period elapsed prior to completion of the ... operation or the server is not responding. ... Which version of SQL Server are the respetive servers? ... setting the database into a simple recovery may or may not be ...
    (microsoft.public.sqlserver.programming)
  • Re: Timeouts von SqlCommand vermeiden
    ... "Timeout ist abgelaufen. ... wenn der SQL Server die Abfrage in der gewählten ... Es ist vielmehr so, dass sich der SQL Server sich zu Tode warten wird, ... Kann man SqlCommand bzw. SqlConnection entsprechend konfigurieren? ...
    (microsoft.public.de.german.entwickler.dotnet.datenbank)