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 ...Install problems on Windows Server 2003 R2Install problems on Windows Server 2003 R2
Previous
 
Next
New Post
11/23/2006 6:06 PM
 
Lee

Joined: 11/21/2006
Posts: 5

I'm trying to install DNN 4.3.6 on a brand new Windows Server 2003 R2 installation that has been fully service packed/updated.  Having got most of it set up I consistently get the following errors, shown below, reported against the web.config file.  The DNN installation is already set up as an application under IIS.

As I haven't been able to find any current information that's relevant I'd really appreciate some help in resolving this.

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: 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 55: 	</system.codedom>
Line 56: 	<system.web>
Line 57: 		<machineKey validationKey="6F92D536C419B2724D4B5FF3B1697878805F67AA" decryptionKey="5F339268BB0985E34A6F89444EF510F7BA78D1A97CF8CCCC" decryption="3DES" validation="SHA1"/>
Line 58: 		<!-- HttpModules for Common Functionality -->
Line 59: 		<httpModules>

Source File: c:\inetpub\wwwroot\dnn_telekomintranet\web.config    Line: 57 



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. (c:\inetpub\wwwroot\dnn_telekomintranet\web.config line 103)

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. (c:\inetpub\wwwroot\dnn_telekomintranet\web.config line 159)

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. (c:\inetpub\wwwroot\dnn_telekomintranet\web.config line 160)

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210

 
New Post
11/23/2006 10:50 PM
 
Lee

Joined: 11/21/2006
Posts: 5

I tried seeing how far I could push things along:

I first of all removed all of the allowDefinition="MachineToApplication" attributes for machineKey, anonymousIdentification, authentication and authorization in the machine.config.

That got me to the next error which was:

Parser Error Message: The element 'codeSubDirectories' cannot be defined below the application level.

Source Error: 

Line 84:          <add directoryName="sub-directory name"/> 
Line 85:       </codeSubDirectories>      -->
Line 86: 			<codeSubDirectories>
Line 87: 				<add directoryName="Reports"/>
Line 88: 				<add directoryName="Survey"/>

So I simply commented out the codeSubDirectories section and it complained about buildProviders (also under the compilation element) so I commented out that as well.

Then I got the following:

Parser Error Message: Could not load file or assembly 'FreeTextBox' or one of its dependencies. The system cannot find the file specified.

Source Error: 

Line 59: 		<httpHandlers>
Line 60: 			<!-- This is for FTB 3.0 support -->
Line 61: 			<add verb="GET" path="FtbWebResource.axd" type="FreeTextBoxControls.AssemblyResourceHandler, FreeTextBox"/>
Line 62: 			<!-- This is for CAPTCHA support -->
Line 63: 			<add verb="*" path="*.captcha.aspx" type="DotNetNuke.UI.WebControls.CaptchaHandler, DotNetNuke"/>

So I commented out the three http handlers one after the other, and then it finally complained about default.aspx

Parser Error Message: Could not load file or assembly 'DotNetNuke' or one of its dependencies. The system cannot find the file specified.

Source Error: 

Line 1:  <%@ Page Language="vb" AutoEventWireup="false" Explicit="True" Inherits="DotNetNuke.Framework.DefaultPage" CodeFile="Default.aspx.vb" %>
Line 2:  <%@ Register TagPrefix="dnn" Namespace="DotNetNuke.Common.Controls" Assembly="DotNetNuke" %>
Line 3:  <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
Line 4:  <html>

At this point I figured I wasn't getting anywhere helpful, so I thought I'd read the install instructions a little more closely.

Following them I renamed the original web.config file and copied release.config to web.config in its place.

That got all the way to the 'buildproviders' issue again.  Restarting the 'commenting out' process at the point yielded exactly the same results.

At this point I'm reasonably certain that it's some tightening up of security on WinServ2003 R2, it's just I can't find any reference to help me open things up appropriately.

So I still need some help.
 
New Post
11/26/2006 6:04 PM
 
Lee

Joined: 11/21/2006
Posts: 5

Actually, after restoring the allowDefinition="MachineToApplication" attributes in the machine.config I was absolutely back to square one.

Can anyone point me in the right direction for this one.
 
New Post
11/26/2006 6:51 PM
 
Lee

Joined: 11/21/2006
Posts: 5

Ok, fixed my own problem.

I had created a web site and pointed it at the folder that I ahd put my install into.
I hadn't realised that there was also a virtual folder underneath the "Default Web Site".

As soon as I had hit the Create Applicaiton button this particular problem went away.

Now onto the next one.
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install problems on Windows Server 2003 R2Install problems on Windows Server 2003 R2


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