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 ...DotNetNEWBIEDotNetNEWBIE
Previous
 
Next
New Post
5/20/2006 10:48 AM
 

I need some help with the web.config file. I have looked on the forums and saw that with the latest version of DNN that all I need to do is reconfigure the release.config file. I have tried that and I still can not get it to work. Below is the code I have after configuring it to my settings. Could someone take a look and tell me what they see is wrong?

==================================================

<configuration>
  <!-- register local configuration handlers -->
  <configSections>
    <sectionGroup name="dotnetnuke">
      <!-- the requirePermission attribute will cause a syntax warning - please ignore - it is required for Medium Trust support-->
      <section name="data" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>
      <section name="logging" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>
      <section name="scheduling" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>
      <section name="htmlEditor" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>
      <section name="navigationControl" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>
      <section name="searchIndex" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>
      <section name="searchDataStore" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>
      <section name="friendlyUrl" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>
      <section name="caching" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>
      <section name="authentication" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>
    </sectionGroup>
  </configSections>
  <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" />
  
    <add
      name="SiteSqlServer"
      connectionString="Server=(local);Database=DotNetNuke;uid=DotNetNukeUser;pwd=*password;"
      providerName="System.Data.SqlClient" />
   -->
  </connectionStrings>
  <appSettings>
   
    <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=DotNetNukeUser;pwd=*password;"/>
    -->
    <add key="InstallTemplate" value="DotNetNuke.install.config" />
    <!--  Alternative Install Templates (included in package)
    <add key="InstallTemplate" value="Club.install.config" />
    <add key="InstallTemplate" value="Personal.install.config" />
    <add key="InstallTemplate" value="SmallBusiness.install.config" />
    -->
    <add key="AutoUpgrade" value="true" />
    <add key="InstallMemberRole" value="true" />
    <add key="ShowMissingKeys" value="false" />
    <add key="EnableWebFarmSupport" value="false" />
    <add key="EnableCachePersistence" value="false"/>
  </appSettings>
  <system.codedom>
    <compilers>
      <compiler
        language="vb"
        type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"
        extension=".VB" />
    </compilers>
  </system.codedom>
  <system.web>
    <machineKey
      validationKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902"
      decryptionKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC"
      decryption="3DES"
      validation="SHA1"/>

 
New Post
5/20/2006 11:32 AM
 

what you need to do with web.config is:

  • on upgrades: save existing web.config of the root folder of your DNN installation
  • copy release.config to web.config
  • on upgrades: keep the following settings from previous web.config (by copying them from saved web.config to new one):
    • MachineValidationKey
    • MachineDecryptionKey
    • ObjectQualifier
    • SiteSqlServer
  • in new installations: alter SiteSqlServer, so it meets your SQL server settings (See the installation instructions, how to set up database)
  • call your web site, installation should start.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/20/2006 12:26 PM
 
It looks like your REM's <-- -->  are possibly in the wrong places, or not there in others.  To determine this, we will need to know the version of SQL Server that you are using.  eg. SQL 2000, SQL 2005, SQL Express 2005?
 
New Post
5/20/2006 6:45 PM
 

I found another post under the Install It forum that mentioned that all I needed to do was copy the release.config file and add the username and password for the localhost, but that did not work. Here are the specifics of my installation:

 

SQL:  SQL Server 2000
DNN: 4.0

If there are any other specifics needed just reply.

 
New Post
5/20/2006 10:59 PM
 

I think that I see your problem now.  I also use SQL Server 2000 and my config had to be altered some from the original by RIM out the SQL Express stuff and un-REM the SQL2000/2005 part.  Read this instruction guide that I made about a month ago, it is 4 pages long and if you follow it exactly, you should have no problem setting up DNN 4.x.

You can view my instructions by clicking HERE

Notice on the last page, I put an example of the connection string when using SQL Server 2000.

good luck

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DotNetNEWBIEDotNetNEWBIE


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