This project has moved and is read-only. For the latest updates, please go here.


HTTP Error 500.19 on Install


I installed SenseNet 6.0.4 Community Edition using the IIS Manager package installer. I created the website for the SenseNet installation using IIS Manager and using SQL 2008 SQL Server. The package installed without an error. When I attempted to launch the website I get 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."
Additional Information:
Error Code 0x80070032
Config Error The configuration section 'system.web.extensions' cannot be read because it is missing a section declaration

Can you please assist?
Thank you


raymueller wrote Jun 27, 2011 at 2:36 AM

Discovered the error. When I created the website, the application pool settings was not set to SenseNet (.NET 4.0). Changing the Application Pool to SenseNet allowed the site to launch (sort of). Here is the URL that helped (

How I am getting the error "System.InvalidOperationException: There is no any backup file." I am certain that it is an error on my part.


dobsonl wrote Jul 6, 2011 at 8:46 AM

Hi, thank you for the report. About the "no backup file" message: you might want to try to delete the LuceneIndex and LuceneIndex_backup folders from the web folder and execute the IndexPopulator.exe in the bin folder (make sure the site is stopped while you are doing it). This will create a new index for the application and should fix the above issue. If it does not help, try to reinstall Sense/Net.
Levi Dobson

wrote Jul 6, 2011 at 2:38 PM

wrote Mar 28, 2012 at 10:18 PM

wrote Feb 22, 2013 at 12:25 AM

wrote May 16, 2013 at 11:54 AM

yongmei wrote Oct 9, 2013 at 7:39 AM

Hello ray, the url you added can not open any more. I got the same problem, but I can not solve that. could you please help with some more details? thank you! yongmei

raymueller wrote Oct 9, 2013 at 12:36 PM

I wish that I can fully remember the solution however the root of the problem was around permissions and the application pool. Here are a couple of sites that will help and

I wish that I could remember more however I have had this issue a few times with different sites. This is a IIS configuration centric issue.