Having LOTS of trouble over here trying to install DNN on a server for our company.
Steps taken so far:
a) A couple of weeks ago, downloaded the latest DNN 4 Source package onto my home computer (XP Pro).
b) Downloaded the template mdf that was missing from the zip package and installed it where it was expected (providers/data_providers/sql/)
c) Ran the program -- and it hickupped -- but finished by finally creating the database, and was ok.
d) Made changes to the styles, inputted pages texts and layout, and basically made a cute looking website.
Now, ready to install it on the office's win2003 server, I've wasted days getting no where.
Help.
The office is going to be using DNN only as an intranet, so they have NOT invested in the full version of SqlServer, only SqlServer Express there too.
What I've done to move it there was:
a) Downloaded NET 2.0 onto the server, and installed it.
b) Downloaded SqlServer Express onto the server and installed that as well, using the generic instance name (sqlexpress) and Windows security and not the SqlServer builtin security (so no 'sa' account, etc.).
c) Changed no rights/roles/anythin on the server, as the SqlServerExpress installation did not make mention of a need for any changes.
a) Zipped up the whole website folder, with mdf within it.
b) Used Microsoft Sql Express Management Studio (Beta) to make a backup of the mdf.
c) Ftp'ed them both over to the office.
d) Unzipped the website,
e) unzipped the mdf backup, and used a second copy of MSEMS to restore the database over the mdf that was in the zip.
f) Rightclicked the folder and webshared it. Made no changes to any settings (ie: script only, not script/exe rights, etc..)
g) Went to IIS, refreshed the tree to see this new virtual directory, and went to security tab, and ensured that anon access was on.
j) DNN instructions say that the virtual directory needs to have Network Services=Full rights, so I do that.
h) Made an attempt to access the website via a browser -- denied.
i) Added "Everyone" to virtual directory...ok, have access.
j) ...But have an error.
"Could not connect to database specified in connectionString for SqlDataProviderSystem.Data.SqlClient.SqlException:
An attempt to attach an auto-named database for file D:\SITE\D4\database.mdf failed.
A database with the same name exists, or specified file cannot be opened, or is located on UNC share."
Which -- even if written in nice big bold letters -- is not helping find a solution, because:
i) It doesn't matter what I rename database.mdf to, and update the web.config to point to (dnn.mdf, database2.mdf, etc. all fail).
ii) The file is on the same computer, and the path not written in UNC notation. (D:\SITE\etc...) so that's not the problem.
iii) No other programs are open and pointing to this mdf (sqlserver express management studio is closed, etc.)
iv) The virtual folder at this point has rights wide enough to drive a truck through it, so it should be able to get SqlServer instance running under it to open the mdf. Or does it?
v) I also tried connectionStrings that refer to the path directly rather than using the "|DataDirectory|" macro -- that didn't help.
vi) There are no usernames/passwords to use, because its the ASP.NET account that is running the show, plus SqlServer was installed with Windows rights management only.
So. What am I doing wrong?
I've even downloaded DNN again directly to the office server, to install a new DNN site from scratch in a second virtual directory -- same problem. In other words, it not just an upgrade issue..
If its a rights issue, what rights should be assigned to
a) the virtual directory running on Win2003
b) any other place? Anything special has to be done to SqlServer Express?
If else, what else?
So damn frustrated after a long lost weekend. Help.