mikeWarners
10-26-2005, 02:41 AM
Currently, we develop all our pages in ASP, and host them on a Windows-based server. We've had problems with the server caching (and sending out) old versions of pages, which we've managed to solve by using IIS on the server and stopping/restarting service for the domain in question.
I had this problem on one of our domains yesterday, so I used IIS as normal. However, when I restarted the service, all the active pages for that particular domain (ASP etc.) wouldn't parse - they just came up with a HTTP 500 error, or a message saying "The server is currently disabled". Static html pages work just fine; anything that requires preprocessing doesn't.
Technical support haven't been too helpful, and I was hoping that someone here had been having similar problems and knew of a solution!
I had this problem on one of our domains yesterday, so I used IIS as normal. However, when I restarted the service, all the active pages for that particular domain (ASP etc.) wouldn't parse - they just came up with a HTTP 500 error, or a message saying "The server is currently disabled". Static html pages work just fine; anything that requires preprocessing doesn't.
Technical support haven't been too helpful, and I was hoping that someone here had been having similar problems and knew of a solution!