Good Day, I´ve same error.. with telerik and coresitemap, with 0 applications running in .net 4

you usually shouldn't touch web.config manually.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Kalle and Ken,

The install failures are being caused by the <location . . . > elements wrapping both the <system.webServer> and <system.web> sections in Kalle's web.config. I had submitted a Gemini issue of show-stopper level regarding the use of <location . . . > elements resulting in not only failure of the Net40.config to be successfully completed by XmlMerge when switching to an ASP.Net 4.0 app pool but also in the upgrade being re-attempted on each start-up with catastrophic growth of both the event log and web.config. Based on some testing I have done, I now believe this same issue may be the cause of many errors with provider/module installs that attempt to modify web.config. I was surprised in reading several forum comments to learn how many people are using a <location . . . > element in their web.config files.

Here's the Gemini issue: http://support.dotnetnuke.com/issue/V...

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner