IIS 5 & IIS 6
IIS recycle when adding new App Pool
Last post May 06, 2008 09:32 AM by gettinlucky
May 05, 2008 09:07 AM|gettinlucky|LINK
I'm sure this has been answered already (or maybe not) but I cannot find any info on it. I'm having troubles in IIS when adding a new Application Pool. It apperas to restart IIS. Though I do not see any hang on the server at this point in the process. I'm
getting a large hang when creating the folder as an application and swicting it to the newly created app pool. I'm also seeing a hang when switching to .net 2.0. For some reason one of these steps is causing IIS to do a full restart.
Perhaps some one can lead me to a solution of a KB article on this problem. I would add another app pool and associated appliaction to see when it does it but there is something about takeing down 80 applications that does not sound very nice to do just
Thanks for any help,
IIS 6.0 Restarting
May 06, 2008 02:19 AM|ganeshanekar|LINK
How are you creating the app pool? Are you using Default App pool as template?
There is no such issue when you create a new app pool which causes entire IIS to go down.
If you facing this issue, can run Process monitor and check the activity happening?
What if you create a new app pool and then a new virtual directory assigned to that app pool...does it cause the Hang as well?
May 06, 2008 09:32 AM|gettinlucky|LINK
Thanks for responding, and I have found the problem. I decided to test it out on my server at home as thats not going to cause 50+ people to call me screaming because they just got bounced out of there program. It's not that creating the App Pool is causing
the issue or making the directory an application that is the issue. The problem is when I switch the newly created directory/application's ASP.NET level from 1.1.xx to 2.0.xx or vice versa.
I'm not sure why IIS must do a full restart when this happens, but it does or at least appears to as all the w3wp.exe's are gone after and it shows in event log that IIS restarted. Maybe you or some one could explain why it must. But to "fix" this I will
be switching the website it's self from 1.1.xx to 2.0.xx this weekend so that I will no longer have to change the .net level at the individual application level.
Oh and I'm creating the app pools manualy and normally use the last one I created as a template that way I know it has the right settings.
Thats for the response though.