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 |
|
MirandaJ
Starting Member
35 Posts |
Posted - 2006-08-24 : 12:30:22
|
| We have a website which uses classic ASP with a SQL Server 2000 database. For some reason this morning pages that have had no problem, are now timing out. The lines it tells me it is timing out at is a line where we update a record in the database. The site has been running fine until today. Other sites which connect to different databases on the same SQL server are running fine. Everything on this one site has slowed to a crawl. Here is the error on one of the pages that is returnedMicrosoft OLE DB Provider for ODBC Drivers error '80040e31' [Microsoft][ODBC SQL Server Driver]Timeout expired /admin/results.asp, line 369 Any help will be appreciatedMiranda |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2006-08-24 : 13:56:27
|
| Maybe it is connected to the web server, not database server?How's DTC Service? RPC?Have you tried to restart the web server?Peter LarssonHelsingborg, Sweden |
 |
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2006-08-25 : 03:37:53
|
| Also check for Management -> Current Activity in Enterprise manager (or Activity Monitor in SSMS) for blocked SPIDS. You might have encountered deadlocks in your system...--Lumbago"Real programmers don't document, if it was hard to write it should be hard to understand" |
 |
|
|
afrika
Master Smack Fu Yak Hacker
2706 Posts |
Posted - 2006-08-25 : 05:24:35
|
| I would advice you change your database NAME in your connection string to read the internal server IPAlso check to see if all updates are installedAfrika |
 |
|
|
madhivanan
Premature Yak Congratulator
22864 Posts |
|
|
|
|
|