2012 IIS server site on another drive

I am trying to run IIS 8 on a completely new 2012 server and run the .net 4.5 application and I cannot get it to work with disks

Error: 500.19 Module IIS Web Core Notification Unknown Handler Not yet determined Error Code 0x80070005 Config Error Cannot read configuration file due to insufficient permissions Config File \\?\D:\callsheet-test\web.config 

The current site is just one index.html file.

If I copy the folder anywhere in c: for example, c: \ callheet-test \ or c: \ inetpub \ callheet-test, it works fine once I change the destination location in IIS 8 (site> basic settings).

It doesn't matter if the web.config file is like a complex mvc / webforms application that gives the same error.

I tried to copy the file with permissions and even thought that the permissions correspond to all users. I am still getting this error.

I deleted the partition and recreated it as the mount point c: \ mount, and the same problem occurred. Copy the files to c: \ notamount and they work fine.

This server runs on a VMware server. Windows 2012 x64 standard.

+4
source share
2 answers

Based on further investigation of the problem (from the link in my comment above), I found a workaround through here : change the value of the group policy “Audit of removable storage” from “Not configured” to “No audit” and reboot. Bizarre I know. This option is located in the Windows Settings / Security Settings / Advanced Audit Policy Policy / System Audit Policies / Object Access.

Despite using VMWare rather than Hyper-V, this solution still works for me. I hope Microsoft can give an answer.

+1
source

I also had the same error and the solution was similar. I installed Sql Server 2012 on Windows Server 2012, and it was during this time that I noticed that the IIS worker processes running from the C: system drive were unable to access the configuration files on the E: drive. The site can only be downloaded on the C: drive, despite all the necessary NTFS permissions provided through IIS_IUSRS, IUSR, Users and / or even a specific AppPool. This became apparent when IIS was unable to access E: drive even when starting AppPool (.NET 4.5) using an administrator account other than the ApplicationPoolIdentity account (IIS APPPOOL.NET v4.5 in this context - verified in procexp. exe), Installing Sql Server 2012 caused installation errors and required enabling auditing to access objects, among other parameters.

Decision:

  • Run → secpol.msc
  • Security Settings → Local Policies → Audit Policy
  • Change the Access Audit Objects policy to No Audit

Hope this background helps relieve a headache. :-)

0
source

All Articles