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).
The PowerShell command below gave an error too
netsh http add sslcert ipport=[IP:port] appid="[APP ID]" certhash=[HASH] certstorename=MYSSL Certificate add failed, Error: 50
The request is not supported
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:
- Go to “Start > Run“. Enter: gpedit.msc
- In the left pane, expand “Computer Configuration > Administrative Templates > Network > SSL Configuration Settings“
- In the right pane, right click “SSL Cipher Suite Order” and choose “Edit”
- Save the text inside “SSL Chiper Suite” field to a Notepad for backup
- Select “Not Configured”
- Click “OK”
- Restart the server (gpupdate doesn’t enforce this setting. You should restart the server)
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.
- 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:inetpubwwwrootetsbob.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%
system32inetsrv.
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
-
Marked as answer by
-
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
-
Marked as answer by
-
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
-
Marked as answer by
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:inetpubwwwrootDefault.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
Hi .. I’m unable to install IIS via PowerShell on a Windows 2012 R2 VM running Server Core. Other features work fine. Just anything related to web-server fails. It gets to about 90% and then spits out an error
I used to be able to fun this on all our Windows 2012 R2 servers, but it’s now failing on multiple systems. I can’t think of what’s different about them. I probably haven’t run this for about 6mos, so perhaps there’s an update that is causing the issue,
but I haven’t been able to find anything in my furious searching.
Windows Update is enabled (manual … we use WSUS) and works just fine. UAC is disabled, firewall is disabled, there’s no network filtering or anything else I can think of.
Anyone have some idea?
PS C:> get-windowsfeature web-server | Install-WindowsFeature -IncludeAllSubFeature -Verbose
VERBOSE: Installation started...
VERBOSE: Continue with installation?
VERBOSE: Prerequisite processing started...
VERBOSE: Prerequisite processing succeeded.
Install-WindowsFeature : The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed.
The request is not supported. Error: 0x80070032
+ CategoryInfo : InvalidOperation: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature], Exception
+ FullyQualifiedErrorId : DISMAPI_Error__Failed_To_Enable_Updates,Microsoft.Windows.ServerManager.Commands.AddWindowsFeatureCommand
Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
False No Failed {}
VERBOSE: Installation succeeded.
PS C:> $Error[0] | Select *
writeErrorStream : True
PSMessageDetails :
Exception : System.Exception: The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed.
The request is not supported. Error: 0x80070032
TargetObject : @{Vhd=; Credential=; ComputerName=localhost}
CategoryInfo : InvalidOperation: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature], Exception
FullyQualifiedErrorId : DISMAPI_Error__Failed_To_Enable_Updates,Microsoft.Windows.ServerManager.Commands.AddWindowsFeatureCommand
ErrorDetails : The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed.
The request is not supported. Error: 0x80070032
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace :
PipelineIterationInfo : {0, 1, 1, 0}
However, I am able to install some other features successfully.
PS C:> get-windowsfeature Web-Ftp-Server | Install-WindowsFeature -IncludeAllSubFeature -Verbose
VERBOSE: Installation started...
VERBOSE: Continue with installation?
VERBOSE: Prerequisite processing started...
VERBOSE: Prerequisite processing succeeded.
Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
True No Success {FTP Extensibility, FTP Server, FTP Servic...
VERBOSE: Installation succeeded.
…I spoke too soon, I guess, assuming it was only IIS stuff. Just tried and got this error. I’ll keep searching for dism-related hits, but figured I’d update this too!
PS C:> Get-WindowsFeature PowerShellRoot | Install-WindowsFeature -IncludeAllSubFeature -Verbose
VERBOSE: Installation started...
VERBOSE: Continue with installation?
VERBOSE: Prerequisite processing started...
VERBOSE: Prerequisite processing succeeded.
Install-WindowsFeature : The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed.
The request is not supported. Error: 0x80070032
+ CategoryInfo : InvalidOperation: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature], Exception
+ FullyQualifiedErrorId : DISMAPI_Error__Failed_To_Enable_Updates,Microsoft.Windows.ServerManager.Commands.AddWindowsFeatureCommand
Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
False No Failed {}
VERBOSE: Installation succeeded.
Lanwench ** Do not fold, spindle or mutilate. Use only a #2 pencil. Fill in the box completely and erase any stray marks.
-
Edited by
Thursday, September 21, 2017 10:14 PM
Additional examples
Is your CMS solution Sitecore? If so, Sitecore has two options for splitting its config out of the main web.config file.
Sitecore supports using the <sc:include> tag to include a part of the configuration from a seperate file. You just put the <sc:include> tag wherever the configuration would go:
<sitecore database="SqlServer">
<sc.include file="C:Program FilesSitecoreSampleSitesitecore.config"/>
</sitecore>
Then you start the configuration at the parent of <sc:include> (in this case sitecore) in the include file:
<sitecore database="SqlServer">
<sc.variable name="dataFolder" value="/data"/>
<sc.variable name="mediaFolder" value="/upload"/>
<sc.variable name="tempFolder" value="/temp"/>
...
</sitecore>
Sitecore themselves use this in their standard configuration so you can see quite a few examples of this just by looking for in their standard configuration file.
Your other option is to pull out some configuration and put it into the app_config/includes directory. At runtime Sitecore will look for any .config files in there and then add any configuration in the file to the main config.
This configuration file needs to have the full Sitecore configuration structure.
Problem
User launches Controller client. User chooses database, and clicks ‘OK’ button. User receives error message.
Symptom
Log on Controller
Server Error in Application «DEFAULT WEB SITE» Internet Information Services 7.0
Error Summary
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. Detailed Error InformationModule StaticFileModule
Notification ExecuteRequestHandler
Handler StaticFile
Error Code 0x80070032
Requested URL http://servername:80/cognos8/cgi-bin/cognos.cgi?b_action=xts.run&m=portal/close.xts&h_CAM_action=logon
Physical Path C:Program Filescognosc8cgi-bincognos.cgi
Logon Method Anonymous
Logon User Anonymous
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.
<…..>
Cause
There are several potential causes for similar error messages.
- For example, see separate IBM Technote #2006918 different potential causes.
This IBM Technote specifically relates to the scenario where there is a missing ‘cgi-bin’ Mapping Module for virtual directory ‘cgi-bin’ website on Controller application server (or report server).
Environment
Controller/Report server based on Windows 2008.
Diagnosing The Problem
If the end user launches Cognos Connection (http://servername/ibmcognos) then the following message appears:
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.
Resolving The Problem
Create ‘cgi-bin‘ Mapping Module for virtual directory ‘cgi-bin’ website on Controller application server (or report server).
- Afterwards, check the «web.config» file.
Steps:
- Logon to Controller application server (or BI report server) as a Windows administrator
- Launch IIS Manager
- In the tree control in the left pane expand (machine name) > Web Sites > Default Web Site
- Locate and select/highlight the cgi-bin virtual directory
- Double-click on ‘Handler Mappings’
- Click on ‘Add Module Mapping’
- Enter the values exactly as appear below (*.cgi, CgiModule, cgi-bin):
8. Click OK.
NOTE: By default handlers defined in IIS 7.0 for either CGI or ISAPI modules do not process the full path information in a URI.
=> Therefore (see Technote 1390241) on Windows 2008 you must also perform the following:
- Using Windows Explorer, open the cgi-bin folder (TIP: By default, for Controller 10 on 32-bit Windows this is: C:Program Filesibmcognosc10cgi-bin)
- Launch NOTEPAD.EXE and edit the file ‘web.config’:
- Add the text allowPathInfo=»true» after the word “unspecified”
TIP: The file will now look similar to:
For most servers, the above is enough to solve the problem. However, in some environments the file contains the phrase types=»CgiModule» instead of modules=»CgiModule». In this case, you will need to change the file to say: modules=»CgiModule»
Related Information
[{«Product»:{«code»:»SS9S6B»,»label»:»IBM Cognos Controller»},»Business Unit»:{«code»:»BU059″,»label»:»IBM Software w/o TPS»},»Component»:»Controller»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»10.2.0;10.1.1;10.1;8.5.1″,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]
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:WindowsMicrosoft.NETFramework64v4…
Обычно после ее выполнения все необходимые компоненты в 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
Если Вам понравилась статья, пожалуйста, поставьте лайк, сделайте репост или оставьте комментарий. Если у Вас есть какие-либо замечания, также пишите комментарии.
Sometimes, ColdFusion tends to be a real troublemaker in connection with IIS. The IIS is also not helping – the error messages are not always meaningful.
The ultimate solution to various problems is to recreate the IIS-ColdFusion connector. I described this topic briefly in HTTP Status 403 – Forbidden after ColdFusion upgrade on IIS and also I mentioned it in 404 on ColdFusion CFM files while default document is still loading.
The thing is that this is not always enough. Also, there are servers or situations when you are not allowed to remove or create an IIS-ColdFusion connector. In such a case, here is my checklist of things to do.
First things first – permissions
The ColdFusion instance is running over the Tomcat server which is called from IIS as ISAPI Module (or ISAPI Filter). I know, there are many strange statements in the previous sentence. The main thing is that each element of the chain has to be able to access the directory and files where your site is located.
The easiest way to give proper permissions is to open Properties of the folder where the site is located and give all permissions to the IIS_IUSRS group. This group contains all modules called by IIS, so it should allow IIS itself, Tomcat, and ColdFusion to gain access to the files of your website. As you can see on the screenshot below, from the directory permissions I selected the Security tab, clicked on the Edit button below the Grou or user names list, and in the new window I added IIS_IUSRS as the new user with all possible privileges. Full control is not mandatory and on production servers, it is better to keep it off.
Default document
The next thing to check is the Default Document. Click on your site in IIS and find the Default Document icon on the list.
Once there, check if there are your desired default documents on the list. For ColdFusion it is good to have at least “index.cfm” and “default.cfm” there. If they are not listed, you can click “Add” on the Actions list on the right side of the screen.
Handler mappings
When IIS is loading your default document but is not able to handle it properly, it displays a 404.3 error (because it is not able to find a proper handler). It is often connected with the “Error Code: 0x80070032” which doesn’t tell us much about what happened. Here is an example error screen:
The “Error Code: 0x80070032” is caused by the missing cfc and (or) cfm handler. IIS simply doesn’t know what to do with these files. How to serve them. Let’s check if they are in place. On your website in IIS, find and click on the Handler Mappings icon:
It should contain on the list the CFM and CFC handlers:
If they are not present, we should add them. The most common way is by executing the connector creation tool, but let’s assume that we are not able to do this. I assume that you have at least one working ColdFusion website in your IIS. Without this, you have to use the connector creation tool in order to generate the first connector between IIS and ColdFusion.
As the first step here, go to your working ColdFusion website Handler Mappings, click on cfcHandler and copy the contents of the Executable field. We will use it in our manually created handler on the site that is not working. In order to do this, go back to your not working site, click on the Handler Mappings and click on the “Add Script Map” on the Actions panel:
Now you can fill the window using “*.cfc” in the Request path, the value you copied in the Executable field, and “cfcHandler” in the Name field.
Now you should click on Request Restrictions and change Mappings to “File or folder”.
When you click on the “OK” button, such a message will be displayed and you should click “Yes”:
There is a possibility that IIS will give you one more popup saying that the file is in use. Close this popup and click “OK” on the new handler again – for as long as it needs. Sometimes it can take 3-5 times to get to the handler on busy servers – the destination executable is simply used by the other IIS process.
ISAPI filter – error code 0x80004005
Once you have your handlers in place, you may see the IIS error 500 followed by the Error Code 0x80004005. Something like this:
This means that IIS was trying to call the executable, but there was an error calling it. In most cases, it is related to the missing ISAPI Filter of ColdFusion. Go to your IIS website again and click on the ISAPI Filters icon:
Normally, you should see the ColdFusion connector executable, like the one you added in Handler Mappings – something like this:
Once again, if this is missing, you should go to the site that is working on the same server, take a look at the ISAPI Filters of this site and copy the Executable. Please note that this is the same we are using in Handler Mappins, so you can use it again. In order to add the ISAPI Filter, go back to your “not working” site ISAPI Filters, click the “Add” action in the Actions menu on the right. Fill the form with the Filter name of ColdFusion and the Executable you used for your Handler Mappings:
Right now we are almost there. There is still one more step though…
Jakarta ISAPI redirect – Error code 0x80070002
The site can work for most of the cases, but from time to time you receive the Error Code 0x80070002? Something like this:
This means that there are virtual directories missing. Once again we will have to create them manually. Normally, the connector configuration tool is creating them for you, but in this case, we will create them manually. There are two of them – CFIDE and jakarta:
In order to add them manually, right-click on the Globe icon of your not working IIS website, and from the list select “Add Virtual Directory”
You will have to create each of them separately. Here are the screenshots of the filled forms. Please note one thing: you should change the ColdFusion installation path to your own! The first one is CFIDE:
The jakarta virtual directory is pointing to the connector location (take a look at your Handler Mappings and use the same directory):
Conclusion
The above are the most common steps to perform in order to fix typical ColdFusion issues on IIS. They are not covering all possibilities, but the most common ones. I know that the solutions above are not described in-depth, but I wanted this post to be short, but useful. Feel free to add your comments below.
1.
"/" Ошибка сервера приложений.
Тип «System.ServiceModel.Activation.HttpModule» не может быть загружен из сборки «System.ServiceModel, Version = 3.0.0.0, Culture = нейтральный, PublicKeyToken = b77a5c561934e089».
Объяснение: Во время выполнения текущего веб-запроса возникло необработанное исключение. Пожалуйста, проверьте трассировку стека для получения подробной информации об ошибке и источнике ошибки в коде.
Сведения об исключении: System.TypeLoadException: не удалось загрузить тип «System.ServiceModel.Activation.HttpModule» из сборки «System.ServiceModel, Version = 3.0.0.0, культура = нейтральная, PublicKeyToken = b77a5c561934e089».
Ошибка источника:
Необработанное исключение было создано во время выполнения текущего веб-запроса. Для определения причины и местоположения исключения можно использовать следующую информацию трассировки стека исключений.
Трассировки стека:
[TypeLoadException: тип «System.ServiceModel.Activation.HttpModule» не может быть загружен из сборки «System.ServiceModel, Version = 3.0.0.0, Culture = нейтральный, PublicKeyToken = b77a5c561934e089». ]
System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type) +0
System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName) +95
System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +64
System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +59
System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase) +49
[ConfigurationErrorsException: не удалось загрузить тип «System.ServiceModel.Activation.HttpModule» из сборки «System.ServiceModel, Version = 3.0.0.0, культура = нейтральная, PublicKeyToken = b77a5c561934e089». ]
System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase) +523
System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, Boolean checkAptcaBit) +29
System.Web.Configuration.Common.ModulesEntry.SecureGetType(String typeName, String propertyName, ConfigurationElement configElement) +60
System.Web.Configuration.Common.ModulesEntry..ctor(String name, String typeName, String propertyName, ConfigurationElement configElement) +68
System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList) +183
System.Web.HttpApplication.GetModuleCollection(IntPtr appContext) +1162
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +139
System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +172
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +418
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +369
[HttpException (0x80004005): не удалось загрузить тип «System.ServiceModel.Activation.HttpModule» из сборки «System.ServiceModel, версия = 3.0.0.0, культура = нейтральная, PublicKeyToken = b77a5c561934e089». ]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +534
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +111
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +718
Информация о версии: версия Microsoft .NET Framework: 4.0.30319; версия ASP.NET: 4.7.2633.0Описание:Во время выполнения текущего веб-запроса возникло необработанное исключение. Пожалуйста, проверьте трассировку стека для получения подробной информации об ошибке и источнике ошибки в коде. Чтобы
Детали исключения:System.TypeLoadException: не удалось загрузить тип «System.ServiceModel.Activation.HttpModule» из сборки «System.ServiceModel, Version = 3.0.0.0, культура = нейтральная, PublicKeyToken = b77a5c561934e089».
Причина ошибки: СогласноОбъяснение MSDN: Если установлено.NET Framework 4, а затем включите HTTP-активацию .NET Framework 3.5 WCF, возникает эта ошибка.
Решение:
Чтобы решить эту проблему, запустите следующую командную строку в командной строке Visual Studio 2010:
aspnet_regiis.exe -i -enable
Или запустите cmd: C: Windows Microsoft.NET Framework v4.0.30319 aspnet_regiis.exe -i -enable
2.
После выполнения этой команды в командной строке появляется сообщение об ошибке:
Microsoft (R) ASP.NET RegIIS версии 4.0.30319.0
Утилита управления для установки и удаления ASP.NET на локальном компьютере.
Авторское право (C) Корпорация Microsoft. все права защищены.
Начните установку ASP.NET (4.0.30319.0).
Эта версия операционной системы не поддерживает эту опцию. Для установки / удаления ASP.NET 4.5, включая IIS8, администратор должен использовать диалоговое окно «Включение или отключение компонентов Windows», средство управления «Диспетчер серверов» или средство командной строки DISM.exe. Для получения дополнительных сведений см. Http://go.microsoft.com/fwlink/?LinkID=216771.
ASP.NET (4.0.30319.0) установлен.Анализ причин: Моя операционная система 64-разрядная, а пул приложений на веб-сайте — «DefaultAppPool». Его версия .NET CLR — v4.0, и интегрирован режим управляемого конвейера. Понятно, что для режима конвейера хостинга 64-разрядной операционной системы следует выбрать классический режим.
Решение. Задайте для пула приложений веб-сайта значение «.NET v4.5 Classic» в IIS. Его версия .NET CLR — v4.0, а управляемый конвейерный режим — классический. Затем установите для параметра «Включить 32-разрядное приложение» значение «Истина» в дополнительных настройках этого пула приложений и сохраните его. (Согласно этой идее, можно установить классический режим конвейера хостинга DefaultAppPool, но мой принцип — как можно меньше менять.)
3.
Ошибка HTTP 500.24-Внутренняя ошибка сервера
Обнаружены параметры ASP.NET, неприменимые в режиме интегрированного управляемого конвейера.
Наиболее вероятная причина:
system.web/[email protected] имеет значение true.
Что вы можете попробовать:
Если приложение поддерживает это, отключите эмуляцию клиента.
Если вы уверены, что эту ошибку можно игнорировать, вы можете отключить ее, установив для system.webServer/[email protected] значение false.
Используйте классический режим .NET для перемещения этого приложения в пул приложений, например% SystemRoot% system32 inetsrv appcmd set app "Default Web Site /" / applicationPool: "Classic .NET AppPool"
(Вы можете установить "Classic .NET AppPool" на имя других пулов приложений, работающих в классическом режиме управляемого конвейера)
Подробная информация об ошибке:
Модуль ConfigurationValidationModule
Уведомить BeginRequest
Обработчик ExtensionlessUrlHandler-Integrated-4.0
Код ошибки 0x80070032
Запрошенный URL http: // localhost: 81 /
Физический путь E: Website IIS school160216
Способ входа в систему не определен
Имя пользователя еще не определено
Детали:
Если вы не уверены или не можете использовать первые два варианта, предпочтительным подходом будет переключение этого приложения в классический режим.
проверьте подробную информацию "Если возникла эта проблема, просто откройте каталог
Второй — добавить разрешения пользователю, подключающемуся к IIS.
Откройте диспетчер IIS, выберите пул приложений (пул приложений, который вы выбрали при создании веб-сайта), щелкните «Установить параметры пула приложений по умолчанию» справа, а затем измените значение «Включить 32-разрядное приложение» на «Истина» и режим управляемого конвейера. к классике
4.Ошибка HTTP 404.3 (запрошенная страница не может быть предоставлена из-за проблем с конфигурацией расширения)
Эта причина обычно не связана с расширенной конфигурацией, но установка .NET FrameWork на компьютер не завершена.
В панели управления включите или выключите функции Windows, информационные службы Интернета, службы World Wide Web, функции разработки приложений, проверьте ASP.NET 3.5, ASP.NET 4.5, серверные включения и другие функциональные параметры, и тогда эта проблема может быть решенным.
5..Netframework4.0 не устанавливается:
Операционная система win10 поставляется с .net4.6, и .net имеет обратную совместимость., Итак, если win10 устанавливает .net4.6, тогда он должен поддерживать опубликованный веб-сайт. Windows + X + P открыть панель управления и найти, чтобы включить или отключить функцию Windows, проверьте и обнаружите, что установлен .net4.6. Как показано ниже: 
Я начал устанавливать Framework4.0, и результат показал, что эта система не поддерживает эту версию (я чувствую себя напряженно, нет, мне нужно установить систему после установки системы!), Посоветовавшись с Великим Богом и Baidu, я наконец нашел решение: я обнаружил, что необходимость установки Asp.net указана в красном поле на следующем рисунке.
СОВЕТЫ: Если вышеупомянутое решение по-прежнему не помогает решить вашу проблему, возможно, будет быстрее переустановить систему.
Кроме того, когда я устанавливал IIS утром, он всегда показывал, что сценарий не был проанализирован или отображение MIME было неправильным. Это может быть связано с установкой сначала .net, а затем IIS. Я надеюсь, что каждый запомнит этот урок. Я мечтал об этом сегодня. Однажды утром и однажды ночью
Я считаю, что блог по установке IIS — это здорово, а ниже приводится полное руководство по установке IIS на win10.
Нажмите, чтобы открыть ссылку
Конфигурация iis под win10 аналогична конфигурации под win7.
1. Щелкните правой кнопкой мыши, чтобы запустить, откройте панель управления, войдите в программу удаления и отметьте пункты, показанные на рисунке ниже, для установки iis.
2. После перезапуска найдите iis и введите конфигурацию iis. Щелкните веб-сайт, щелкните правой кнопкой мыши, чтобы создать новый веб-сайт, и введите имя веб-сайта.
Вот и ключ, пул приложений должен быть изменен на версию проекта, написанную им самим. (Например, .net v4.5 classic)
Физический путь установлен на уровень index.aspx (не слишком высокий, иначе его нельзя будет просмотреть)
IP-адрес может быть установлен как внутренний сетевой адрес, внешний сетевой адрес или нет.
На данный момент существует проблема с настройкой теста.Мы нажимаем «Подключить как», затем действуем, как показано на рисунке ниже, добавляя имя пользователя и пароль для своего компьютера, а затем проверяем настройки теста, они верны.
3. Включите аутентификацию.
4. Запустите соответствующую службу в пуле приложений, как показано ниже:
В некоторой информации говорится, что вам необходимо изменить расширенные настройки классической версии .NET v4.5, показанной выше. Измените идентификатор пула приложений на localSystem или NetworkService. Но я посмотрел, и ничего страшного не менять.
5. Добавьте документ по умолчанию.
6. Откройте браузер и введите localhost: 42 для доступа. Или щелкните, чтобы открыть div в правой части страницы iis. Если это порт 80, просто введите localhost.
Справка:MSDN
Справка:Используйте win10 с IIS для публикации веб-сайта ASP.NET