There are 2 points into the web.config file where you have set the connection string.  To use backwards compatible modules that still used lower package manifestes as the DNN version you are using (e.g. you want use a module 4.x.x on a DNN 5.x.x) you need the 2nd connection string!  So you must have set both connection strings successfully.

On your sample I so you ahve empty types on the connectionString properties, that makes isses to connect to the database.

Your wrong sample:
Server=   db2.3essentials.com

Must be:

Server=db2.3essentials.com

Basicly you could use both connection strings, the file based connection string only could be used if you have installed a SQL Server on the same maschine as the IIS is installed. The file based connection string also used the Integrated Security.  File based connection only supported one connection to the database, which mean that you could not connect to the database with SQL Management Studio if your DNN is online!  The database file is located on the App_Date folder.

For using a SQL Server that is installed on a 2nd maschine or you want use a webfarme you have to use the SQL Server connection string.  Personaly I use this methode, so I could also work on the database on a running DNN instance.

If you want connect with SQL Management Studio to your database and you use the "db2.3essentials.com" you have also to connect to this server if it is not your local server.

Hope this helps to solve your issue.

---

Regards

Matthias

DNN MVP

www.aarsys.de

Metro7 Skin

ShoutCastStats Module for DNN

Currently, your localhost install of DotNetNuke is using the Database.mdf file located in the App_Data folder. It will not be accessible in MS SQL Server Management Studio without attaching to the file.

Please see the following older, but still valid blog entry concerning how to attach to the Database.mdf file and in particular note the issues that will require you to modify your web.config's connection strings (2) after attaching to the database file outside of DotNetNuke:

http://www.dotnetnuke.com/Community/B...

I recommend (except for quick test installs of DotNetNuke on localhost) always creating a blank database manually (usually with username/password credentials created for SQL Server Authentication rather than Windows Authentication)  then supplying its connection information to the install wizard when installing DotNetNuke.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner