I'm trying to install the latest DDN onto our Windows 2003 server using a local SWL Server DB. I've read through the install PDF, which references that 3.x process for the package I'm using.

I set up the DB, the login, the user, then modified the web.config to match, then launched my site.

It then starts the wizard (which seems to repeat things I already did in web.config)

I get to the CONFIGURE DATABASE CONNECTOIN and I entered in the following:

Server: (local)

Database: DotNetNuke

User ID: DDNportal

Password: [the password]

Run ad dn Owner NOT checked.

Object qualifier: ddn_

I then run the TEST DATABASE CONNECTION and I get the green 'OK' text.

Then I hit next, and then get this connection error:

============

Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 16
Number: 2714
Message: There is already an object named 'DDNportaldnn_Version' in the database.

=============

Any ideas as to what is going on and what to change to fix?

So...does 'testing' the connection 'install' the db, thereby causing the 'next' function to error out?

Is the fix to just blow out the DB and start fresh? (I'll give that a shot regardless)

With 4.x, is there any reason to do the manual config file changes, or is that what the wizard is for?

Thanks, all.

Indeed, somehow, the DB got created, but the wizard never got beyond that screen, so any subsequent NEXT clicks would give me the error, as the DB was already there.

I went into SQL, delete the table that was created, went back to the site and then the wizard started over, this time fully installing the software.

Fairly painless in the end.

Again, thanks!