Geek Answers Handbook

ApplicationPoolIdentity in IIS7 401 Errors

We just started using Windows Server 2008 R2 and IIS7.5, and I am trying to move some existing sites from our Windows 2003 window. I can make the sites work fine, but I get 401 errors for all CSS / images on the sites. Giving everyone access to reading will solve this, but I'm not very happy doing this.

I read that IIS7.5 uses a magical new “account” , and each application pool has its own account.

I still have

  • Created a new folder in wwwroot for my site (kbank)
  • I copied the files from another computer.
  • IIS7 created a new website (not a virtual directory), this created a new application pool with the same name as my website. This is a combined pipe pool.
  • Process Model / Identity set ApplicationPoolIdentity and Load User Profile to True
  • Granted access to IIS AppPool \ kbank for access to the root in the folder

Can someone tell me how best to set up my sites.

+4
source share
3 answers

Perhaps you just missed a small step. When you granted read access to the account, you verified that it replaced settings in all subdirectories. In addition, after changing permissions, IIS reset may be required.

+1
source

2008 R2 IIS 7.5

Like fyi. After recovering the servers and spending endless hours resolving error 401.3 after changing the AppPool ID for the domain account, we came to the conclusion that the GPO is killing IIS. Make sure that you test the server in the Computer container and that no GPO changes groups with restrictions outside Administrators.

In our case, NT Authority \ Authenticated Users was removed from the local user group, and it shut down IIS.

+2
source

I would see what the exact 401 error status code is. IIS 7 status code Once you know the exact error code, it will be easy for you to fix the problem.
I also launched Process Monitor and looked to see if there is any “ACCESS DENIED” using the filter.

Yours faithfully,
Vivec.

0
source

More articles:


All Articles