I'm using a third party app build on asp.net. It runs on Server 2003/IIS6. I changed the way that app pools are recycled. After this happened the third party application stopped working. Specifically URLs that didn't correspond to files in the third party program directory returned 404 errors.
(I'm not that up to speed on how asp.net works.) What I mean is that if I go to a URL like
example.com/thirdparty/page.aspx, when there is a page.aspx file in the third party program directory, the page works. If I go to
example.com/thirdparty/stylesheet6.css, when there is no stylesheet6.css file in the program directory, I get a 404 error.
It stopped working after I did this change to the app pools, though I could have changed some other aspect of the IIS configuration by mistake. I've put those app pool settings back how I think they were, but that hasn't fixed it.
The company for this third party software suggests uninstalls and reinstalls and restoring from backup (basically they haven't a clue why it's broken) but I'd like to undo what damage I did because that might be easier.
What sort of changes to IIS configuration could I have done that would break these sort of URLs?