Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
suhasckanade
Starting Member
8 Posts |
 Posted - 2008-07-18 : 08:05:18
|
| Hello Guys, We are experiencing following SQL error frequently on production server 2000 but we are unable to reproduce it on testing server. "Timeout expired. The timeout period elapsed prior tocompletion of the operation or the server is not responding."0 " .Net SQL Client Data Provider ConnectionRead (WrapperRead())."As there are no additional information in the Errors collection, we are stuck here what will be the probable reasons for occurrence of error. We have searched on net also but not found any satisfactory reasons. Pls help us by providing probable solutions to this problem.Thanks in advance. |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-18 : 08:12:09
|
| Is Services packs and patches applied to server is in top notch? |
 |
|
|
suhasckanade
Starting Member
8 Posts |
Posted - 2008-07-18 : 08:24:32
|
quote:
Originally posted by sodeep
Is Services packs and patches applied to server is in top notch?
Service Pack is 4dbnmpntw.dll version no -2000.80.194.0 |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
|
|
suhasckanade
Starting Member
8 Posts |
Posted - 2008-07-18 : 08:56:27
|
quote:
Originally posted by sodeep
Check this out:http://forums.asp.net/p/903456/992979.aspxor google out the error.
I al'ready search a lot on google but did'nt find the solution so far...... |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-19 : 00:02:44
|
| Did you see network problem between sql server and app machine? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-07-19 : 01:55:32
|
| To troubleshoot this error, you should be running SQL Profiler and Performance Monitor. You will see long durations in SQL Profiler if you are receiving timeouts. Look for anything over the timeout value set in the application, which is typically 30 seconds. Once you've located the code, see if you can make any improvements via indexes, rewriting the query, or redesigning the tables. Also look in Performance Monitor for hardware bottlenecks which might be slowing your queries down. I'd start with CPU and memory checks.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-07-19 : 01:57:25
|
| Also, do not just increase your timeout value to make the error go away. You should exhaust all possible avenues to make this more efficient before you decide to increase the value.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
|
|
|
Timeout expired Error