What are the configuration issues that IIS Metabase Analyzer detects, and how do I resolve them?
1. Multiple ASP.Net application versions in one Application Pool. This condition occurs when you are setting up a new website on an IIS web server with another ASP.Net web application already installed but of a different version of the .Net framework than your new application. If you forget to change the application pool from the default value, both ASP.Net applications (with different .Net framework versions will attempt to use the same Application Pool, which causes the Application Pool to crash. Once you have located the offending application, the easiest way to fix the issue is to create a new Application Pool, and assign the offending application to it, or assign the offending application to another Application Pool that contains ASP.Net applications at the same version as your offending application. 2. Use of differing .Net versions of the ASP.Net script processors in the same Web Application. You can specify custom script mappings inside the advanced application configuration se
