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 ...Configuration error during install...Configuration error during install...
Previous
 
Next
New Post
3/2/2006 8:18 AM
 
finn christensen

Joined: 5/28/2004
Posts: 1

Hey all,

I'm installing dnn4 on w2k3 server, iis 6.0. On my testenvironment this is functioning perfect, but when I install on my production server I keek getting the same configuration error:

Server Error in '/DotNetNuke4' Application.: Section or group name 'data' is already defined. Updates to this may only occur at the configuration level where it is defined.

Line 4:      <sectionGroup name="dotnetnuke">
Line 5:        <!-- the requirePermission attribute will cause a syntax warning - please ignore - it is required for Medium Trust support-->
Line 6:        <section name="data" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>
Line 7:        <section name="logging" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>
Line 8:        <section name="scheduling" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>

I have tried almost everything. Does anybody have an idea about what this means!

Any help is apriciated. Thanks in advance.

 

Finn.
 
New Post
3/16/2006 1:48 AM
 
Jeff Petrie


Joined: 7/6/2004
Posts: 17

Same thing.  Making me crazy!

Seems to have something to do with multiple DNN sites on the same box.  I'm running DNN 2 and DNN 4.  I have to manually cut over the content.

I have separate application pools and the ASP.NET 1 for the old stuff and ASP.NET 2 on the new site.

I even bought an IIS 6.0 book.  How's that for desperation.

Several others are getting this too.  Help!

Jeff

Trusmart Technologies Corp.
 
New Post
4/3/2006 4:19 PM
 
Jeff Petrie


Joined: 7/6/2004
Posts: 17

I got this to go away.  My guess is you are using a subfolder on the production server and the root home directory on the "Default Web Site" is pointing somewhere else.  I have a DNN 2.X and a DNN 4.02 and if I point the root home directory at either site it breaks the other one(just like what you have).  If I set the root home directory to C:\inetpub\wwwroot and have virtual directories to both sites they both work.  This does not help me but at least I understand and I can make it go away.  I also don't understand why it does that and it seems like either DNN or IIS6 is misbehaving...but what do I know?

Good Luck...Jeff

Trusmart Technologies Corp.
 
New Post
4/12/2006 4:56 PM
 
Jeff Petrie


Joined: 7/6/2004
Posts: 17

I got this one.  Any subfolder webs (virtual directories) under the Default Web site may get this. The different web sites are fighting over the web.config file.  If you create a separate Application Pool for each of the subfolders and another different Application Pool for the main Default Web site it will fix this.  This will only work with IIS 6.0 because IIS 5.0 does not really have application pools.  I like to make the application pool and the web subfolder (virtual directory) the same name.

For the record: In IIS Services Manager right-click on Application Pools/ Select "New"/Application Pool. Type in the new name (I use the default for new pools) and Ok. Then go into the properties of the Virtual Directory and on the Virtual Directory tab you will see the Application Pool drop-down at the bottom. Select the new Application pool you created.

I also created another Application Pool for the Default Web Site (overkill because there already is one) but be carefull when you make changes to the Default Web site properties because it may try to push some of the settings down to your virtual directories. Good idea to check everything again after you make changes to the Default Web Site.

Not only did I make this go away, but I actually understand what it was doing now.

Good Luck...Jeff

Ok...Hold it...I was wrong.  I just checked it again and it's still broken.  I guess the moral of the story is you can't point the Default Web site at either of the two virtual directories.  If you do, you will get this config error on the other site.  If you point the Default Web Site at the standard C:\Inetpub\wwwroot (at nothing) both the virtual directories will work.  I give up.  It would appear Application pooling does not work on the Default Web Site.  Hmmmmmm.

Trusmart Technologies Corp.
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Configuration error during install...Configuration error during install...


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