By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,584 Members | 1,774 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,584 IT Pros & Developers. It's quick & easy.

[165]ODBC Error 0 Timeout expired[SQLSTATE HYT00]

P: n/a
sql server 2000 8.00.194
Microsoft Windows 2000 Service Pack 2

I looked into my sqlserver agent log and found the following

ODBC Error 0 Timeout expired[SQLSTATE HYT00]
logon to server local '( failed)' (Job manager)

I have no idea what that means but it did keep out users for a minute or more.
The threads found on this forum almost all point to reccuring situations
mine is a sporadic one time issue.
Is it Ok to conclude it is a network error as I did?

TIA
Vince
Jul 20 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Vincento Harris (wu*****@yahoo.com) writes:
sql server 2000 8.00.194
That's an SQL Server with no service pack. I strongly encouarge you to
download and install Service Pack 3.
I looked into my sqlserver agent log and found the following

ODBC Error 0 Timeout expired[SQLSTATE HYT00]
logon to server local '( failed)' (Job manager)

I have no idea what that means but it did keep out users for a minute or
more. The threads found on this forum almost all point to reccuring
situations mine is a sporadic one time issue.
Is it Ok to conclude it is a network error as I did?


This may be a correct conclusion in the end, but it is not the most likely.

The ODBC error "Timeout expired" means that a query did not start to
return rows with the timeout period, which by default is 30 seconds.
The reason for this could be that the query itself needed longer time
to execute, because of large amounts of data to search and/or poor
indexing. It could also be that the query was blocked by another query,
and that query was long-running. In fact it does not have to be a query
as such that was blocking, but a process holding locks because of
an earlier abandoned query, which was not properly handled.

All this could have been started by some abnormal event like a
network glitch. However, it is much more likely that there was
some inappropriate SQL statement somewhere.
--
Erland Sommarskog, SQL Server MVP, so****@algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 20 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.