May 2, 2013 at 10:55 am
We have a web application manufactured by a company that no longer exists. I'm running the front end on a Windows 2003 server with IIS6. The database server is Windows 2003, SQL Server 2000. We do batch postings to AR daily. Smaller batch jobs post without a problem, within minutes. Larger ones however fail after just about 1 hour. (the application generates a message saying it failed). In the event log on the web server I get an entry each time this happens that reads:
Error:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
I have been reading about how to fix this, most information I find seems to point me to increasing the timeout period of the connection string. I also found a KB article referring to the .Net SP1 update that allows you to change this property. But I have no idea how to implement this change, or if that is really what I even need to be doing. I do not see this hotfix listed in my add/remove programs list. I do see .Net 2.0 and 3.0 SP2, and 3.5 SP1. But not .Net 1.1 SP1.
I do know that my Query timeout in SQL Server Properties is set to 0=Unlimited. But apparently that is not enough.
I also just configured the Maintenance Planner to run tonight to rebuild/re-index the database, on a suggestion from another article. But I don't know what results that will produce, if any.
Basically, I'm getting this timeout error and need to get it fixed and have no idea how to do it. Sorry for my lack of knowledge, but I just don't have to do this kind of thing enough to know it.
Any help would be appreciated. Thank you.
May 19, 2013 at 10:15 am
1) Check IIS pool is full or not if is make iis restart.
2) check CPu utilization on server
3) check all process on ssql server
4) check error log.
5) if required check suspended process then kill them.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply