IIS localhost file request issue

Question

Recently and out of the blue whilst working locally with iis 10 my web pages became unresponsive. After a little investigation if was clear the offending files seemed to be .asp.
All the pages on the site had worked perfectly up until this point as does the remote site still.
The only recent change to the local host machine was a win 10 update and an Adobe Dreamweaver update, this may be coincidence but the changes happened around the same time.
Having set many local servers up to work with classic asp in the past I was confused as to what could be causing the issue.
The network log shows all the files being requested and then some pending, which sill stay pending for various amount of time then suddenly load, however repeat loading of the page results in the error returning after just a couple of reloads.
One asp page is left with a 500 error Server.ScriptTimeout, but this will load independently if request without issue, so I believe it to be a symptom not the cause.
I’m not an expert in IIS and am hoping someone can shed light on this phenomenon. My thoughts were that it could be a thread limit related issue or a release thread issue. But I am truly stumped.
Below are snips of the network traffic from edge webtools

Answer 1

@AJMLECIRA

One asp page is left with a 500 error Server.ScriptTimeout, but this will load independently if request without issue, so I believe it to be a symptom not the cause.

ASP pages have to have a timeout, they cannot run indefinitely, so please check you have set ScriptTimeout in asp and iis? If not, try setting it. The maximum value for ScriptTimeout is 2147483647. but ScriptTimeout can never be lower than the AspScriptTimeout set in IIS.

In asp page:

<%  
    Server.ScriptTimeout = 2147483647  
%>  

In iis:

The Script Time-out specifies the default length of time that ASP pages allow a script to run before attempting to stop the script and writing an event to the Windows event log. The default is 00:01:30 minutes.

Click the ASP Tab --> Expand "Limit Properties" --> Set "Script Time-out" parameter to what you want.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi SamWu-msft, thanks for your answer.

All setting are as suggested, and the site works perfectly on the live server and another testing server as localhost with the same file set.
I have also set all the parameters of both localhost iis services to match and all windows services too.
I have even re installed IIS and windows itself on the culpable machine without effect.
The problem must be somewhere on this particular machine.
My last resort would be to do a complete drive wipe and restore the whole machine unless you have any other suggestions

Answer 3

Apologies for any miscommunications here or other forums, I very rarely use forums, but after 4 days of pain the problem lay in a corrupt database... making the diagnosis very difficult, however many thanks for those who have replied with suggestions, they were very much appreciated :-)