Hi,

I'm fairly new to this. I've got that dreaded error when I try to browse to my newly installed DNN installation by using http://localhost .... here's what the error says:

DotNetNuke Upgrade Error
The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database specified in connectionString for SqlDataProvider

I had this error with both DNN 2.1.2 and just tried DNN 3.0.8 and no change. Here's my 3.x config file (I've only included the stuff that relates to the SQL data connection):

<appSettings>
<add key="SiteSqlServer" value="Server=cops;Database=DotNetNuke;uid=dnn;pwd=dnn;" />
<add key="MachineValidationKey" value="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902" />
<add key="MachineDecryptionKey" value="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC" />
<add key="MachineValidationMode" value="SHA1" />
<add key="InstallTemplate" value="DotNetNuke.install" />
</appSettings>

For Server= I have tried "localhost", "(Local)", "cops" (the machine name), and even its IP address. I've even tried putting in a machine name that doesn't exist - "blarg" !! But noooo, it makes no difference. I am running this all on Windows 2003 Server, with IIS6 and SQL Server 2k SP3 (official product name & version is MS Sql Server Standard Edition, version 8.00.194).

I have followed the instructions to the letter - regarding permissions for the ASPNET and "NETWORK SERVICE" accounts having full file/folder permissions. I've even given the aforementioned two user accounts dbowner permissions in my SQL database. I've tried creating various different SQL databases, different uid's and pwds, etc etc.

What strikes me as odd is that even when I put in a totally fake server name into the web.config file, it still gave the same error.

HELP!!! I have a little IIS experience and very little SQL experience but believe me, I've searched and searched the net and tried to find out as much as I could before posting here - I'm at my wit's end! Any help would be SO MUCH appreciated.

Thanks in advance,

Ashley Dando

Are you sure the user 'dnn' with password 'dnn' exist in your database and has access to the DotNetNuke database that you have created ?

You could try connecting to the database with another tool first to see if the database is not your problem.

I myself am using EMS MS SQL Manager for this.

http://www.sqlmanager.net/products/mssql/manager

---

Geert Veenstra

Hey Geert,

Thanks for your suggestion! I downloaded a trial of EMS MS SQL Manager and I think we may be narrowing down the problem! I went to register a database.... typed in "localhost", switched to SQL authentication and entered "test" and "test" which are the username/password I created (along with some others - "dnn", pw "dnn"). None of them work when I try to click the dropdown box to select my database - I get the following error message:

Login failed for user 'test'. Reason: Not associated with a trusted SQL Server connection

If I switch back to Windows Authentication it works fine. I presume that's because I'm logged into the box (locally) as Administrator? Note: I'm not too well-versed in using SQL Server so maybe I set up my database(s) and/or user(s) wrong?

Any suggestions?

thanks in advance!

Ashley

Geert,

I GOT IT WORKING!!! The short answer: In Enterprise Manager, Right click on the server, click Security tab, select under Authentication "SQL Server and Windows". I had tried a few times earlier today to select that radio button, and every time I clicked OK, it would close out of the screen, and the next time I went back in there, the setting would have reverted to Windows Authentication. This time around, when I changed it, it said "This will be saved, but you have to restart the server" - which it never said before when I'd tried all those times. Weird huh?

I deleted all my databases, deleted all the extraneous user accounts I'd created, then shut down SQL Server, restarted it, created a DotNetNuke database, created a user account with dbowner permissions, did the above-mentioned change to both authentication types, updated web.config, and voila, it runs.

Thanks for the hint about EMS - it gave me the ability to test my connection and get meaningful error messages. <sigh> I started working on this problem at 4:30pm and it's now 1am. I am very tired but satisfied to have beaten it - I couldn't go to bed defeated!

Geert thanks once again for your help - your answers lead me down the trail which caused me to stumble on another forum article (when I searched in Google for the "Not associated with a trusted SQL" error message) which caused me to try the above mentioned authentication setting. To be honest, I still don't understand the whole authentication thing, but at least it's working now.

thanks again

Ashley

I'm having the same problems, but my SQL server is on a separate machine. It does allow both authentication methods, but I still can't get it going at all. Does DNN need to have the SQL server running on the web server box?