asked on IIS APP Pool Change
Hi All,
This is unexplainable to me but if I have IIS 7.5 and I have some web sites defined in it. The web sites work fine most of the time. I have the same setup in two different machines. A TEST and a USE (TEST and PROD essentially). However, something really weird happens on both these machines - it mysteriously changed the app pool to something I never defined it for.
Then on the TEST machine I have the APP POOL set to an identity of a unique account one as the Local System did not work. (That didn't make sense.)
Now, on the USE machine I came to find out that the APP POOL changed there too. However, I could not create the identity to the unique account. That did not work. I had to change it to Local System and then it worked.
The APP POOL on both mysteriously changed from the original app pool to ASP.NET 4.0 Classic.
Does anybody have any idea or know why the APP POOL would change from the original to the ASP.NET 4.0 Classic? And does anybody have any idea why the identities would need to differ? (i.e. the TEST is the opposite of PROD (and they can't alternate))?
I'm stumped on this one and hope that somebody has as answer.
Thanks
This is unexplainable to me but if I have IIS 7.5 and I have some web sites defined in it. The web sites work fine most of the time. I have the same setup in two different machines. A TEST and a USE (TEST and PROD essentially). However, something really weird happens on both these machines - it mysteriously changed the app pool to something I never defined it for.
Then on the TEST machine I have the APP POOL set to an identity of a unique account one as the Local System did not work. (That didn't make sense.)
Now, on the USE machine I came to find out that the APP POOL changed there too. However, I could not create the identity to the unique account. That did not work. I had to change it to Local System and then it worked.
The APP POOL on both mysteriously changed from the original app pool to ASP.NET 4.0 Classic.
Does anybody have any idea or know why the APP POOL would change from the original to the ASP.NET 4.0 Classic? And does anybody have any idea why the identities would need to differ? (i.e. the TEST is the opposite of PROD (and they can't alternate))?
I'm stumped on this one and hope that somebody has as answer.
Thanks
Microsoft IIS Web ServerASP.NETSSL / HTTPS
Last Comment
Marc Davis
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Without more detail about what your code is doing I can't say why the application pool is making a difference. Remember, the account the code is running as affects the permissions of the code, so without knowing what the code is doing I can't determine why it's failing.
ASKER
It's actually not the code as we determined. It's the nature of the app pool.
Thanks for the information guys! It are reaching out to our networking folks to see if the cloning of the VM had any impact.
Thanks!
Thanks for the information guys! It are reaching out to our networking folks to see if the cloning of the VM had any impact.
Thanks!
Chinmay_Patel, but if that is the only one that works it is the only one that works. Why the difference is beyond me - in relation to why the TEST environment has one thing that works and the USE environment has another (albeit local system). Any ideas on that aspect?