Hi all,
We have a web based database application that is getting asp 0113 script time out error. We are using this application for last 3 years without any problems. No change has been made neither hardware nor software so why all of a sudden we are getting this error? The only thing that has changed is number of users and data within application. But then we get time out error on weekends when not many users are using the application. So, the argument that we are getting error because many users are using it at the same time does not have much standing.
Good news is that we are able to find the root cause of the error. A stored procedure creates a process that blocks other processes. To solve our error, we simply kill the process and our application is back. But we are doing this for over a month now. We have changed the store procedure but we are still getting the error.
We tried re-organizing our database and shrinking database. Checks on database has proved that it's not corrupt. We have moved content from BIN into newly created BINBAK on web server. We have turned profiler on and turned IIS logging on, but still no luck.
We are out of ideas now. Your help in solving my error is greatly appreciated.
We are using SQL Server 2000.
Topic Options
Post Options
Thanks(0)
