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 |
|
AlanS
Starting Member
28 Posts |
 Posted - 2005-05-11 : 10:41:49
|
| We have a VB 5 application with an SQL Server 2000 database back end. With increasing frequency, users can log in and view data, but when they try to do inserts or updates, they get the following error:Run-time error '-2147217871 (80440e31)': Timeout expiredThis happened several times last week, and every morning this week. We initially thought it might be related to task scheduling, since there was a task scheduler error in the logs last week, and so we disabled all the maintenance plans and are now running them manually - that seemed to resolve the problem the first time or two, but now it makes no difference. Now I'm seeing no errors in the logs, but every morning the same problem happens. The only way I can restore functionality is to reboot the server, and then wait - about 10 or 15 minutes after the server has finished rebooting, everything goes back to normal until the next morning. This morning, I got the timeout error when I tried to log in to the application during the 10-15 minute period.The application has not been changed in a long time, and we have not recently modified any of the server or database properties. The server runs a RAID-5 configuration with three disks, and there's plenty of free space on all the disks. Anyone have a clue about what might be causing this? Thanks. |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2005-05-11 : 11:33:10
|
| VB5? Wow :)Well, I think you need to analyze what's going on.Head over to http://www.sql-server-performance.com and find their article on performance monitoring.You'll need to monitor SQL Server User Connections, Average Disk Queue Lengths, etc.I suspect that if a reboot fixes the problem that you have an issue with connections not getting closed / cleaned up properly.Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
 |
|
|
|
|
|
|
|
Bizarre timeout errors