Hello everyone,

I'm having an interesting issue with my sites and I can't seem to find a solution online.  When I enable client side errors, I would get:

<SNIP>

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. 

Parser Error Message: Unrecognized attribute 'requestValidationMode'. Note that attribute names are case-sensitive.

Source Error: 

</SNIP>

The settings on my site changed somehow (automatically, hosting support employee, I'm not sure) to use ASP.NET 4.0 instead of 2.0 and I think that's what started this issue.  Whenever I delete the requestValidationMode="2.0", everything will run fine for a while, then after a while, it goes down again with the same error and I discover that the attribute had again been added to my web.config.  I was using DNN 5.4, but upgraded to the latest version of 6 thinking it would support .net 4.0 and stop giving me this issue.  Unfortunately even after upgrading I was still getting the error message (it seems random).

I did some searching online and found this on another forum:

"DNN adds the attribute in question when it detects ASP.NET 4.0 (unfortunately we cannot do the reverse as the request fails in ASP.NET before it reaches us."

Does anyone know if there is there any way to prevent DNN from modifying my web.config automatically and adding this attribute?

Thanks,

Kevin

But would write protecting it mess with any other DNN functionality?

Yeah, I am using a hosting provider (webfarm) but I've set my application pool to use 4.0 and it gives me the error with the requestValidationMode attribute.  I thought that it was being set back to 2.0 as well, so I would check randomly (as it was mysteriously changed to 4.0, which is when I starting having this issue) and it was still unchanged.

I would love to raise it with my hosting provider, but their service is somewhat..........sad.  I've had issues with them (very simple issues, like file permission issues) that have taken almost a month to resolve.  This would probably blow them out of the water.  I really need to find a better hosting service.