I am moving my asp classic code over to the IIS7 2008 web server.
I'm going through my code and finding problems and debugging and copying changes files up to the server and retesting etc. Pretty normal stuff.
My web app is in its own application pool. For no apparent reason, the application pool will just stop. Then the browser screen will grind and do nothing and then I'll realize it's not my code, it's because the app pool has stopped.
Sometimes it just hourglass grinds, and other times it will give a message that the application isn't availble or something similar.
Anyway, why is it resetting my app pool? What can I do to get it to stop?
I have tried both Integrated and Classic mode and it occurs in both.
Will this quit happening when I stop finding problems? Because this is scary that I would put a live website on 2008 and have it just stop the application for no apparent reason.