Hi my name is Trevor Forrester and I'm fairly you to dotnetnuke and I would like to share some of my insights into the installation process of dotnetnuke 6.0.4.
I posted on this for about a week ago that I was having problems getting access to the database during the installation process. I then spent the next four days reading am looking on the Internet for instance.
The problem that I was having was that when I try to connect to the SQL database be at an express version for full version I was getting the following error:
connection error(s): index #: 0 source: .net sqlclient data provider class: 14 number: 18456 message: sql login failed
I search and search and finally I did a full reinstall because I thought there was something wrong in the subsystem that was not allowing me to connect to the SQL database during the installation. I checked and rechecked the permissions for the user accounts as explained in the video that I watched from the
Dotnetnuke website. I went through all the procedures of setting permissions, setting up a database, creating a logon, setting up a website and the general installation process. I have followed this process to the letter and I had no Joy, I was always getting the above error no matter what I did.
Finally after many hours of frustration and being much bolder I finally found the answer in the Microsoft SQL Forum.
What is the answer:
The Answer Is This because the instructions to installing dotnetnuke tell you to create a logon to the new database and select SQL authentication this does not mean that there is a logon to the server itself for the current user. When I checked I found that I had Windows mode authentication even though I had installed the SQL server with mixed mode IE: both Windows authentication and SQL authentication. There was no logon for the SQL authentication to the database proper.
What I had to do was create a logon for my current user and give that user access to all the databases and superuser for sa privileges.
It is important to remember that I was installing this on a local instance of Windows. The logon that I created was a superuser or administrator logon to administer the databases as a SQL authenticated user. If you are in a production environment I would suggest that you only create a logon to the dotnetnuke database with SQL authentication for the current user.
I hope that you find this of help during your installations because I must have read and come across hundred and hundreds of articles describing this particular problem going right back to dotnetnuke version 4.
Okay I have said enough for now so good computing.
Regards
Trevor