I am getting following error from my hosted site
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information
Module ProtocolSupportModule
Notification SendResponse
Handler ExtensionlessUrlHandler-Integrated-4.0
Error Code 0x800700b7
Config Error Cannot add duplicate collection entry of type 'add' withunique key attribute 'name' set to 'X-UA-Compatible'
Config File \\?\C:\inetpub\wwwroot\abc\web.config
Requested URL http://abc:80/Test
Physical Path C:\inetpub\wwwroot\abc
Logon Method Not yet determined
Logon User Not yet determined
Config Source
54: <customHeaders>
55: <add name="X-UA-Compatible" value="IE=edge" />
56: </customHeaders>
I gave the permission to the IIS_USR also in security and allow the windows authentication. Any idea to fix this
It looks like you may have duplicate key's in your configuration file based on: duplicate collection entry of type 'add' with unique key attribute 'name' set to 'X-UA-Compatible'
Search for "X-UA-Compatible" in your configuration file and make sure there is only one entry with this name.
You may also want to read this article: Click Here
Related
I've installed an IIS server on windows 8 and plublished my first site, this is the error I get. Any help would be appreciated.
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:\inetpub\wwwroot\ContractorScoping\web.config
Requested URL
http://localhost:80/ContractorScoping
Physical Path
C:\inetpub\wwwroot\ContractorScoping
Logon Method
Not yet determined
Logon User
Not yet determined
Config Source:
68: <validation validateIntegratedModeConfiguration="false" />
69: <modules>
70: <remove name="ApplicationInsightsWebTracking" />
Line 69 is the one highlighted in red
Schoolboy error, forgot to install asp.net on the server
This error comes due to missing IIS Packages. I solved the error with doing these steps:
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.
I am trying to run my asp.net mvc website on the IIS. I got the following error:
HTTP Error 500.19 - Internal Server Error The requested page cannot be
accessed because the related configuration data for the page is
invalid.
I use IIS through IIS manager and when I try to configure MIME Types in IIS Manager, I got the following config error:
There was an error while performing this operation. Error: Cannot add
duplicate collection entry of type 'mimeMap' with unique key attribute
'fileExtension' set to '.woff2'.
As a result of my detailed research, this problem occurs on IIS 7.5. How to get rid of this errors and run my web page on IIS?
At first, try to install iis rewrite module to told IIS my custom web.config is not failure or faulty. If it's not fix the problem, I suggest another solution particularly for your problem. Delete your .wolf2 config from your web.config file. For example;
<staticContent>
<mimeMap fileExtension=".woff2" mimeType="application/font-woff2" />
</staticContent>
Delete mimeMap row which has .woff2 file extension from the staticContent. It would fix your problem because this error says that I already have .wolf2 in my config file but you trying to add one more.
I'm a student and I was given a folder Web folder to use as my project. The problem is what they I try to publish my site to the server I get an error:
It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This
error can be caused by a virtual directory not being configured as an
application in IIS.
Meaning that my Web folder was not configured as an application folder, therefore my project cannot be rendered (if I got this right? was reading a bit from the internet).
My question is, is there a way to handle this error without having an access to IIS server configurations? From code side of my project?
Error I get:
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.
Source Error:
Line 29: validate="false" />
Line 30: </httpHandlers>
Line 31: <authentication mode="None" />
Line 32: <compilation targetFramework="4.5">
Line 33: <assemblies>
The answer is no. IIS configuration system relies on such lock down mechanism, which you cannot break.
More information can be found at
http://www.iis.net/learn/manage/managing-your-configuration-settings/understanding-iis-configuration-delegation
Am trying to learn how to use dotnetnuke so am kinda new to it. I installed it correctly and i set up a user in server management studio. So when i try to open my page localhost\mypage i get these errors:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information:
Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x8007000d
Config Error Configuration section not allowed in a <location> tag
Config File \\?\C:\inetpub\wwwroot\ANTONISDB\web.config
Requested URL http://`localhost`:80/dotnetnuke
Physical Path
Logon Method Not yet determined
Logon User Not yet determined
Config Source:
210: </system.web>
211: <runtime>
212: <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
Anyone knows whats wrong with this?
Check to make sure the Application Pool for the virtual directory/application is configured to USE ASP.NET 4.0, DNN won't run with .NET 3.5 anymore (starting with Version 7)
I have Sitecore as site root (which is running ok) and under it I need to have a bunch of asp.net applications running.
So far, created a virtual directory for the child application, turned it into an app. But as soon as I browse the child app it comes with this error message.
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0246: The type or namespace name 'Sitecore' could not be found (are you missing a using directive or an assembly reference?)
Source Error:
Line 3264: </providers>
Line 3265: </roleManager>
Line 3266: <profile defaultProvider="sql" enabled="true" inherits="Sitecore.Security.UserProfile, Sitecore.Kernel">
Line 3267: <providers>
Line 3268: <clear/>
It seems that the child asp.net app is inheriting Sitecore settings which are coming from Sitecore web.config.
Any ideas?
This should be possible. You'll have to author a web.config for that non-Sitecore application in virtual directory, and overwrite the sections under <system.web> and <system.webserver> which reference Sitecore classes. This includes:
httpModules / httpHandlers (for these you should "remove all" and add those of that web app)
security section (put the default ASP.NET provider classes back)
in Sitecore main web.config add the path of this web app to IgnoreUrlPrefixes setting to let Sitecore know it should not handle requests to those
It might be something else, but you should get the general idea.
This answer is similar to Yan, but is different enough for a separate answer. Hope it helps.
Go into IIS and select the Child Application. Select Modules. Remove all the Sitecore related modules that are present. Don't worry, the parent Sitecore app will still retain these modules.
When you do this, you are actually changing the child app web.config, so you will see the elements removed in the web.config file like so.
<remove name="SitecoreConfigWatcher" />
<remove name="SitecoreHttpModule" />
You also may have to clear out some other inherited settings.
<profile enabled="false"><providers><clear/></providers></profile>
<roleManager enabled="false"><providers><clear /></providers></roleManager>