Now I would certainly not call myself an iis buff, as this would be a lie. I can however get by setting sites/ftp users up. I have even installed php and asp.net....but this is as far as I like to get into the nuts and bolts of IIS and web server configuration!
Problem: I recently moved an application from asp.net 1.1 to 2.0. That was easily done and my new and improved aplication was working fine on my production machine. The machine to host the new application was already running a 1.1 application. Having had a quick look at some MS support sites, it seemed like a very simple task to run both 1.1 and 2.0 sites on the same machine.
So all I did was switch the asp.net version, believing this was enough to get both sites working together. I was wrong. The following happened in the following order:
- The 1.1 site stopped working and gave "Server Application Error".
- The new 2.0 site never worked
- I had to "iisreset" to get ANYTHING working!!!!
So after that little mishap....i decided to google the problem and found that it was indeed a well known issue...silly of me to think it was that easy (its iis after all ;) I posted up on the www.iis-resources.com site and had a solution within minutes! (many thanks)
Solution: As pictured below, both sites need a seperate application pool. The sites WILL NOT WORK together unless you create and assign a seperate application pool to the 1.1 and 2.0 sites!! In my case the new 2.0 site used the ASP 2.0 pool while the old 1.1 app used the DefaultAppPool.
Write a comment
Required fields are marked with *.