Multiple Application Errors - application taken offline errors in Application Pools

Originally posted by : steve schofield (steve@aspfree.com)Hi All,I ran into when trying to get applications using the Default Application Pool. I was running into Server application unavailable error message. After further research, I wasn't able to get any applications(TLD's, or virtual application roots) using the Default Application Pool. Defined in the IIS MMC, right click on properties, Home directory tab, application settings, application pool. If I switched the application pool to SharePoint application pool, webpages(ASPX, ASP, and HTML) started to work.1. When trying to launch ALL types(ASPX, ASP or HTML) pages of webpages when the application is configured using the Default Application Pool. The following error is shown to the user "Multiple Application Errors - application taken offline.". The Everytime application that is configured using this application pool gets hit. This an event log message, Source WAS: EventID:22 The application pool 'DefaultAppPool' has been disabled because of a failure to create a worker process to serve the application pool. The data field contains the error number. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.I tried to recycle the Application process, doing an IISReset, change permissions of the user account it was running under each time i would stop and start the process using IIS MMC, same result.2. I created a new Application Pool called "test" and defined the TLD using this new application pool. I getthis error (Server Application Unavailable) when trying aspx pages . HTML and ASP pages work. Only ASPX pages didn't work and gave me the error below.Server Application UnavailableThe web application you are attempting to access on this web server iscurrently unavailable. Please hit the "Refresh" button in your web browserto retry your request.Administrator Note: An error message detailing the cause of this specificrequest failure can be found in the system event log of the web server.Please review this log entry to discover what caused this error to occur.However nothing would show up in the event log.I did an IISReset on various occasions, stopping the WWW service and performing tests on multiple types (HTML, ASP and ASPX) of webpages. Each time the problems described happened, before and after a reboot of the server. The help documents haven't been to in-depth describing this new application pool architecture. Anyone else run into this?