• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 428
  • Last Modified:

configuration error dotnetnuke

I installed dotnetnuke using ms access and went to localhost/dotnetnuke and cannot get it to work because of the following erreor
Parser Error Message: Unrecognized attribute 'validateRequest'.
Source Error:


Line 48:
Line 49:             <!-- page level options -->
Line 50:             <pages validateRequest="false" enableViewStateMac="true" />
Line 51:
Line 52:       </system.web>
 
can someone please help...i have tried this many times
0
coletteck8
Asked:
coletteck8
  • 7
  • 6
1 Solution
 
ihenryCommented:

That might because you're using ASP.NET 1.0 since validateRequest only available for version 1.1. You can just remove the validateRequest attribute to

<pages enableViewStateMac="true" />

Or try previous version of DotNetNuke.
0
 
coletteck8Author Commented:
if i remove that then i get this error.
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: Failure decoding embedded permission set object.

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: Failure decoding embedded permission set object.]
   System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Boolean isStringized, Evidence assemblySecurity, Boolean throwOnFileNotFound, Assembly locationHint, StackCrawlMark& stackMark) +0
   System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Boolean stringized, Evidence assemblySecurity, StackCrawlMark& stackMark) +300
   System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark) +68
   System.Reflection.Assembly.Load(String assemblyString) +19
   System.Web.UI.CompilationConfiguration.LoadAssemblies(Hashtable original) +200

 
0
 
ihenryCommented:

It doesn't seem because of removing or disabling the validateRequest, instead you should see error message such as "A potentially dangerous Request.Form value was detected..." from HttpRequestValidationException when ASP.NET detects a potentially dangerous input string from the client.

I found this from DotNetNuke 2.0.4 readme.txt file and make sure the security settings is done before running the application.
//--------------
If using Windows 2000 - IIS5
- the {Server}/ASPNET user account must have Read, Write, and Change Control of the root application directory ( this allows the application to create files/folders )
If using Windows 2003 - IIS6
- the {Server}/NetworkService user account must have Read, Write, and Change Control of the root application directory ( this allows the application to create files/folders )
//---------------
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
coletteck8Author Commented:
i did see  that article, i've read everything i can, but still cannot get it to work. I am using XP Pro w/sql server, so if i understand that correctly, then i should give the ASPNET account access to the wwwroot folder?
0
 
coletteck8Author Commented:
by this time, i'm so frustrated with it i could scream, but i have to get this for work.
0
 
ihenryCommented:

What version .NET framework are you running?
0
 
ihenryCommented:

And what version DotNetNuke are you using?
0
 
coletteck8Author Commented:
it's .net 1.0 and DNN 2.1.2
0
 
ihenryCommented:

If you used the original assemblies that came from the downloaded zip file, try to re-compile all the projects.
0
 
coletteck8Author Commented:
i am using vs.net 2002 so i can't even open the dotnetnuke project
0
 
ihenryCommented:

dnn 2.x has some features that only available in .NET Framework 1.1. So the solution either upgrade to .NET Framework 1.1 as well as your vs.net or use dnn 1.x.
0
 
ihenryCommented:

read this article
http://searchvb.techtarget.com/vsnetATEAnswers/0,293820,sid8_gci996684_tax293475,00.html

but I'm not sure if it can help you to solve this problem.
0
 
coletteck8Author Commented:
i did end up installing vs.net 2003 with the .net framework 1.1 and i no longer have the problems i had before. unfortunately, now i can't get the connection string to work, but that's a different question.
thanks for everyone's help.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now