I do a lot of website testing on my internal SBS box. With the release of DotNetNuke 4.0 I simply had to install it. As part of its setup requirements, I needed the newly released .NET 2.0 installed on my server. Sure, I thought…. I will need that for SQL 2005 anyway later…
So, I backed up the server… and installed. All seemed to go pretty well, and my new DotNetNuke 4.0 site was up and running in no time, but I did have to set the site to use the ASP.NET version 2.0.xxxx on the ASP.NET tab.
A little while later, I had to get something from my Companyweb site. Uh oh…. an error:
Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable. Please hit the “Refresh” button in your web browser to retry your request.
Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log
After I picked myself up off the floor I thought, let’s try an IISRESET…. which worked, but now my new DotNetNuke site gave the same above error. Time to look in the event viewer….
The event viewer is reporting
ASP.NET 2.0.50727.0
It is not possible to run two different versions of ASP.NET in the same IIS process. Please use the IIS Administration Tool to reconfigure your server to run the application in a separate process.
One Google search later, and I come up with a post from John Brennan that gives us an answer.
Basically, ASP.NET cannot run two versions in the same Application Pool. You simply need to create another pool, and then assign the site to that pool. Simple Eh 😉