Ok new problem:

Basically I'm trying to take an existing database (that I was sent from someone) and use it to launch the site and modify it. So the portal already exists, if that makes sense. 

I have a database in SQL Express called DNN. This takes its files from the location C:\dnndb.
Then I have my Virtual Directory called DNN. This takes its files from the location C:\Websites\DNN.

I think the big issue I'm having it getting my virtual directory code (ie. web.config) to recognize and use the database. I currently have these two lines:
connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True; AttachDBFilename=C:\dnndb\DNN_Data.mdf;"

But I get this error:

DotNetNuke Upgrade Error

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

ERROR: Could not connect to database.

Unable to open the physical file "C:\dnndb\DNN_Data.mdf". Operating system error 5: "5(Access is denied.)". An attempt to attach an auto-named database for file C:\dnndb\DNN_Data.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

Do you have a control panel for managing your Database and/or account on your host server? 

I used the Database=DNN name because you said in your initial post:
"I have a database in SQL Express called DNN"

Using a database manager you can tell the SQL Express Engine where the DB files are and the connection string will then be able to use the name that you specified in the DB Managment console.

Hi, I think when you say that you "go into SQL Express and right-click on the database" that you are actually using the database management program I am talking about. It looks like this:

If you have a named user then it would be good to use that user in your connection string so that you do not have to get permisions for the website to be trusted in the Database.

The User should be given DBO privledges.

There is a pretty good Step by Step setup here:
http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/38723/scope/posts/Default.aspx

Hi John,

Came across this post and realized it was one of the few post I had seen where someone with an extensive knowledge of dnn had address some basic SQL Express questions and in particular, questions concerning the management tool SQL Managment Studio Express.  I'm sure there are many folks who originally set up their sites using the free tools provided by MS and encouraged in the DNN documentation.  Many development environments probably look very similar to mine:

Either Windows Server 2003 or XP Pro
Visual Web Developer
SQL Express 2005
IIS6

Now to the questions and how they relate to this post. I too frequently receive the previously posted error when trying to connect to my db via the database management tool.  It happens when I'm trying to attach the db to do a backup or restore operation. I n order to get past the error, I have to do things like kill the worker process associated with either the ASPNET Machine account or Network Service account, depending on  what operating system I'm working on at the time.  I searched and posted for help on the appropriate forums for these tools but receive no help.

I did not intially create an empty db with this tool when I first installed dnn.  I also did not have to make any changes to the connection strings in the web.config file and my installation went smoothly.  So, I have a db just named database with no username/password info in the connection string.  I assume that I can sometimes connect to the db using the management tool only because I set the program up to use windows authentication and not SA.  I also assume that VWD connects the same way, through or by windows authentication.

I tried to implement your suggestion posted earlier so as to rid myself of this frequent error I receive when trying to attach the db through the management tool but when I change the entry(s)? in my web.config, the site would not load.  It wouldn't be such a big deal to have to do  things like kill the wp.exe to attach the db if I only did it frequently, but the more I try to customize/personalize my dnn installation I am more and more having to interact with the db.  So this error is a real irritant.  Her's what I've done so far:

Original connection strings:

Modified connection strings in order to change the way SQL sees the db:

Once done, I get the following error:

Cannot open database "Database.mdf" requested by the login. The login failed. Login failed for user 'ADM-LTDEVELOP\ASPNET'.

What did I do wrong?  This is my dev site so it's not urgent.  I'm just trying to improve my effeciency with working with dnn and getting rid of this problem would help me with my backup and restore procedures.

Long winded I know:-) but I try to be precise in my explanations.

Thanks,

Paul

If you connect to the DB with a named user and attach it in SQL Express manager you should have smoother sailing.

There is a blog about the trouble you are having here:

http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1202/Default.aspx

You may still have to kill the asp.net process to detatch or backup the DB, but that happens with any DB that has a connection from ASP.Net, even in SQL Server.

Thanks John...always the resourceful one.  The blog helped me a great deal.

Paul