IIS 5 Isolation mode

A couple of weeks ago I had some trouble with windows 2003/IIS 6. Finally I got my asp.net application which uses a COM component to work under windows 2003. I tried everything, I even gave my Network Service account administrator rights and even that didn't work. Until I found the IIS 5 Isolation mode option in the IIS manager. So if you're having problems getting a asp.net application to work under IIS 6 and getting desperate, try the IIS 5 Isolation mode. You can find it this way:  Right click on Websites in the IIS Manager, choose Service and check the IIS 5 Isolation mode checkbox.

From: Jonne Kats
Via: Tech Guru

 

2 Comments

  • You should have been able to configure the application pool for the application to run as a specific account.



    If your application is running in anonymous mode then the application pool's identity doesn't act as the account it runs under (bug?) but the IUSR_ account for the machine.



    If you are using NT authentication then the application pool's identity is used (defaults to IWAM_ i think).



    Then you could have checked what account was trying to access the component using FILEMON. (www.sysinternals.com)

  • Hi Darrel Yes I consult Dotnetjunkies everytime but I missed this info, so I got it from Tech Guru. Simple as this I mention the writer and how I found the info.

    And yes I LOVE reading bloggers from dotnetjunkies ;-)

Comments have been disabled for this content.