There was an issue where after a fresh install of the SharePoint Server 2016, the Central Administration website could not be accessed. The following error "the website cannot display Page” with HTTP error code 500 is displayed. There is no clue from the Event Log or ULS log. Tried Fiddler but no luck. Finally, a feature in IIS called “Failed Tracing Request” was found. As soon as it was enabled and the XML file was read, the cause was found.2016-03-25_23h47_29

To Enable Trace Logging for Failed Requests, please check this blog: Enable Trace Logging

Go to the logs file location and click the XML file. (Note: you will get this file once you enable the Failed Tracing request and create the rule.)2016-03-25_23h50_03

In the file it gives the following details:

Error Code: The process cannot access the file because another process has locked a portion of the file. (0x80070021)

ConfigExceptionInfo:\\?\C:\inetpub\wwwroot\wss\VirtualDirectories\39229\web.config ( 817) :This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault=”Deny”), or set explicitly by a location tag with overrideMode=”Deny” or the legacy allowOverride=”false”.


From the above error, it is not clear which section is locked at the parent level.Open the web.config file of Central Admin and go to line 817. This line tells says that Module Section is called here. Let’s check the IIS.

  • Open IIS Manager
  • Click on Server in Connection Pane. Double-click on Configuration Editor under Management in the Feature Pane.2016-03-25_23h51_09
  • In the Configuration Editor, click on Section Drop Down, expand the System.webServer and select Modules.
  • Here is the problem. You can see this Section is Locked (see under the Actions Pane).2016-03-25_23h52_00


To resolve the issue, please click on the Unlock Section. You will be all set now.

This problem can happen with the web application if the Module Section is locked.