« Previous Next »

• 11-02-2009, 9:56 AM

  shapper Joined on 11-28-2004, 9:15 PM Posts 47

  Cannot verify access to path C:\inetpub\wwwroot\ Reply Contact  Hello, When creating a web site I clicked "Test Settings" and: 1. It passed Authentication 2. It didn't pass Authorization. I get the following error:  "Cannot verify access to path C:\inetpub\wwwroot\" 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." What is wrong? How can I solve this problem? Thanks, Miguel

• 11-02-2009, 9:57 PM

  In reply to

  lextm Joined on 10-22-2008, 12:18 AM Shanghai, PRC Posts 1,433	Re: Cannot verify access to path C:\inetpub\wwwroot\ Reply Contact In most cases, this is a false alarm which you can ignore. Regards, Lex Li Support Engineer at Microsoft --------------------------- This posting is provided "AS IS" with no warranties, and confers no rights.

• 11-04-2009, 2:53 AM

  In reply to

  mook Joined on 11-04-2009, 7:47 AM Posts 1

  Re: Cannot verify access to path C:\inetpub\wwwroot\ Reply Contact   lextm: In most cases, this is a false alarm which you can ignore. Regards, Please does anyone have an elaborate answer to this problem? I have the same problem and I cannot test my websites which are created in the wwwroot directory. If the problem cannot be ignored what are the alternative solutions to this problem? Best regards

• 11-04-2009, 4:42 AM

  In reply to

  qbernard Joined on 03-25-2003, 10:12 PM Malaysia Posts 3,252	Re: Cannot verify access to path C:\inetpub\wwwroot\ Reply Contact For built-in accounts, it can't verify it as it is only valid at run-time. The explaination is exactly stated in the error msgs :) Cheers, Bernard Cheah