Hi, I made first wconnect intallation and HTTP Error 500.19 - Internal Server Error
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:\wconnect\web\wconnect\web.config
Looks like your installation did not properly configure the virtual directory. Check in the IIS Management console and make sure that the /wconnect
virtual is configured as a virtual application:
This should happen automatically if you run SETUP.exe. Make sure you don't get any errors and if you do report them here.
For more info see here:
+++ Rick ---
Hi,
I hope this helps if you get this same error message: "HTTP Error 500.19 - Internal Server Error" which I did after installing West Wind Web Connection on a Windows 10 laptop.
Following Rick's recommendation, I did firstly confirmed that /wconnect virtual was configured as a virtual application. I then did some more research and found the following to be the most useful: https://docs.microsoft.com/en-us/iis/get-started/planning-for-security/how-to-use-locking-in-iis-configuration
My suggested resolve is...
1 - Use a text editor (e.g. Notepad) to open: %windir%\system32\inetsrv\config\applicationHost.config (possibly make a backup copy of it first)
2 - Change/update the file as follows:
Best regards, Simon
Yup that will work.
This is not a default setting however - handlers
and modules
are not locked down by default unless somebody changed policy on the machine. So whether an explicit change or a changed through corporate policy any number of the sections required by Web Connection (and many other things) can be locked down. Locking down handlers
and modules
will affect ASP.NET in general not just Web Connection.
+++ Rick ---