July 21, 2006 at 3:00 am
All,
Advice required. Recently we are having recurring DTS package failure due to a timeout issue this seems to run hand in hand with a dramatic increase in a backup job run time from approx. 9 mins to over an hour.
Within the error logs am receiving log entries as below:
2006-07-18 14:00:39 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2006-07-18 14:00:39 - ! [382] Logon to server '(local)' failed (JobManager)
Recorded for jobs on the local server
AND
[DBNETLIB][ConnectionOpen (PreLoginHandshake()).]
Run from a remote server.
This issue has occured previously and a restart of SQL resolved the issue and brought the backup time to normal. However on this occassion has not corrected it and would like a more permanent solution and a reason for the issue.
Many Thanks.
September 8, 2006 at 1:21 pm
We are experiening the same problem with serveral customers. They connect to SQL 2000 via ODBC and get the SQLState: S1T00 Timeout Expired error message. The errors occur ramdomly during both peek and non-peek times.
Does anyone know how ODBC uses Connection Pooling and if Connection Pooling with ODBC drivers could be the problem?
Switching to named pipes fixes the problem, a site with a couple hundred users touching all these workstations can be a problem....
Don Davidson
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply