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 ...http://localhost/DotNetNuke Errorhttp://localhost/DotNetNuke Error
Previous
 
Next
New Post
2/8/2011 2:16 PM
 
When I go to http://localhost/DotNetNuke I get the below error.  I tried changing load user to "True" and I also tried changing v4.0 in IIS7 but I am still getting the below error.

The value for the 'compilerVersion' attribute in the provider options must be 'v4.0' or later if you are compiling for version 4.0 or later of the .NET Framework. To compile this Web application for version 3.5 or earlier of the .NET Framework, remove the 'targetFramework' attribute from the <compilation> element of the Web.config file.

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.Configuration.Configurati sException: The value for the 'compilerVersion' attribute in the provider options must be 'v4.0' or later if you are compiling for version 4.0 or later of the .NET Framework. To compile this Web application for version 3.5 or earlier of the .NET Framework, remove the 'targetFramework' attribute from the <compilation> element of the Web.config file.

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:

[Configurati sException: The value for the 'compilerVersion' attribute in the provider options must be 'v4.0' or later if you are compiling for version 4.0 or later of the .NET Framework. To compile this Web application for version 3.5 or earlier of the .NET Framework, remove the 'targetFramework' attribute from the <compilation> element of the Web.config file.] System.Web.Compilation.MultiTargetingUtil.ValidateCompilerVersionFor40AndAbove(String compilerVersion) +323 System.Web.Compilation.MultiTargetingUtil.EnsureFrameworkNamesInitialized() +287 System.Web.Compilation.BuildManager.Initialize() +282 System.Web.Compilation.BuildManager.InitializeBuildManager() +11393383 System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags, PolicyLevel policyLevel, Exception appDomainCreationException) +874 [HttpException (0x80004005): The value for the 'compilerVersion' attribute in the provider options must be 'v4.0' or later if you are compiling for version 4.0 or later of the .NET Framework. To compile this Web application for version 3.5 or earlier of the .NET Framework, remove the 'targetFramework' attribute from the <compilation> element of the Web.config file.] System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +11529072 System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +141 System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +4784373 


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
 
New Post
2/10/2011 9:17 AM
 
please check your web.config is not read-only and that the executing web user has permissions to modify the file - DotNetNuke detects when a site is running .net4.0 and updates the web.config to work corretly i.e. setting compileversion etc.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
2/11/2011 10:08 PM
 
I have no idea how this happened but the folder had a lock symbol on it. I tried many methods to get control or permissions to edit the fodler.
Even with full access tot eh folder I could not edit it.  I just created a new folder and draged the fodler in it.  When I deleted the new folder I was able to
start the project over. 

The great news is I am able to get the wizard open in the browser; however,  I did not set up a database because I assumed I could use the express
edition to do an auto install.  Unfortunately, I do not have the auto install option meaning I do not have an express edition on my system.  What is the best
way to proceed?  Uninstall everything and install me a fresh copy of express edition then restart the project over?  Or do you think installing the express edition
then rerunning the wizard should resolve the issue.  Any advise is great and thanks for your support!
 
New Post
2/12/2011 4:53 AM
 
please follow http://www.dotnetnuke.com/Resources/Blogs/tabid/825/EntryId/2897/Fix-Portal-Permissions.aspx

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/12/2011 3:57 PM
 
I am good to go and thanks for the response.  I reinstalled SQL Express and ran the install wizard with no problems.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...http://localhost/DotNetNuke Errorhttp://localhost/DotNetNuke Error


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