Databases
StackOverflow2013
Postsdbo
POWeb Application Problems (web.config errors) HTTP 500.19 with IIS7.5 and ASP.NET v2
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWeb Application Problems (web.config errors) HTTP 500.19 with IIS7.5 and ASP.NET v2
    primarykey
    data
    text
    <p>This is driving the whole team crazy. There must be some simple mis-configured part of IIS or our Web Server, but every time we try to run out ASP.NET Web Application on IIS 7.5 we get the following error...</p> <p>Here's the error in full:</p> <pre><code>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 Config File \\?\E:\wwwroot\web.config Requested URL http://localhost:80/Default.aspx Physical Path Logon Method Not yet determined Logon User Not yet determined Config Source -1: 0: </code></pre> <p>The machine is running <strong>Windows Server 2008 R2</strong>. We're developing our Web Application using <strong>Visual Studio 2008</strong>. </p> <p>According to Microsoft the code 8007000d means there's a syntax error in our web.config -- except the project builds and runs fine locally. Looking at the web.config in XML Notepad doesn't bring up any syntax errors, either. I'm assuming it must be some sort of poor configuration on my part...?</p> <p>Does anyone know where I might find further information about the error? Nothing is showing in EventViewer, either :(</p> <p>Not sure what else would be helpful to mention...</p> <p>Assistance is greatly appreciated. Thanks!</p> <p><strong>UPDATES! - POSTED WEB.CONFIG BELOW</strong></p> <p>Ok, since I posted the original question above, I've tracked down the precise lines in the <strong>web.config</strong> that were causing the error.</p> <p>Here are the lines (they appear between <code>&lt;System.webServer&gt;</code> tags)...</p> <pre><code> &lt;httpHandlers&gt; &lt;remove verb="*" path="*.asmx"/&gt; &lt;add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56"/&gt; &lt;/httpHandlers&gt; </code></pre> <p>Note: If I delete the lines <em>between</em> the <code>&lt;httpHandlers&gt;</code> I STILL get the error. I literally have to delete <code>&lt;httpHandlers&gt;</code> (and the lines inbetween) to stop getting the above error.</p> <p>Once I've done this I get a <em>new</em> 500.19 error, however. Thankfully, this time IIS actually tells me which bit of the web.config is causing a problem...</p> <pre><code> &lt;handlers&gt; &lt;remove name="WebServiceHandlerFactory-Integrated"/&gt; &lt;add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory,System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56"/&gt; &lt;add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56"/&gt; &lt;add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56"/&gt; &lt;/handlers&gt; </code></pre> <p>Looking at these lines it's clear the problem has migrated further within the same <code>&lt;system.webServer&gt;</code> tag to the <code>&lt;handlers&gt;</code> tag.</p> <p>The new error is also more explicit and specifically complains that it doesn't recognize the attribute "validate" (as seen on the third line above). Removing this attribute then makes it complain that the same line doesn't have the required "name" attribute. Adding this attribute then brings up <strong>ASP.NET</strong> error...</p> <blockquote> <p><em>Could not load file or assembly 'System.web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56' or one of its dependencies. The system cannot find the file specified.</em></p> </blockquote> <p>Obviously I think these new errors have just arisen from me deleting the <strong><code>&lt;httpHandlers&gt;</code></strong> tags in the first place -- they're obviously needed by the application -- so the question remains: Why would these tags kick up an error in IIS in the first place???</p> <p>Do I need to install something to IIS to make it work with them?</p> <p>Thanks again for any help.</p> <p><strong>WEB.CONFIG</strong></p> <p>Here's the troublesome bits of our <strong>web.Config</strong>... I hope this helps someone find our problem!</p> <pre><code>&lt;system.Web&gt; &lt;!-- stuff cut out --&gt; &lt;httpHandlers&gt; &lt;remove verb="*" path="*.asmx"/&gt; &lt;add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56"/&gt; &lt;add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56"/&gt; &lt;add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56" validate="false"/&gt; &lt;/httpHandlers&gt; &lt;httpModules&gt; &lt;add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56"/&gt; &lt;/httpModules&gt; &lt;/system.web&gt; &lt;system.webServer&gt; &lt;validation validateIntegratedModeConfiguration="false"/&gt; &lt;modules&gt; &lt;add name="ScriptModule" preCondition="integratedMode" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56"/&gt; &lt;/modules&gt; &lt;remove verb="*" path="*.asmx"/&gt; &lt;add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56"/&gt; &lt;handlers&gt; &lt;remove name="WebServiceHandlerFactory-Integrated"/&gt; &lt;add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory,System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56"/&gt; &lt;add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56"/&gt; &lt;add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56"/&gt; &lt;/handlers&gt; &lt;/system.webServer&gt; </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChuck Le Butt
    1. USChuck Le Butt
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWeb Application Problems (web.config errors) HTTP 500.19 with IIS7.5 and ASP.NET v2
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWeb Application Problems (web.config errors) HTTP 500.19 with IIS7.5 and ASP.NET v2
      1. USChuck Le Butt
      1. VTFavorite
    3. VO
      singulars
      1. POWeb Application Problems (web.config errors) HTTP 500.19 with IIS7.5 and ASP.NET v2
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you post the web.config?
      singulars
      1. POWeb Application Problems (web.config errors) HTTP 500.19 with IIS7.5 and ASP.NET v2
      1. USJoe Ratzer
    2. CORemove all the comments in the `web.config`. They begin with `<!-- ` and end with `-->`.
      singulars
      1. POWeb Application Problems (web.config errors) HTTP 500.19 with IIS7.5 and ASP.NET v2
      1. USAlex Bagnolini
    3. COwoot. it's something to do with <httpHandlers>
      singulars
      1. POWeb Application Problems (web.config errors) HTTP 500.19 with IIS7.5 and ASP.NET v2
      1. USChuck Le Butt
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload