Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...MachineKey Error While Setting UPMachineKey Error While Setting UP
Previous
 
Next
New Post
4/24/2006 3:21 AM
 
Peter Cawdron

Joined: 4/19/2006
Posts: 3
I'm getting....

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: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS.

Source Error: 

Line 56:   </system.codedom>
Line 57:   <system.web>
Line 58:     <machineKey 
Line 59:       validationKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902" 
Line 60:       decryptionKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC"

Source File: C:\Inetpub\DotNetNuke403\website\web.config    Line: 58

But I definately have my Virtual Directory set up as an Application (on the VD properties I can see Application Name, Execute Permissions is Scripts and Executables, Application Protection is Medium). Also, I've ensure that I'm using ASP.NET 2.0 with Dot Net Nuke 4.0.3

Isn't the machinekey supposed to be something from my machine? Where can I find it to insert the correct key value into the web.config file?

Thanks for your help. It is very much appreciated.

Kind regards,
Peter



 
New Post
4/24/2006 7:20 AM
 
Claus Vestergaard

www.zycon.dk
Joined: 2/12/2006
Posts: 1

I have the exact same problem!

Maybe someone can help me/us out!? ;o)

My scenario:

SERVER:

* WIN2003,
* IIS 6.0 with virtual "DotNetNuke" library,
* .NET2.0,
* DNN4.x installed in "C:\DotNetNuke"
* "NETWORK SERVICE" account is set to read+write+modify on the "C:\DotNetNuke"-folder
* I have an "DotNetNuke" database in MS SQL v.8 with the user "NETWORK SERVICE"
* connection-string is corrected 2 places in the "web-config"-file with value="Server=MyServerName;Database=DotNetNuke;trusted_connection=yes;"

Client:

* WInXP Professional,
* .NET2.0,
* VS2005

RESULT:
* http://localhost/dotnetnuke/ = Error 400 The page cannot be found
* http://MyServerName/DotNetNuke/ = Error 403 You are not authorized to view this page
* http://MyServerName/DotNetNuke/Website/ =

------ error START ------
Server Error in '/DotNetNuke' 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: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.

Source Error:


Line 61: </system.codedom>
Line 62: <system.web>
Line 63: <machineKey
Line 64: validationKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902"
Line 65: decryptionKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC"


Source File: C:\DotNetNuke\website\web.config Line: 63
--------- error END --------

What do I do wrong? And should these calls be made from the client or the server? I have tried both!

Extra info:

execute permissons: Scripts only..

Folder-structure:
c:\DotNetNuke
c:\DotNetNuke\library
c:\DotNetNuke\website
c:\DotNetNuke\website\index.aspx
c:\DotNetNuke\website\web.config

Thanx in advance.. ;o)
Martin
 
New Post
4/25/2006 12:33 AM
 
Peter Cawdron

Joined: 4/19/2006
Posts: 3
OK Vester, it doesn't look like anyone else is going to help us so we'll have to help ourselves.

I found another forum posting on Problems installing DNN 4.0.2 (see the reply by ar anand) which got me moving in the right direction. I recommend you tha print out. For me, the only variations were...

1. I cleaned everything out. Deleted all my previous Virtual Directories, SQL databases from other attempts, etc.
2. I had to download Visual Basic 2005 Express Edition (from Microsoft) in order to open the file DotNetNuke.sln
3. Visual Studio coughed up a few errors about not having the Virtual Directory set up for DotNetNuke_2 and said the Solution explorer wasn't available. So I'm not sure what good it did.
4. I set up the Virtual Directory manually but even when I repeated step 3 VS VB still complained. So I ignored the messages and continued on with ar_anand's suggestions
5. Ar_anand says to set up the database in VS VB but it wasn't showing there for me so I opened the same file with Visual Web Developer Express. That choked a bit, throwing up a couple of errors, but I could follow his instructions for setting up the database. Please note, I did NOT have to change any database settings.
6. I could not figure out how to make Win XP grant ASPNET access to the folder so I opened it to all and sundry (probably not a smart move. If anyone has any suggestions on how to limit access to just ASPNET I'm open to hear them, but it worked)
7. On ar_anand's last point, nothing redirected for me, but when I pasted http://localhost/DotNetNuke_2/Install/Install.aspx?mode=Install into my browser WHAM... everything fell into place and DNN is running.

I hope this helps you.

Kind regards,
Peter
 
New Post
4/25/2006 10:58 AM
 
Michael Flanakin


Michael Flanakin's Avatar

michaelflanakin.com
Joined: 4/5/2004
Posts: 994
I believe the machine keys are generated during the install. These are required by the ASP.NET membership beta to provide an additional layer of security when encrypting passwords. This is not stored anywhere on the machine, and if you don't keep the same key values between versions, you won't be able to login to any of your accounts after upgrading. If you need to retrieve an old value, you'll need to get a hold of a backup.

As for the specific error you mentioned before, I can't really help you with that because I've never seen it. The only thing I can think of would be to remove the app and recreate the VD as an application.
Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
4/25/2006 5:29 PM
 
Peter Cawdron

Joined: 4/19/2006
Posts: 3
OK, so this is just some legacy requirement from Beta times and not applicable to the install (other than that now I've inherited a machinekey from someone else -DNN team- I need to keep track of it with future updates.)

DNN is installed now and working beautifully. Now comes the real challenge. Learning to program ASP.NET inside the DNN framework.

Cheers,
Peter
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...MachineKey Error While Setting UPMachineKey Error While Setting UP


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