IIS 7 and Above
Intermittent Site Hang (ASP Request Execution Time)
Last post Feb 12, 2018 07:55 AM by Yuk Ding
Feb 09, 2018 12:01 PM|WideEyedFox|LINK
We have a third party application running which has its own 2012 R2 IIS server (2x 2.29Ghz, 8Gb, VM within VMWare environment) and also uses our 2014 SQL Server. The issue started on 22 January and prior to that the site has worked fine for 4 years.
For the last 3 weeks, seemingly intermittently the web application has become unresponsive for anything from 20 seconds to 20 minutes, however CPU/Memory/Disk access is fine. Performance Monitor shows a big spike in Active Server Pages "Requests
Queued" and "Requests Executing" over the same time period. Other counters (Drive, Network, plus the SQL server access) all look normal and do not spike.
The web server has been migrated to different hosts, and even to a different data center altogether. In addition we have also spun up another 2012 R2 server and migrated the site and the problem follows.
We have 2 other instances of this product, each with a dedicated web server and neither have this issue.
Using performance monitor we can see the request queue spike by 5x and in turn drive up executing time. Is there anything in IIS we can use (knowing the start and finish time of the issue) to potentially see the trigger of this spike?
Any help, advice and pointers appreciated!
Feb 09, 2018 06:15 PM|lextm|LINK
We have a third party application running which has its own 2012 R2 IIS server
Why not contact the third party vendor for support? You can learn from the internet that most of such issues are due to the third party products themselves, which you as IIS administrators usually have no easy way to analyze on your own.
Feb 09, 2018 07:05 PM|WideEyedFox|LINK
Feb 10, 2018 04:34 PM|lextm|LINK
the third party has spent 3 Weeks on this already
What have they done? I would be surprised if they did not ask for hang dumps and then analyze for the root cause. If they lack of such capabilities, I doubt if they really would like to resolve the issue for you. Of course, they might have application level
logging in the product as well to collect other data for troubleshooting, but after all they should have enough progress in three weeks (it is such a long time).
Opening a support case to involve Microsoft support might speed it up, as Microsoft guys surely have the skills to analyze hang dumps. But it is not cheap, and you need to check who will cover the cost (your company or the third party vendor).
Feb 12, 2018 07:55 AM|Yuk Ding|LINK
The IIS internal worker process monitor could display state and module of the hanged request. Of course ,the failed request tracing could help you as well:
This link provide the steps to fix:
I would like to know did you change something in IIS including the NTFS permission. Or did you get any limit or restriction with the concurrent request or memory usage?