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 ...DNN Multiple Installs for Dev on IIS6 (3 + 4)DNN Multiple Installs for Dev on IIS6 (3 + 4)
Previous
 
Next
New Post
7/26/2006 11:36 AM
 
Hey, I've got a Development box which we are going to use to test modules. However, we want access to both versions 3 and 4 of DNN simultaneously.  Is this even possible in IIS? The inheritance of DNN3's web.config (it's under default webpage) mucks up DNN4's attempt to install.  I read that removing the namespaces that conflict can help, but that didn't work for me. I'd share my Error page, but I killed IIS tinkering ;)   But it's basically all the configSections in the first block of the web.config trying to write to data that's already there, and saying "This can only be done on the config level"  (since it's already looked at DNN3's web.config).  Is there at trick to isolate them from each other? Or does .NET 2 just not allow it?
 
New Post
7/26/2006 2:12 PM
 
By the way-

OS: Windows Server 2003

And fixed IIS6.0, the error is:

Server Error in '/DotNetNuke_2' 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: Section or group name 'data' is already defined. Updates to this may only occur at the configuration level where it is defined.

Source Error:

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

Source File: C:\DotNetNuke_2\Website\web.config    Line: 10



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



Is it possible to get around this using AppPools, or putting it as a virtual under a different IP, or a different port? Anything? :P
 
New Post
8/10/2006 9:57 PM
 

Joefish711,

Have you found any workaround of the error?
My client has error:

Section or group name 'caching' is already defined. Updates to this may only occur at the configuration level where it is defined. (C:\...\web.config line 17)

 We couldn't see any other web.config files in their installation, neither in machine.config. Any suggestions?

I also found another thread http://www.dnnportal.de/default.aspx/tabid/178/g/profile/u/320 , but I can't read German(can you?) to understand, if they have any solution.


Michael Freidgeim http://geekswithblogs.net/mnf
 
New Post
8/10/2006 10:08 PM
 
Install one version under one Virdir and another under another virdir. You can have, in that way, several installs (I have 7) . By changing the cookie name, you can work with all of them at the same time without worrying at all. Just pay attention when assigning the aspnet version that each install uses.

Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
New Post
8/16/2006 11:59 AM
 
~Hey

   We did eventually get it to work. I never thought about changing the cookies. What we ended up doing was creating the second install in a Virdir under a dummy website. When we tried mult. virtuals under the default website, we still got the inheritance issue. We also put the new Virdir under it's own app-pool, and gave it a different port. By isolating them so much, they didn't have a chance to steal each other's passed values in the config file.  Whether all these steps are necessary is debateable, but after all these things were done, it worked.

~Joseph
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN Multiple Installs for Dev on IIS6 (3 + 4)DNN Multiple Installs for Dev on IIS6 (3 + 4)


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