IIS 5 & IIS 6
Last post Jun 27, 2013 09:41 AM by mvolo
Apr 19, 2009 10:01 PM|ankit.g|LINK
We are using IIS 6.0 on the MS 2003 server SP2. Application uses oracle database and the client version installed on the server is Oracle 10.2.0.4.
We are experience a performance issue where the site randomly hangs and we are not even able to take the server remotely to debug the issue. We installed the DebugDiag tool to find the root cause. Please find below the log from the DebugDiag.
Request your help in resolving the issue
Apr 20, 2009 10:17 AM|ma_khan|LINK
We are experience a performance issue where the site randomly hangs and we are not even able to take the server remotely to debug the issue.
You are not able to take control remotely by that we can say it is the server that is hanging rather than just the site. Next, by the analysis report that you have given ...a lot of it hints at oracore10.dll
Did you check that ?
Seems like your threads are in wait state as they are unable to run queries....
Apr 20, 2009 11:26 PM|ankit.g|LINK
Thanks ma_khan for your quick help. Actually I am not sure how to troubleshoot the oracore10.dll. Is it the problem with the oracle client on the server? Because when we execute the same queries from PL/SQL we get the results in less than 0.04 seconds.
It will be really great if you can please let me know how the issue related to oracore10.dll can be tackled.
All the valuble inputs are well appreciated.
Apr 21, 2009 10:52 AM|ma_khan|LINK
Are these pages DB intensive... I mean are you trying to get large amount of data ... Also you might want to check if there is good connectivity between the IIS server and the DB Server ...
That is all I can tell with the data we have ? is your oracle client patched...
Jun 27, 2013 09:41 AM|mvolo|LINK
Is this an ASP.NET application? Usually hangs happen due to request threads blocking on database or network calls, and exhausting available threads in the threadpool. If you can catch the hang live, you should be able to snapshot the thread stacks in the
worker process to identify where they are hanging. Past that, you'd have to use the debugger and do some analysis.
DebugDiag mostly focuses on synchronization deadlocks, which we see rarely these days.
We also recently added automatic hang troubleshooting to LeanSentry, see
The holy grail: Automatically diagnose IIS and ASP.NET website hangs. This will diagnose most of the common hang causes for IIS/ASP.NET applications.