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 ...web.configweb.config
Previous
 
Next
New Post
4/25/2006 2:56 AM
 

I am setting up DNN 4.0.3 on a Win2003 server and SQL Server 2000.  I keep getting errors every time I try to set it up.  I was able to setup DNN 3.x about a year ago, but I forgot how I got it to work.  I think my problem is the web.config settings.  It seems like every instruction sheet says a different way to configure it.  Could somebody help me with some instructions for the changes that should be done on a setup like this?  My SQL Server is setup with SQL authentication instead of local.

Thanks,

 
New Post
4/25/2006 10:47 AM
 
Can't really help without knowing what errors you're getting...

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
4/25/2006 6:56 PM
 
I have tried many different settings in WEB.CONFIG with a different error each time.  I am pretty sure my database permissions are ok, and IIS is setup properly, which leads to that one config file.  Its a clean install and most of my errors have to do with the dabase connection, even though I set the rights in accordance with every instruction procedure that I can find.  If you were to setup a new DNN4 app, and you were using my configuration of equipment, what parts of the config file would you edit.  And would the config settings be different depending if I were to choose local authentication or SQL authentication?

Thanks,
 
New Post
4/26/2006 12:18 AM
 

Here is the connection part of WEB.CONFIG.  I am using SQL Server 2000 Enterprise locally with SQL Server authentication.  Listed is example database parameters.  Should I delete the SQL Server Express 2005 line?

I was able to get DNN3 working very easily about a year ago, and it ran nicely for a while.  Something is different with the new DNN4 config that is driving everyone crazy trying to get it to install.  Any help would be appreciated.

  • My SQL server is (local)
  • Database Name:  DotNetNuke
  • Fake Username:  dnnuser
  • Fake Password:  password



  <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="Server=(local);Database=DotNetNuke;uid=;pwd=;"
      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="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>


 
New Post
4/26/2006 12:35 AM
 

I am getting the following error.  "dnn" is my virtual directory.  Windows Server 2003, SQL Server Ent 2000 SQL authentication.

Server Error in '/dnn' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...web.configweb.config


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