Код ошибки 0x80070032 iis

IIS uses bindings to determine where to redirect requests. These bindings can be secured (https – mostly on port 443) or unsecured (http – mostly on 80).

In a case I worked on, I came across to this error while trying to add an https binding: The request is not supported (Exception from HRESULT: 0x80070032).

Nedim_0-1598277126016.png

The PowerShell command below gave an error too

netsh http add sslcert ipport=[IP:port] appid="[APP ID]" certhash=[HASH] certstorename=MY

SSL Certificate add failed, Error: 50
The request is not supported

Nedim_1-1598277126022.png

Additionally, Windows Update wasn’t working neither. It displayed the following error.

“We couldn’t connect to the update service. We’ll try again later, or you can check now.”

Solution

Since both secure binding and Windows Update were failing, the issue seemed to be related to TLS protocol settings.

If you are troubleshooting a similar issue, make sure TLS protocols and encryption algorithms are enabled. Additionally, check if secure cipher suites are enabled. In our case, there was only one cipher suite defined. This was the reason of both binding and Windows Update issues.

We followed the steps below to use default cipher suite list:

  1. Go to “Start > Run“. Enter: gpedit.msc
  2. In the left pane, expand “Computer Configuration > Administrative Templates > Network > SSL Configuration Settings
  3. In the right pane, right click “SSL Cipher Suite Order” and choose “Edit
  4. Save the text inside “SSL Chiper Suite” field to a Notepad for backup
  5. Select “Not Configured
  6. Click “OK
  7. Restart the server (gpupdate doesn’t enforce this setting. You should restart the server)

Nedim_2-1598277126042.jpeg

Note: If the setting is already «Not Configured», change it to «Enabled» and restart the server. It should work. Later, you can change it back to «Not Configured» and restart again.

Posted: April 27, 2011 | Filed under: .Net | Tags: asp.net, iis7.0 |

When you are building the first development environment  in your machine is common to have this error message thrown by IIS 7.0

HTTP Error 404.3 – Not Found
Description: The page you are requesting cannot be served because of
the Multipurpose Internet Mail Extensions (MIME) map policy that is
configured on the Web server. The page you requested has a file name
extension that is not recognized, and is not allowed.

Error Code: 0x80070032

Notification: ExecuteRequestHandler

Module: StaticFileModule

Requested URL: http://localhost:80/Default.aspx

Physical Path: C:\inetpub\wwwroot\Default.aspx

Logon User: Anonymous

Logon Method: Anonymous

Handler: StaticFile

The error message is saying that it didn’t recognize the mimetype as an static file. So, there is a problem with ASP.NET file handler.

The first thing you have to do is check if you have installed Microsoft .Net Framework vX.XX. To do this go to: Control Panel > Add and Remove Programs and check if it’s listed there

The second one, to check if the ASP.NET extensions are installed for IIS7.0. To do this go to Control Panel > Add and Remove Programs > turn windows features on or off > IIS


  • Remove From My Forums
  • Question

  • User-1019990578 posted

    Hi I am a complete noob with IIS 7.0, actually IIS in general but my project does work in Win XP SP2 IIS 5.1 with no probs.

    However when I install Vista Business and setup IIS 7.0 it automatically referred to .NET 2.0 without installation, (not sure if it comes as a default).

    When I try and run the site using
    http://localhost/test/default.aspx I get the following error:

    HTTP Error 404.3 — Not Found
    Description: The page you are requesting cannot be served because of
    the Multipurpose Internet Mail Extensions (MIME) map policy that is
    configured on the Web server. The page you requested has a file name
    extension that is not recognized, and is not allowed.

    Error Code: 0x80070032

    Notification: ExecuteRequestHandler

    Module: StaticFileModule

    Requested URL: http://localhost:80/ets/bob.asp

    Physical Path: C:\inetpub\wwwroot\ets\bob.asp

    Logon User: Anonymous

    Logon Method: Anonymous

    Handler: StaticFile

    Most likely causes:

    It is possible that a handler mapping is missing. By default, the
    static file handler processes all content.
    The feature you are trying to use may not be installed.
    The appropriate MIME map is not enabled for the Web site or
    application. (Warning: Do not create a MIME map for content that users
    should not download, such as .ASPX pages or .config files.)
    What you can try:

    In system.webServer/handlers:
    Ensure that the expected handler for the current page is mapped.
    Pay careful attention to preconditions (e.g. runtimeVersion,
    pipelineMode, bitness) and compare them to the settings for your
    application pool.
    Pay careful attention to typographical errors in the expected handler
    line.
    Please verify that the feature you are trying to use is installed.
    Verify that the MIME map is enabled or add the MIME map for the Web
    site using the command-line tool appcmd.exe.
    Open a command prompt and change directory to %windir%
    \system32\inetsrv.
    To set a MIME type, use the following syntax: appcmd set config /
    section:staticContent /+[fileExtension=’string’,mimeType=’string’]
    The variable fileExtension string is the file name extension and the
    variable mimeType string is the file type description.
    For example, to add a MIME map for a file which has the extension
    «.xyz», type the following at the command prompt, and then press
    Enter:
    appcmd set config /section:staticContent /+
    [fileExtension=’.xyz’,mimeType=’text/plain’]
    Warning: Ensure that this MIME mapping is needed for your Web server
    before adding it to the list. Configuration files such as .CONFIG or
    dynamic scripting pages such as .ASP or .ASPX, should not be
    downloaded directly and should always be processed through a handler.
    Other files such as database files or those used to store
    configuration, like .XML or .MDF, are sometimes used to store
    configuration information. Determine if clients can download these
    file types before enabling them.
    Create a tracing rule to track failed requests for this HTTP status
    code. For more information about creating a tracing rule for failed
    requests, click here.
    More Information… This error occurs when the file extension of the
    requested URL is for a MIME type that is not configured on the server.
    You can add a MIME type for the file extension for files that are not
    dynamic scripting pages, database, or configuration files. Process
    those file types using a handler. You should not allows direct
    downloads of dynamic scripting pages, database or configuration
    files.

    I am not quite sure what the issue is as it wasn’t that hard in IIS 5. I added default.aspx in the default parameters to look for if you don’t type in the filename of the root folder.

    Can anyone help with how I can overcome this issue, as I have absolutely no clue here.

    thanks for any tips in advance

    Ringo (aka blind venison)

Answers

  • User1073881637 posted

    Make sure ASP is installed.  By default, ASP is not installed with IIS.

    • Marked as answer by

      Tuesday, September 28, 2021 12:00 AM

  • User-1653247517 posted

    You say you requested default.aspx but the error indicates that you requested bob.asp. Are you getting 404.3 for default.aspx and bob.asp? Static file module is handling the asp, aspx requests on your machine. That means either you don’t have asp and asp.net
    installed on your machine or your system.webServer/handlers configuration is not correct. Can you make sure you have the components installed on the machine first?

    • Marked as answer by
      Anonymous
      Tuesday, September 28, 2021 12:00 AM

  • User-1019990578 posted

    Ok have had a chance to look at the issue further and I had to do the following:

    First of all I had to put it back to the Pipeline mode as I believe I had it in Classic mode when setting up the virtual application. (sorry if all the terminology is wrong as it is on another machine that is now shut down and I need some sleep)

    I then tried it and I ended up with a 500 server error and it suggested that I add <identity impersonate=»false» /> in the first choice to fix the error (from 3 options) as it sounded like it suggested impersonatioon was only avail in .NET 3.0?

    Anywayz, it has got the problem sorted. It isn’t or wasn’t as hard as I had thought even for a noob like me.

    The error handling messages are fantastic and give some very good suggestions; my hat goes off to the developers just on this alone.

    thanks, problem now sorted.

    • Marked as answer by
      Anonymous
      Tuesday, September 28, 2021 12:00 AM

ASP.Net Не запускается приложение. Регистрация компонентов в IIS 8.5

Дано: Windows Server 2012 R2, IIS 8.5, на нем установлен сайт — приложение ASP.Net.
Проблема: при запуске сайта выдается ошибка 404.3.

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 Code 0x80070032

Т.е. это означает, что в IIS не зарегистрированы компоненты ASP.Net  и отсутствуют его handlers.
Предположим, что всё необходимое уже сделано, т.е. установлены компоненты .Net Framework и  ASP.Net:

В большинстве случаев помогала перерегистрация компонентов ASP.NET при помощи команды aspnet_regiis.exe с ключом «-i» (под администратором). Найти ее можно по пути  C:\Windows\Microsoft.NET\Framework64\v4…
Обычно после ее выполнения все необходимые компоненты в IIS появляются и дальнейшие действия не требуются.
Однако, с недавнего времени, данная регистрирующая утилита перестала поддерживаться и при запуске выдается следующее сообщение:
This option is not supported on this version of the operating system.  Administrators should instead install/uninstall ASP.NET 4.5 with IIS8 using the «Turn Windows Features On/Off» dialog, 
the Server Manager management tool, or the dism.exe command line tool.  For more 
details please see go.microsoft.com/fwlink/?LinkID=216771.

Как говорилось выше компонент ASP.NET 4.5 уже был установлен, однако IIS по-прежнему его не видит. Все инструкции по приведенной ссылке были выполнены.

Чтобы решить данную проблему и перерегистрировать компоненты ASP.NET 4.5, необходимо выполнить следующую dism команду:

dism /online /enable-feature /featurename:IIS-ASPNET45 /all

Результат ее работы:

Теперь можно проверять, компоненты должны появиться.

Для использования возможностей WCF, возможно потребуется выполнение следующих команд:

dism /Online /Enable-Feature /FeatureName:WAS-WindowsActivationService
dism /Online /Enable-Feature /FeatureName:WAS-ProcessModel
dism /Online /Enable-Feature /FeatureName:WAS-NetFxEnvironment
dism /Online /Enable-Feature /FeatureName:WAS-ConfigurationAPI
dism /Online /Enable-Feature /FeatureName:WCF-HTTP-Activation
dism /Online /Enable-Feature /FeatureName:WCF-HTTP-Activation45

Если Вам понравилась статья, пожалуйста, поставьте лайк, сделайте репост или оставьте комментарий. Если у Вас есть какие-либо замечания, также пишите комментарии.

  • Remove From My Forums
  • Question

  • User-1019990578 posted

    Hi I am a complete noob with IIS 7.0, actually IIS in general but my project does work in Win XP SP2 IIS 5.1 with no probs.

    However when I install Vista Business and setup IIS 7.0 it automatically referred to .NET 2.0 without installation, (not sure if it comes as a default).

    When I try and run the site using
    http://localhost/test/default.aspx I get the following error:

    HTTP Error 404.3 — Not Found
    Description: The page you are requesting cannot be served because of
    the Multipurpose Internet Mail Extensions (MIME) map policy that is
    configured on the Web server. The page you requested has a file name
    extension that is not recognized, and is not allowed.

    Error Code: 0x80070032

    Notification: ExecuteRequestHandler

    Module: StaticFileModule

    Requested URL: http://localhost:80/ets/bob.asp

    Physical Path: C:\inetpub\wwwroot\ets\bob.asp

    Logon User: Anonymous

    Logon Method: Anonymous

    Handler: StaticFile

    Most likely causes:

    It is possible that a handler mapping is missing. By default, the
    static file handler processes all content.
    The feature you are trying to use may not be installed.
    The appropriate MIME map is not enabled for the Web site or
    application. (Warning: Do not create a MIME map for content that users
    should not download, such as .ASPX pages or .config files.)
    What you can try:

    In system.webServer/handlers:
    Ensure that the expected handler for the current page is mapped.
    Pay careful attention to preconditions (e.g. runtimeVersion,
    pipelineMode, bitness) and compare them to the settings for your
    application pool.
    Pay careful attention to typographical errors in the expected handler
    line.
    Please verify that the feature you are trying to use is installed.
    Verify that the MIME map is enabled or add the MIME map for the Web
    site using the command-line tool appcmd.exe.
    Open a command prompt and change directory to %windir%
    \system32\inetsrv.
    To set a MIME type, use the following syntax: appcmd set config /
    section:staticContent /+[fileExtension=’string’,mimeType=’string’]
    The variable fileExtension string is the file name extension and the
    variable mimeType string is the file type description.
    For example, to add a MIME map for a file which has the extension
    «.xyz», type the following at the command prompt, and then press
    Enter:
    appcmd set config /section:staticContent /+
    [fileExtension=’.xyz’,mimeType=’text/plain’]
    Warning: Ensure that this MIME mapping is needed for your Web server
    before adding it to the list. Configuration files such as .CONFIG or
    dynamic scripting pages such as .ASP or .ASPX, should not be
    downloaded directly and should always be processed through a handler.
    Other files such as database files or those used to store
    configuration, like .XML or .MDF, are sometimes used to store
    configuration information. Determine if clients can download these
    file types before enabling them.
    Create a tracing rule to track failed requests for this HTTP status
    code. For more information about creating a tracing rule for failed
    requests, click here.
    More Information… This error occurs when the file extension of the
    requested URL is for a MIME type that is not configured on the server.
    You can add a MIME type for the file extension for files that are not
    dynamic scripting pages, database, or configuration files. Process
    those file types using a handler. You should not allows direct
    downloads of dynamic scripting pages, database or configuration
    files.

    I am not quite sure what the issue is as it wasn’t that hard in IIS 5. I added default.aspx in the default parameters to look for if you don’t type in the filename of the root folder.

    Can anyone help with how I can overcome this issue, as I have absolutely no clue here.

    thanks for any tips in advance

    Ringo (aka blind venison)

Answers

  • User1073881637 posted

    Make sure ASP is installed.  By default, ASP is not installed with IIS.

    • Marked as answer by

      Tuesday, September 28, 2021 12:00 AM

  • User-1653247517 posted

    You say you requested default.aspx but the error indicates that you requested bob.asp. Are you getting 404.3 for default.aspx and bob.asp? Static file module is handling the asp, aspx requests on your machine. That means either you don’t have asp and asp.net
    installed on your machine or your system.webServer/handlers configuration is not correct. Can you make sure you have the components installed on the machine first?

    • Marked as answer by
      Anonymous
      Tuesday, September 28, 2021 12:00 AM

  • User-1019990578 posted

    Ok have had a chance to look at the issue further and I had to do the following:

    First of all I had to put it back to the Pipeline mode as I believe I had it in Classic mode when setting up the virtual application. (sorry if all the terminology is wrong as it is on another machine that is now shut down and I need some sleep)

    I then tried it and I ended up with a 500 server error and it suggested that I add <identity impersonate=»false» /> in the first choice to fix the error (from 3 options) as it sounded like it suggested impersonatioon was only avail in .NET 3.0?

    Anywayz, it has got the problem sorted. It isn’t or wasn’t as hard as I had thought even for a noob like me.

    The error handling messages are fantastic and give some very good suggestions; my hat goes off to the developers just on this alone.

    thanks, problem now sorted.

    • Marked as answer by
      Anonymous
      Tuesday, September 28, 2021 12:00 AM

Понравилась статья? Поделить с друзьями:
  • Код ошибки 0x80070017 при обновлении windows 10
  • Код ошибки 0x80070026 при установке windows server 2016
  • Код ошибки 0x8007002
  • Код ошибки 0x8007001f 0x20006
  • Код ошибки 0x80070017 как исправить