Which verson of DotNetNuke are you using?

From your description, it appears that you do have DotNetNuke installed correctly, and that the website is configured correctly. Your problem is that DotNetNuke is not connecting to the SQL Server.

As you have not made any changes to the parmeters on the Configure Database Connection screen, it's clear that something needs to be changed. Here is how I would go about diagnosing.

You said that you can connect to the database using SQL Server Management Studio Express. What were the server, usename and password that you used? Those are the ones that you should use in the DotNetNuke configuration.

I am using DotNetNuke 5.5 Community Edition.

I am using Windows Authentication to connect to SQL Express 2005 database. The server name is ".\SQLExpress". No user name and password has been specified.

During installation of DNN, at the "Configure Database Connection" stage the same parameters has been used and "Integrated Security" has been selected as default.

Still I am getting the connection error and am unable to complete installation of DNN.

Do I have to make any changes to web.config (in the connectionstring section)? Do I have to attach the app_data\database.mdf database to SQLExpress prior to installing DNN? How do I do that? I tried to do it through SQL Server Management Studio Express. But it is automatically choosing a non-existant folder C:\DotNetNuke_Build\Websites as the location.

I am unable to catch where I am making the mistake. Waiting for suggestions from other experienced developers.

Thank you.

Lalit Kumar Barik

You shouldn't edit web.config.  The installation wizard will do that for you.

I have always found it easier to create a user and login and not to use Integrated security.  Also, I create my own database before starting the Wizard.  That way, I know exactly what I am using and where it is.

I have WIN7 professional 32 bit, SQL Express 2008, trying to install DNN5.06 install, Created Database "Dnn506" prior to install, Created user with All privilages to DB. I can sign into DB using this new user without any issue. When Installing Auto option is disabled, I take Typical, I enter Dnn506.mdf, enter user ID, and password, uncheck as owner (I have tried as owner as well), Click Next I get Connection error. I have redone the whole process several time. Can not pass this point. I have followed everything in Lee's videos. I can't figure out what is missing. Appreciate your help.

Try entering DNN506 as the database name.  DNN506.mdf is the file name, not the database name.

I'm having the same issues with 5.06.01. Following Lees videos. Before I joined I was going my own way but thought it time to learn more. I didn't have any probs before with 5.04. Now I get this error using both integrated or run as owner.

Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 14
Number: 18456
Message: Sql login failed

Got so p...ed off thinking that I had changed a setting uninstalled SQL 2008 Express and reinstalled afresh copy 2008 R2 and still get the same error.

What to do?

Check both connection strings in your web.config file.  Since the message is "login failed" that would seem to indicate that either the username or password is incorrect.  Also make sure that you are pointing correctly to the SQL Server.

You say that you had no problems with 5.04, but do have problems with 5.06.01.  Is this an upgrade or separate installations?  If you have an installation that is working, check those connection strings and compare them to the ones that do not work.

Reinstalling software isn't likely to help.  Make sure that passwords work.  Also, if you haven't permitted TCP/IP connections you may have trouble, but I don't think that you would get that login failed message in that case.

Thanks Joe.

I did finally get it sorted. The videos that I had did not contain the "How_to_install_DNN_to_windows7_video5" with the workaround for the Win 7 issues. Even with following video 5 the Auto feature was never available. One thing I found, I like to add a prefix to the table names, was that caused an error. I tracked it down to the fact that the prefix string was too long. Looks to be a max of 3 chars. May they (DNN) should mention the length.

Also never had the Test Connection button on any of the install pages.

Yes, the Windows 7 version of IIS is quite different, and I'm still not comfortable with it myself.

There is a decent video also available on the DotNetNuke.com site (I think you'll find a reference in Chris Hammond's blog there or on the Webinars page that refers to installation.)

If the prefix to which you refer is an Object Qualifier, the recommended best practice is to NEVER use an object qualifier.  It you are still near the beginning, I would do a new install without the Object Qualifier.

Hello everyone.
How can I test for a database login? I want to test to see if my database login works. I know I can connect to the SSMS (SQL Server Management Studio) with Windows Credential then the SSMS will allow me to attach the SQLExpress server instance, in which I can find the database "dnn490, for which I created with login_name and password.

Peter

The connection login screen for SQL Server Management Studio has an option to login using your standard credentials rather than Windows credentials. Use that option and specify the server, the user name, and the password that you use in your DotNetNuke connection string.