Hello,

I am in the process of updating/upgrading my website that was largely ignored for 18 months (I know, this is horrible). The first thing I did was have my hosting company upgrade me from 6.1.5 to 7.2.1. After a few tweaks, everything seemed to me working at a quick glance.

Then I looked at the modules I was using and started upgrading them. I am using Dr.Nuke's EasyMod version 1.0.6 that I purchased in July 2009. I wanted to upgrade this to 1.0.11 which was released in September 2013. FYI, I am also using their Flex2 skins that I was going to upgrade next. The new version installed successfully. When I tried to access it logged in as a host, I received the attached error message. Below is the text from the message. Any ideas how to fix this?

Server Error in '/' Application.
A potentially dangerous Request.Path value was detected from the client (<).
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: A potentially dangerous Request.Path value was detected from the client (<).


Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): A potentially dangerous Request.Path value was detected from the client (<).]
System.Web.HttpRequest.ValidateInputIfRequiredByConfig() +9560004
System.Web.PipelineStepManager.ValidateHelper(HttpContext context) +53

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18408

P.S. I used DNN Creative extensively when designing my website and just rejoined due to the tremendous help the community provides.

Thanks for the kind words.

You need to get some support from the module developer.

This might also result from a problem discussed in this comment I found:

"The problem is when you have a Dnn page with a name that includes non-ascii characters (such as icelandic, or japanese), and using a module container which includes the ability to show the 'commands' for a module (usually 'edit content' and 'settings') - the code that generates the Urls for the popup window links for those module-specific commands double-encodes the Urls, which ASP.NET throws an exception on.

There are a couple of workarounds:
- use the DNN 6 'manage' or the DNN7 floating module menu to access the module commands. It will help to use a module container that doesn't show the other values - the dnn6 & dnn7 standard containers do not show the module commands, as they rely on the in-built module menu.
- switch off popups for the site."


Perhaps one of those suggestions will help.