Web Application Problems web config errors HTTP 500 19 with IIS7 5 and ASP NET v2

Question

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     Here s the error in full   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     The machine is running Windows Server 2008 R2  We re developing our Web Application using Visual Studio 2008    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      Does anyone know where I might find further information about the error  Nothing is showing in EventViewer  either     Not sure what else would be helpful to mention     Assistance is greatly appreciated  Thanks   UPDATES  - POSTED WEB CONFIG BELOW  Ok  since I posted the original question above  I ve tracked down the precise lines in the web config that were causing the error   Here are the lines  they appear between  lt System webServer gt  tags           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    Note  If I delete the lines between the  lt httpHandlers gt  I STILL get the error  I literally have to delete  lt httpHandlers gt   and the lines inbetween  to stop getting the above error   Once I ve done this I get a new 500 19 error  however  Thankfully  this time IIS actually tells me which bit of the web config is causing a problem          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    Looking at these lines it s clear the problem has migrated further within the same  lt system webServer gt  tag to the  lt handlers gt  tag   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 ASP NET error        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    Obviously I think these new errors have just arisen from me deleting the  lt httpHandlers gt  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     Do I need to install something to IIS to make it work with them   Thanks again for any help   WEB CONFIG  Here s the troublesome bits of our web Config    I hope this helps someone find our problem    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

User · Answer

Had the same problem as above  same error code etc   Setting up a local website on Windows 8   After much searching it was found that we were missing URL rewrite   After downloading it everything was fine

User · Answer

I had the same error  I had an IIS site with  net framework version 2 0  but my app needed 4 0  I changed the version and it worked   Posting just as a reminder if someone might have the same issue

User · Answer

If you are deploying asp net core application you also must install  net core hosting bundle  https   docs microsoft com en-us aspnet core host-and-deploy iis index view aspnetcore-3 0 install-the-net-core-hosting-bundle

User · Answer

I had exact same error message with IIS10 and Windows 10  I tried everything listed here  and other internet pages as well  but it did not fixed it  What solved the issue was to install  NET Core Hosting a second time  I choose  quot Repair quot  button   I m 100  confident this is what fixed it because I had to deploy the same website to other laptops as well  different brands but all Windows 10   The same error message  500 19  occurred and reinstalling bundle fixed it again

User · Answer

Aha  I beat this problem  My god  it was a beast for someone like me with limited IIS experience  I really thought I was going to be spending all weekend fixing it   Here s the solution for anyone else who ever comes this evil problem   First thing to be aware of  If you re hoping this is your solution  make sure that you have the same Error Code  0x8007000d  and Config Source  -1  0    If not  this isn t your solution   Next thing to be aware of  AJAX is not properly installed in your web config   Fix that by following this guide  http   www asp net AJAX documentation live ConfiguringASPNETAJAX aspx  Then  install the AJAX 1 0 extensions on your production server  from this link        http   www asp net ajax downloads archive    Update  Microsoft seems to have removed the above page        That s it

User · Answer

The below config was the cause of my issue        lt rewrite gt         lt rules gt           lt clear   gt           lt rule name  Redirect to HTTPS  stopProcessing  true  gt             lt match url          gt             lt conditions gt               lt add input   HTTP HOST   pattern     spvitals  com     gt               lt add input   HTTPS   pattern  off  ignoreCase  true    gt             lt  conditions gt             lt action type  Redirect  url  https    HTTP HOST  REQUEST URI   redirectType  Permanent  appendQueryString  false    gt           lt  rule gt         lt  rules gt       lt  rewrite gt    Note  I removed this section for local testing  as it works fine in Azure

User · Answer

Same issue on Server 2016  IIS 10  500 19 error   I installed the redirect module and it worked   I do not know why this was not included by default   https   www iis net downloads microsoft url-rewrite additionalDownloads  To be clear it looks like the web config from IIS 7 will work  or is designed to work  but the lack of this module gives the really odd and unhelpful error   Googling takes you to a Microsoft page which insists that your site is corrupted or your web config is corrupted   Neither seems to be the case   That unhelpful page is here   https   support microsoft com en-us kb 942055

User · Answer

To sum up based on answers here and elsewhere    Check the  NET version of the app pool  e g  2 0 vs 4 0  Check that all IIS referenced modules are installed   In this case it was the AJAX extensions  probably not the case these days   but URL Rewrite is a common one

User · Answer

I had these exact symptoms and my issue was similar to Peter s   Was setting up an existing project on a new server   My project referenced the IIS7 URL Rewriting module  but that hadn t been installed yet on the new server   Installing it fixed my issue   You can use the Microsoft Web Platform Installer to install it  Execute it  select Products  in the left menu select Server and find URL Rewrite in the list and install it   Or you can download it here

User · Answer

This error is related to web config file  When web config is not proper or using some features which is not available in IIS  then this issue will come  In my case  I forgot to install URLRewrite module and was referencing it in web config  It took some time to find the root cause  I started removing sections one by one and checked  only then i was able to find out the actual issue

User · Answer

Comment the following lines in the web config file    lt modules gt       lt  -- lt add name  ScriptModule  preCondition  integratedMode  type  System Web Handlers ScriptModule  System Web Extensions  Version 1 0 61025 0  Culture neutral  PublicKeyToken 31bf3856ad364e35   gt -- gt   lt  modules gt    lt handlers gt       lt remove name  WebServiceHandlerFactory-ISAPI-2 0   gt       lt  -- lt add name  ScriptHandlerFactory  verb     path    asmx  preCondition  integratedMode  type  System Web Script Services ScriptHandlerFactory  System Web Extensions  Version 1 0 61025 0  Culture neutral  PublicKeyToken 31bf3856ad364e35   gt       lt add name  ScriptResource  verb  GET  path  ScriptResource axd  type  System Web Handlers ScriptResourceHandler  System Web Extensions  Version 1 0 61025 0  Culture neutral  PublicKeyToken 31bf3856ad364e35   gt -- gt   lt  handlers gt    This will work

User · Answer

I had the same issue in Windows 7   The solution was to go to basic settings   connect as   specific user - and log in as a user  instead of the default  pass-through   This fixed the issue for me

User · Answer

Make sure all of your IIS features are properly enabled     Open Windows Features  Turn Windows features on or off    Scroll down to Internet Information Services Open the World Wide Web plus box drop down Open the Application Development Features plus box drop down Manually check all of the subsequent check boxes  then click ok

User · Answer

I just add an answear because I spent hours trying to solve the same symptoms  but different issue    A possible cause is a x86 dll in a 64 bits app pool  the solution is to enable 32 bits apps in the application pool settings

User · Answer

My IIS 7 5 does not understand  tag in web config In VS 2010 it is underline that tag also  Check your config file accurate to find all underlined tags  I put it in the comment  and error goes away

User · Answer

Similar to the top answer  we were getting this incredibly unhelpful exception because of a missing IIS CORS module  It was the exact same error with Error Code  0x8007000d  and Config Source  -1  0    but installing the URL Rewriting module didn t fix it    We had recently updated the web config to enable CORS for some developers that needed it  but did not expect it would be required for all developers to install the IIS CORS module  Unfortunately it looks like it is required    To fix it  install the IIS CORS module from here

User · Answer

This lovely detailed error is still present in 2019  I just want to add that if your web config is valid and accessible it most likely is a dependency issue   As mentioned by the OP it was a AJAX module  and as by others commonly the Rewrite module  Just keep your eyes open in your web config what modules and libraries your tags are referencing to since the error code 0x8007000d can be about ANY dependency   In my case I didn t realize the AspNetCore bundle was missing and had to be installed  So happy I found this post

User · Answer

Windows 7  Try this   run cmd as Admin   Unistall all iis   start  w pkgmgr exe  uu IIS-WebServerRole WAS-WindowsActivationService   Reinstall iis and normaly it s work  Alain

User · Answer

I got this error by putting the  lt customErrors gt  tag inside of  lt system webServer gt  instead of  lt system web gt  where it belongs   There was a little squiggle under the  lt customErrors gt  tag but I didn t notice it right away

User · Answer

In my case  there was something wrong with the  NET Core Windows Hosting Bundle installation   I had that installed and had restarted IIS using   net stop was  y  and  net start w3svc   after installation  but I would get that 500 19 error with Error Code 0x8007000d and Config Source -1  0    I managed to resolve the issue by repairing the  NET Core Windows Hosting Bundle installation and restarting IIS using the commands I mentioned above   Hope this helps someone

User · Answer

For me  re-registering asp net for iis did the trick  Hopefully that helps someone else   aspnet regiis exe -i

User · Answer

After battling with this for a day on a new machine I came across the following links  I was missing the rewrite modules  This fixed everything   http   forums iis net t 1176834 aspx  http   learn iis net page aspx 460 using-the-url-rewrite-module

User · Answer

Another way of getting 500 19 errot for no apparent reason is - missing directories and or broken permissions on them   In case of this question  I believe the question asks about full IIS version  I assume this because of this line   Config File             E  wwwroot web config   IIS installer usually creates the wwwroot for you and that s the default root folder for all websites and mount point for virtual directories  It always exists  so no problem  you usually don t care much about that   Since web config files are hierarchical  you can put there a master web config file and have some root settings there  and all sites will inherit it  IIS checks if that file exists and tries to load it   However  first fun part   This directory will exists if you have IIS properly installed  If it does not exist  you will get 500-class error  However  if you play with file directory permissions  especially  advanced  ones  you can actually accidentally deny IIS service account from scanning reading the contents of this directory  If IIS is unable to check if that wwwroot web config exists  or if it exists and IIS is not able to open amp read it - bam - 500-class error   However  for full IIS it is very unlikely  Developers Admins working with full IIS are usually reluctant regarding playing with wwwroot so it usually stays properly configured   However  on IIS Express    Usually  IIS Express  just works   Often  developers using IIS Express often are not aware how much internally it resembles the real IIS   You can easily stumble upon the fact that IIS Express has its own applicationHost config file and VS creates and manages it for you  correctly  to some extent  and that sort of an eye-opener telling you that it s not that simple and point-and-click as it seems at first   Aside from that config file  VisualStudio also creates an empty directory structure under your Documents folder  If I remember correctly  IIS Express considers these folders to be the root directories of your website s  upon which virtual directories with your code are mounted   Later  just like IIS  when IIS Express starts up  it expects these folders to exist and checks for root web config files there  The site web config files  Almost always  these web config files are missing - and that s OK because you don t want them - you have your   application web config   they are placed with rest of the content in a virtual directories   Now  the second fun part is  IIS Express expects that empty directories  They can be empty  but they need to exist  If they don t exist - you will get a 500-class error telling  you that  web config  file at that path cannot be accessed   The first time I bumped into this problem was when I was clearing my hard drive  I found that  documents websites  folder  full of trash  I recognized several year-old projects I no longer work on  all empty  not a single file  so I deleted it all  A week later - bam - I cannot run debug any of the sites I was working at the moment  Error was 500 19  cannot read config file    So  if you use IIS Express and see 500-class error telling about reading configuration  carefully check the error message and read all paths mentioned  If you see anything like   c  users user documents visual studio 2013 projects WebProject1 WebProject1 web web config c  users zeshan munir documents visual studio 2015 projects WebProject1 WebProject1 web web config c  users zeshan munir documents visual studio 2017 projects WebProject1 WebProject1 web web config etc     Go there exactly where the error indicates  ensure that these folders exist  ensure that IIS worker account can traverse and read them  and if you notice that anything s wrong  maybe it will be that   BTW  In VisualStudio  on ProjectProperties Web there s a button  Create Virtual Directory   It essentially does this very thing  so you may try it first  but IIRC it can also somethimes clear overwrite swap configuration sections in applicationHost config file  so be careful with that button if you have any custom setups there

User · Answer

This may or not be related    I started off with the same error mentioned above  started googling  making changes  getting new errors  endless loop   The change that got me by that error was messing with the Feature Delegation in IIS Manager under the Management section of the server   I m sorry I can t remember which one I changed  but googling might help   That got me past the 1st error into a whole new stream of others  some totally nonsensical    I would get one error when running under a virtual directory  converting it to an application yielded another error  etec etc    What finally solved this series of errors was  IIS manager  Application Pools  DefaultAppPool  Enable 32-Bit applications True  I had started this app on a 32 bit windows xp box  and I am now running it on a 64Bit Windows 7 box   So hopefully this helps someone else

[asp.net] Web Application Problems (web.config errors) HTTP 500.19 with IIS7.5 and ASP.NET v2

Examples related to asp.net

Examples related to iis

Examples related to web-applications

Examples related to web-config

Examples related to iis-7.5