Select to view content in your preferred language

Web Adaptor 500.19 Internal Server Error

2297
2
Jump to solution
04-13-2018 04:55 PM
DouglasLong
Regular Contributor

I installed Web adaptor, having issues getting it to run properly. cant access the configuration page.

I get the following error, any thoughts?

HTTP Error 500.19 - Internal Server Error

The requested page cannot be accessed because the related configuration data for the page is invalid.

Detailed Error Information:

Module   IIS Web Core
Notification   BeginRequest
Handler   Not yet determined
Error Code   0x80070021
Config Error   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".
Config File   \\?\C:\inetpub\####\arcgis\web.config
Requested URL   http://####/arcgis/webapaptor
Physical Path   C:\inetpub\###\arcgis\webapaptor
Logon Method   Not yet determined
Logon User   Not yet determined

Config Source:

  272:   273:         <handlers>  274:             <remove name="StaticFile" />

More Information:

This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.

View more information »

0 Kudos
1 Solution

Accepted Solutions
DouglasLong
Regular Contributor

nevermind, I solved it by uninstalling net framework 4.5 and reinstalling (im on windows server 2012 R2).

View solution in original post

2 Replies
DouglasLong
Regular Contributor

nevermind, I solved it by uninstalling net framework 4.5 and reinstalling (im on windows server 2012 R2).

LHo
by
Occasional Contributor

We had a similar issue in ArcGIS Web Adaptor 11.3 fresh install where we installed the .NET hosting bundle 8.0.11 as the first prerequisite install. We saw an error code: 0x800700d. 

LHo_0-1732059064987.png

 

 

We needed to run a repair on the .NET installation for it to work.

0 Kudos