IIS 5 & IIS 6
ASP lockup - Recycle worker process?
Last post Jul 24, 2008 03:36 AM by tigermatt
Jul 16, 2008 03:29 PM|tigermatt|LINK
I am currently in the middle of developing a new application on my IIS server. It would seem that any minor coding issues I may create with any ADO object will cause IIS to stop serving ASP pages, although HTML pages will still respond perfectly fine.
Note that I do not believe this is an issue code-wise - although the code IS deliberately faulty (which causes the error), it just seems to be any code which is incorrect related to any instance of any ADO object.
I have found that recycling the worker process for my DefaultAppPool will kick start ASP back running again, but as would be expected, the problem repeats the next time I get an error (or if I refresh the erroring page).
I have tried creating a new application pool with no success. Surely there must be somebody out there who can help me to solve this issue?
Jul 24, 2008 12:48 AM|davcox|LINK
When you say it "stop serving ASP pages" does that mean that future requests for ASP pages will timeout (hang) or do they return some kind of 500 error?
Also, are you saying just one request to the bad application will cause this?
Jul 24, 2008 03:36 AM|tigermatt|LINK
Any request to any slightly incorrect piece of ASP code seems to do this. IIS simply stops responding to all requests for ASP - although it will happily continue serving HTML pages.
It seems more often than not that the faulty piece of code is something to do with ADO - perhaps a connection to a database which has been moved etc.
It seems to have stopped - at least for my development site - ever since I created it a new application pool and then disabled ASP server-side debugging. I don't have a clue why that would interfere - but I'm still monitoring it to check that has actually
If you have any further suggestions though, they are much appreciated :)
IIS 6.0 hang