Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

"The page you are requesting cannot be served because of the extension configuration." error message

Tags:

asp.net

iis

People also ask

How do I fix HTTP Error 404.3 Not Found?

To Overcome “HTTP Error 404.3 - Not Found THE PAGE YOU ARE REQUESTING CANNOT BE SERVED BECAUSE OF THE EXTENSION CONFIGURATION. IF THE PAGE IS A SCRIPT, ADD A HANDLER. IF THE FILE SHOULD BE DOWNLOADED, ADD A MIME MAP.” Error.

Is ASP net installed?

Click the radio button for Select a server from the server pool. The local server is selected by default. Click Next. If ASP.NET 3.5 or 4.5 are installed, in the list of Roles they will be located under Web Server (IIS) > Web Server > Application Development.


In Windows 8/10, you have to use

  • Open Control Panel →
  • Programs and Features →
  • Turn Windows features on or off →
  • Internet Information Services (IIS) →
  • World Wide Web Services →
  • Application Development Features →
  • Check the appropriate items, such as enabling ASP.NET. (i.e install the appropriate version you want to configure your websites with)

Reference: Check the solution of this question for reference


Use aspnet_regiis.exe to register version of .NET framework you are using.

This is a common issue and happens when IIS is installed after VS or .NET framework.

Note - for Windows 8/10 users, see the other answer by JohnOpincar below. And also the comment/tip from Kevin Brydon.


I fixed that on my Windows 10:

  1. Go to Control Panel - Programs and Features - Turn Windows features on or off.

  2. Select .NET Framework 4.6 Advanced Services - WCF Services

  3. Check HTTP Activation.

  4. OK done.


In my case I needed to add MIME types for each file extension that I wanted to serve to web config:

<system.webServer>
    <staticContent>
      <mimeMap fileExtension=".shp" mimeType="application/octet-stream" />
      <mimeMap fileExtension=".dbf" mimeType="application/octet-stream" />
      <mimeMap fileExtension=".kml" mimeType="text/xml" />
    </staticContent>
    ...
</system.webServer>