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 ...SiteSqlServer has already been addedSiteSqlServer has already been added
Previous
 
Next
New Post
7/25/2006 7:30 AM
 
Hi,
im trying to install a second instance of dotnetnuke (4.3.3) on my local machine and i'm getting the following error;

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: The entry 'SiteSqlServer' has already been added.
Source Error: 

Line 27: 	-->
Line 28: <!-- Connection String for SQL Server 2000/2005 -->
Line 29: <add
Line 30: name="SiteSqlServer"
Line 31: connectionString="viewmobile;Database=coralsolutions;uid=dbtestuser;pwd=xxx;"

I have read the posts relating to this problem and i'm almost certain that my web.config settings are correct.  (see below);

  <connectionStrings>
    <!-- Connection String for SQL Server 2005 Express
    <add
      name="SiteSqlServer"
      connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
      providerName="System.Data.SqlClient" />
    -->
    <!-- Connection String for SQL Server 2000/2005 -->
    <add
      name="SiteSqlServer"
      connectionString="viewmobile;Database=coralsolutions;uid=dbtestuser;pwd=xxx;"
      providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules  
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>
    -->
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->
    <add key="SiteSqlServer" value="viewmobile;Database=coralsolutions;uid=dbtestuser;pwd=xxx;"/>
     

I already have DNN 4.3.1 installed and wanted to install 4.3.3 fresh.  I'm not sure if i can actually have 2 instances of DNN running on the same machine pointing to 2 different databases on the same instance of Sql Server.

any help would be appreciated.
John
 
New Post
7/25/2006 8:37 AM
 

No, your web.config does contain an issue as stated, there CANNOT be two connection strings with same name, if you have SQL2005Express with file based db, use the first one, otherwise the second entry. please remove the second one.

You can have as many DotNetNuke portals per DotNetNuke installations, as your Server can bear.

You can have as many DotNetNuke installation in your IIS (in different web sites or virtual directories) on your IIS as your server can bear, either with separate Databases or sharing a single Database and membership provider using different ObjectQualifiers (but I would not recommend this)


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/25/2006 10:02 AM
 
the other connection string was commented out.  Just to be sure, i completely removed the SQLexpress connection strings.  Here is my new web.config.  But the error is the same..

  <connectionStrings>
    <!-- Connection String for SQL Server 2000/2005 -->
    <add
      name="SiteSqlServer"
      connectionString="viewmobile;Database=coralsolutions;uid=coralsolutions;pwd=xcoral12345;"
      providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <add key="SiteSqlServer" value="viewmobile;Database=coralsolutions;uid=coralsolutions;pwd=xcoral12345;"/>
    <add key="InstallTemplate" value="DotNetNuke.install.config" />


Also,
i'n not actually creating a new portal.  I am installing a completely new instance of DNN 4.3.3 on a machine that already has an instance of dnn 4.3.1.

any ideas
cheers
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SiteSqlServer has already been addedSiteSqlServer has already been added


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