ASP.NET Core web API : 0x80070021

Question

ASP.NET Core web API : 0x80070021

Holysmokes-6260 41

web.config.txtHi,

I am struggling to visualize a detail error of my asp.net core web api application (NET 6) as nothing is logged.

In IIS i receive the following error

IIS 10.0 Detailed Error - 500.19 - Internal Server Error

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

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".

Could someone shed some light on this issue? I attach my web.config

Thanks,

Holy

AgaveJoe 30,126 Reputation points

2023-05-15T13:28:41.32+00:00

ASP.NET Core uses the web config to locate and start the Core application. The web.config is not used like is was in ASP.NET applications. ASP.NET Core Configuration is in the appsettings.json file.

Use the web.config created by the deployment process and do not add customErrors, compilation, handler, elements. Just deploy the web.config as is.
Lex Li (Microsoft) 6,037 Reputation points Microsoft Employee

2023-05-17T06:06:01.2633333+00:00

The web.config file you used assumes that system.webServer/handlers and system.webServer/modules can be overridden to add ASP.NET Core module to the pipeline. But this isn't always possible if your server administrators decided to lock them up. Please contact them and ask for assistance. This is not what you can resolve on your own.

Accepted answer

0 additional answers

Your answer

AgaveJoe 30,126 Reputation points

2023-05-15T13:28:41.32+00:00

ASP.NET Core uses the web config to locate and start the Core application. The web.config is not used like is was in ASP.NET applications. ASP.NET Core Configuration is in the appsettings.json file.

Use the web.config created by the deployment process and do not add customErrors, compilation, handler, elements. Just deploy the web.config as is.
Lex Li (Microsoft) 6,037 Reputation points Microsoft Employee

2023-05-17T06:06:01.2633333+00:00

The web.config file you used assumes that system.webServer/handlers and system.webServer/modules can be overridden to add ASP.NET Core module to the pipeline. But this isn't always possible if your server administrators decided to lock them up. Please contact them and ask for assistance. This is not what you can resolve on your own.

Answer 1

Sam Wu-MSFT 7,561 Microsoft External Staff

@Holysmokes-6260

This problem can occur if the specified portion of the IIS configuration file is locked at a higher configuration level.

Try to unlock the specified section, or don't use it at the higher level. For more information about configuration locking, see How to Use Locking in IIS 7.0 Configuration.

Another way is checking your windows features.

Click "Start button"
in the search box, enter "Turn windows features on or off"
in the features window, Click: "Internet Information Services"
Click: "World Wide Web Services"
Click: "Application Development Features"
Check (enable) the features. I checked all but CGI.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Holysmokes-6260 41 Reputation points

2023-05-22T13:08:10.1066667+00:00

Sorry for updating late. I just tried the step How to Use Locking in IIS 7.0 Configuration. and got it resolved.

Thanks all,

Hol
Raja Rupinder 0 Reputation points

2023-12-06T07:12:48.9466667+00:00

Absolute spot-on.

Share via

ASP.NET Core web API : 0x80070021

0 additional answers

Your answer