User564503313 posted
Hi
I’ve been searching through the forums and came across many posts similar to the problem I am experiencing but none of the suggestions have got me any closer to getting this fixed. The following are the errors I get:
Error summary:
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 BeginRequest
Handler Not yet determined
Error Code 0x800700b7
Config Error Cannot add duplicate collection entry of type ‘add’ with unique key attribute ‘name’ set to ‘CommerceContentRedirect’
Config File \\?\C:\inetpub\wwwroot\StarterSite\web.config
Requested URL http://localhost:80/StarterSite
Physical Path C:\inetpub\wwwroot\StarterSite
Logon Method Not yet determined
Logon User Not yet determined
Config source:
462: <handlers>
463: <add name=»CommerceContentRedirect» path=»redir.axd» verb=»*» type=»CommerceComponents.ContentRedirectHandler, CommerceComponents» preCondition=»integratedMode,runtimeVersionv2.0″ />
464: <add name=»CommerceSiteCacheRefresh» path=»SiteCacheRefresh.axd» verb=»*» type=»Microsoft.CommerceServer.Runtime.SiteCacheRefresh, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
» preCondition=»integratedMode,runtimeVersionv2.0″ />
I hope someone can please help, Any help/suggestions is greatly appreciated.
Regards
johana
I was adding the ability to serve SVG & WOFF files to my Azure hosted web application. I found the following instructions:
https://blogs.iis.net/richma/archive/2014/01/07/adding-mime-types-to-your-windows-azure-web-site.aspx
Which I have followed by adding the below text to my Web.config file:
<staticContent>
<mimeMap fileExtension=".json" mimeType="application/json" />
<mimeMap fileExtension=".svg" mimeType="image/svg+xml" />
<mimeMap fileExtension=".woff" mimeType="application/x-font-woff" />
</staticContent>
This works when published to Azure. However, now I get the following error from IIS-Express whenever I attempt to start up the website in Debug mode locally for every resource the website attempts to serve.
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: CustomErrorModule
- Notification SendResponse
- Handler StaticFile
- Error Code 0x800700b7
- Config Error Cannot add duplicate collection entry of type ‘mimeMap’ with unique key attribute ‘fileExtension’ set to ‘.svg’
- Config File snip\web.config
- Requested URL http://snip:14466/resources/img/snip.png
- Physical Path C:*snip*\Resources\img*snip*.png
- Logon Method Anonymous
- Logon User Anonymous
Config Source:
58: <mimeMap fileExtension=".json" mimeType="application/json" /> 59: <mimeMap fileExtension=".svg" mimeType="image/svg+xml" /> 60: <mimeMap fileExtension=".woff" mimeType="application/x-font-woff"/>
It clearly hates my mimeMap for .svg but this works fine out in Azure Websites. Is there something I am missing for locally running these changes to the Web.config?
пятница, 20 апреля 2012 г.
Сокрытое в листве — 0x800700b7
Если после переноса web-сайта под IIS на новый комп он не открывается с ошибкой 0x800700b7 Ошибка конфигурации Определена копия раздела… с указанием куда-то внутрь файла web.config, не надо ничего выкашивать из web.config, нужно просто доустановить ASP.NET (из установщика компонентов windows), зарегистрировать его (aspnet_regiis.exe -i) и проверить, что указанный для сайта пул приложений использует нужную версию .NET Framework.
Подобными сведениями нужно дорожить. ©
Комментариев нет:
Отправить комментарий
Skip to content
This post has been republished via RSS; it originally appeared at: IIS Support Blog articles.
If IIS Manager doesn’t open because of the error below, it may cause delays in maintenance and migrations.
The error message:
Creating an instance of the COM component with CLSID from the IClassFactory failed due to the following error: 800700b7
Solution
This issue may happen after an in-place upgrade, migration, Windows updates or any other operation that works with system libraries. There is likely a corrupted or missing system file.
There are a couple things to check if you run into this issue:
- Check Event Viewer to find out information about the root cause
- Collect Process Monitor trace and look for any failures. Don’t be surprised if everything looks good in the trace because the root cause may hide behind a SUCCESS message. Take another trace from a working server and compare them
If logs and traces don’t provide a lead, here are a few things to try (Test if IIS Manager opens successfully after each step):
- Uninstall IIS Management Tools in Server Manager and install them back
- Check if IIS Admin Service starts in Services window
- Perform iisreset
- Run aspnet_regiis -I
- Check the permissions on this folder: c:\programData\Microsoft\crypto\RSA\machineKeys
Make sure Everyone has Read/Write and Administrators have all permissions - Reinstall .NET Framework
- If nothing works, uninstall IIS and install it back
From application slowness to 500 errors, we use Failed Request Tracing logs to get clues about the root cause of website related issues. However, the tracing itself may be subject of the troubleshooting efforts because of an error like “Cannot add duplicate collection entry of type (0x800700b7)”.
This the error message I saw for one of the applications after I enabled Failed Request Tracing in the IIS server:
Cannot add duplicate collection entry of type ‘add’ with unique key attribute ‘path’ set to ‘*’
Error code: 0x800700b7
Solution for the “Cannot add duplicate collection entry of type (0x800700b7)” error
The error message mentions a duplicate record so the first thing to try is checking the web.config for identical definitions:
- Enable Failed Request Tracing
- Add a rule
- If the issue occurs, check web.config file. Are there two sets of Failed Request Tracing rules even though you added only one?
If there are no duplicate entries, check the tracing module in all application, site, and server levels in IIS Manager. Make sure there are no conflicting rules. Do the same for applicationHost.config file. Make sure tracing for the same site is not enabled more than once.
After making sure there is only one rule, if the issue persists, add the line below into web.config. It will remove all existing rules to prevent duplication (Related forum post).
<remove path="*" />The entire configuration of the Failed Request Tracing rule in the web.config:
<configuration>
<system.webServer>
<tracing>
<traceFailedRequests>
<remove path="*" />
<add path="*">
<traceAreas>
<add provider="ASP" verbosity="Verbose" />
<add provider="ASPNET" areas="Infrastructure,Module,Page,AppServices" verbosity="Verbose" />
<add provider="ISAPI Extension" verbosity="Verbose" />
<add provider="WWW Server" areas="Authentication,Security,Filter,StaticFile,CGI,Compression,Cache,RequestNotifications,Module,FastCGI,WebSocket" verbosity="Verbose" />
</traceAreas>
<failureDefinitions statusCodes="500" />
</add>
</traceFailedRequests>
</tracing>
</system.webServer>
</configuration>A side note: In my case, the environment this issue occurred had two IIS servers pointing to the same web.config (located in a network share). This made it the issue more complicated.
There could be more than one root causes of the 0x800700b7 error. If the issue is still occurring after the config change above, check this post out: Creating an instance of the COM component with CLSID failed (800700b7)