Downloaded the documents and Install package zips. Copied the files to the web server as directed in the readme file, and modified the web.config to point to the SQL Server DB located on the same box as directed by the Installation guide version 1.0.02.

Trying to start the install and getting the following error. Note, I'm using MS SQL Server 2000.

Server Error in '/DNN' 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: Unrecognized configuration section 'connectionStrings'

Source Error:


Line 15:     </sectionGroup>
Line 16:   </configSections>
Line 17:   <connectionStrings>
Line 18:   <!-- Connection String for SQL Server 2005 Express -->
Line 19:   <add


Source File: E:\websites\DNN\web.config    Line: 17

Any suggestions?

This is a symptom that the IIS virtual directory is not set up to use .NET 2. (4.0.0 requires .NET2)

---

Charles Nurse
Keydance Computer Services
Langley, BC, Canada

So the Checkdotnet.aspx link provided in the readme file does not check the .net version?. The link told me I was good to go.

I used the Windows Update program to install the .net2 framework and after rebooting, get the same problem. Dowloaded the .net2 framework from asp.net main page and it prompts me to repair or delete .net2. So I think I have .net2 installed correctly. ANy way to test?

Thanks!

Same error here with SQL Server 2000 on WH4L which is set up with ASP.NET 2

The DNN documentation for setting up SQL Server is wrong; it shows pictures of SQL Express Edition not SQL Server (on the html page for SQL Server). 

Does anyone have simple instructions for modifying the web.config to use SQL Server instead of Express?
It appears later in the config file that SQL Server is the default data provider.

---

Co-Author of UCanUse Products Get it here!

Let me answer my own question and for anyone else who has the same question:

You have to uncomment the 2 SQL Server connection strings, and comment out the 2 SQL Express connection string. 

I also discovered the domain was not configured to use ASPNET 2; I had to make a custom request to WH4L to switch it to ASPNET 2.

The documentation for using SQL Server should be cleared up to reflect the above I believe.

---

Co-Author of UCanUse Products Get it here!

Ragolko!  Well done, well done. You were dead on for both accounts. I finally pulled up web.config with VS and the need to comment and uncomment for my MS SQL Server 2000 popped right into play.

I also had to tell my web site in IIS to use .net2 and now the install is kicking off!!  Woot!

Thanks again!!