Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...production site down..production site down..
Previous
 
Next
New Post
11/25/2010 11:23 PM
 

I tried to access my site and got an error. It was the last dnn prior to 5.6 It seemed to be working fine untill today, I have made no changes to the server or the app except to put the app pool in IIS to .net 2 from 4.

After the problem appeared I restored the data base and the the file system through xcopy. with the same results and error.

I also tried commenting out the offending line with  some more obscure (to me) result. so  i put it back and here I am.

This is a critcial enough issue I am considering giving up on this  app for further use....i dont know where it came from or why normal back up processes have not recoverd :

Server Error in '/' Application.

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:

Line 178: --> Line 179: < !-- allow large file uploadsI changed this to try to load app agianst error-- >
Line 180: < httpruntime requestValidationMode="2.0" requestLengthDiskThreshold="8192" maxRequestLength="8192" useFullyQualifiedRedirectUrl="true" / >
Line 181: < httpcookies requireSSL="false" httpOnlyCookies="true" / >

Source File: E:\websites\dnn\web.config    Line: 180


Version Information: Microsoft .NET Framework Version:2.0.50727.4927; ASP.NET Version:2.0.50727.4927

 
New Post
11/25/2010 11:42 PM
 
When you changed the AppPool from ASP.Net 2.0/3.5 to 4.0, a number of changes would have been automatically made to the web.config file. The addition of the requestValidationMode="2.0" attribute to the < httpRuntime > node would have been one of those changes. Apparently, either the modified web.config file was restored or if the site files was restored with the AppPool still set for ASP.Net 4.0, the same web.config changes would have been made again automatically. Since the requestValidationMode attribute is not compatible with ASP.Net 2.0/3.5, you are seeing this error. After confirming that you have switched the AppPool back to 2.0/3.5 you will need to restore the web.config file from the backup made prior to changing the AppPool to 4.0. If you do not have a backup web.config you will manually need to revert the changes made for 4.0. One of them will be to remove the requestValidationMode="2.0" attribute from the < httpRuntime > node. There would have been two other changes made to the < runtime >< assemblyBinding > nodes relating to binding redirects for System.Web.Extensions and System.Web.Extensions.Design assemblies. Changes made for ASP.Net 4.0 should be commented in web.config so should be easy to find.

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
 
New Post
11/25/2010 11:45 PM
 

looking over some of the other posts that seemed  related by the downgrade from .net 4 to .net 2 I tried  removing the offending

attribute 'requestValidationMode'.

I then get this:

Security Exception

Description: The application attempted to perform an operation not allowed by the security policy.  To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.

Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

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:

[SecurityException: Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.] System.RuntimeTypeHandle._GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, Boolean loadTypeFromPartialName) +0 System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) +62 System.RuntimeType.PrivateGetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) +42 System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +77 System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +105 System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase) +64 


Version Information: Microsoft .NET Framework Version:2.0.50727.4927; ASP.NET Version:2.0.50727.4927
 
New Post
11/26/2010 12:54 AM
 
Thanks for your input.

I did a restore again, this time under .net 4, and am able to bring the site up.

I am not sure where to proceed from here.

should I try to get it back to .net 2 ?

should I try to upgrade to 5.6?

I need a stable platform for a good client.

Perhaps it will work as is, but I have to be up and running well in just a few more days.

any Ideas?

Thanks again for the input.

E Hansen
 
New Post
11/26/2010 8:48 AM
 
If the site appears to be running without errors (check Event Viewer to see any errors that are being logged) under DotNetNuke 5.05.01 and ASP.Net 4.0, I would be tempted to leave it as is for now as there is a know issue with the 5.06.00 upgrade/install relating to the URLRewriteModule that is affecting some sites.

On the otherhand, a low-level security vulnerability with DotNetNuke 05.05.01 and prior versions was just announced and was fixed in 5.06.00. Here's the blog post describing that issue: http://www.dotnetnuke.com/Resources/B...

If you do upgrade to 5.06.00, be sure to make a good filesystem and database backup first in case you have to roll back.

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
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...production site down..production site down..


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out