LocalSystem (currently)
Main Topics
Browse All TopicsI get the following error when running the "test" for a virtual directory on IIS7 running locally on Vista 64 Ultimate:
"The server is configured to use pass-through authentication with a built-in account to access the specified physical path. However, IIS Manager cannot verify whether the built-in account has access. Make sure that the application pool identity has Read access to the physical path. If this server is joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that <domain>\<computer_name>$ has Read access to the physical path. Then test these settings again."
The computer is joined to a domain. The folder permissions are wide open ("god-mode") for IIS, IUSER, Network User, Everyone, etc. etc., but that does not work.
I've changed the application pool to use every combination I can think of - still same error!!!!
I've tried NetworkService, LocalService and LocalSystem for the app pool and have switched Managed Pipeline from "Integrated" to "Classic" and back again.
What's the secret to getting IIS7 to actually work on a LOCAL MACHINE?
What are the CORRECT settings (NetworkService, LocalService, LocalAccount?) for a LOCAL MACHINE?
I've recently moved to a Vista 64 machine and can't figure the secret magic trick, registry edit to make IIS7 actually work!
Anyone?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi,
have you seen this?:
http://forums.iis.net/t/11
Cheers.
I checked the link - noticed there was no resolution there either - except null sessions or to use an account other than NetworkService (which MS claims is not necessary, though they don't actually show you how to get NetworkService account to actually work). :(
Here's what I've done so far (besides granting full permissions to the application folder to every account on the machine - which STILL does nothing)
ran the following on the command line (apparently, this changes all the web.config files for all the apps running
under the "Default Web Site"
%SystemRoot%\system32\inet
right click the virtual directory and selected "convert to application" - fixed other errors and allowed me to change the application pool (sinde the default pool, no matter what, never appears to work )
created a new application pool called "compatibilitypool" - the default pool had the same settings but never worked, so I created a new pool
- set the following for the compatibilityPool I created, and the site is now visible (though the error above is still there, it still works)
Enable 32-bit Applications = True
Managed Pipeline Mode = Classic
Identity = NetworkService (this account has FullControl over the folder)
LoadUserProfile = False
Now I get "Error: Unable to Start Debugging on the Web Server" when trying to debug the app, though it works fine off of "http://localhost/mywebapp
I can debug a newly created website, so why not this one?!?!?
That's crazy! The only thing I can suggest (which is what I'd be doing in this situation) would be to enable auditing on the entire system and look for access failure events for clues as to what is going on. This should at least tell you want credentials are being passed and where access is being attempted (and failing)
Regards, Mike.
how do you enable auditing on Vista 64?
I'm thinking seriously about re-upgrading to Windows XP - Microsoft has almost no information concerning Visual Studio development on Vista 64.
I really don't know what the developers in Redmond are smoking these days, but they need to stop wasting money on marketing and come up with product that is usable without registry hacks, security hacks, command line tweaks and the hundreds of man-hours wasted just trying to accomplish the simplest task like getting a friggin' website to work properly.
Geez!
bd9000 is right - Microsoft are proving singularly useless in this area. I've Googled this problem extensively and the only responses I find are either people like me looking for a solution, or various uber-geekish responses that don;t sound anythging like solutions to me. This is fairly fundamental to my work as a web developer, yet here I am swimming around in the supposedly wonderful Windows 7 with no local webserver. Come on someone - how do I fix this??
Solution:
1- Open IIS 7.0
2- Select Default Web Site and Right-Click on it
3- Select Add Application... or Add Virtual Directory...
4- Select Contact as..
5- Change Path credentials: from Application user (pass-through authentication) to Specific user:
6- Add a Admin User with password like COMPUETRNAME\Administrator
Business Accounts
Answer for Membership
by: meverestPosted on 2009-03-23 at 15:06:51ID: 23962759
Hi,
what user are the application pools running as?
Cheers.