Jump to content


Photo

ALE - HTTP Error 500.19 - Internal Server Error


  • Please log in to reply
2 replies to this topic

#1 Scott Walker

Scott Walker

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 07 February 2013 - 04:09 PM

Hi,

Im getting the following error when trying to run ALE:

Server Error
Internet Information Services 7.5
Error Summary
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 0x800700b7
Config Error There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined
Config File \\?\C:\Program Files (x86)\NetWrix\Account Lockout Examiner\Web\web.config
Requested URL http://localhost:80/ALE/
Physical Path C:\Program Files (x86)\NetWrix\Account Lockout Examiner\Web\
Logon Method Not yet determined
Logon User Not yet determined
Config Source
13: <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
14: <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
15: <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
Links and 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 »

#2 Tommy Garvin

Tommy Garvin

    Advanced Member

  • Members
  • PipPipPip
  • 92 posts
  • Gender:Male
  • Location:Tampa, FL

Posted 12 February 2013 - 01:06 PM

Hi Scott Walker,

The error you have occurs because system.web.extensions sectiones are defined both in site-level and application level web.configs. This can happen with applications developed for ASP.NET 2.0 when ASP.NET 4.0 is set as default.

Please go to IIS manager, in the left pane select Applications pool, make sure that DefaultAppPool uses ASP.NET 2.0 (.NET Framework column in the central pane)

The workaround for the this is to delete or comment out all the system.web.extensions configuration section definitions and configuration section group definitions from the application-level Web.config file. It is located in the \Web subfolder in the Account Lockout Examiner installation directory.

If the issue persists, please provide us with a screenshot of the error, version of .NET installed, and your web.config file from Web folder in the Account Lockout Examiner installation directory.

Please zip your files and upload them at www.netwrix.com/upload . Please specify the following in the subject line: Forum-ALE

- Tommy

#3 mmahacek

mmahacek

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 06 November 2014 - 09:32 PM

I am getting the same error on my Win 2012 R2 server. I switched to .NET 2 and now get this error:


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:\Program Files (x86)\Netwrix\Account Lockout Examiner\Web\web.config



Requested URL
http://localhost:80/ALE/

Physical Path
C:\Program Files (x86)\Netwrix\Account Lockout Examiner\Web\

Logon Method
Not yet determined

Logon User
Not yet determined




Config Source:
139: </modules>
140: <handlers>
141: <remove name="WebServiceHandlerFactory-Integrated"/>




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 user(s) are reading this topic

0 members, guests, anonymous users