Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install DNN 4.0.3 on Windows Server 2003, SQL ExpressInstall DNN 4.0.3 on Windows Server 2003, SQL Express
Previous
 
Next
New Post
5/24/2006 4:34 PM
 
I would like to begin by saying that the ONLY reason I am posting this is because of a post that *almost* got me through the entire installation process

I would like to begin by saying that the ONLY reason I am posting this is because of a post that *almost* got me through the entire installation process.  Almost all of the following instructions was done by KathrynRF, so any and all credit should go to her (post can be found at http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/21459/scope/posts/Default.aspx)  It is only because of this post that I was able to make it through this process.  With that said, I am making some small adjustments according to my system and hope that those who need it will find it just as helpful to them as the above post was to me.  If you do not have the same resources as I do, I recommend going to the link above.

DNN 4.0.3 Source

Windows Server 2003

IIS v. 6.0

SQL Express v9.0.2047

ASP.NET 2.0.50727

1)       Create a directory and unzip the DotNetNuke source file there. (I put mine here C:\DotNetNuke)

2)       Copy DotNetNuke.install.config (C:\DotNetNuke\Website\Install\) and place it directly into the Website folder

3)       Create IIS Virtual Directory:

a)        Control Panel -> Administrative Tools -> Internet Information Services

b)        Open Up the tree: (by clicking the +’s) MyComputer (local computer) -> Web Sites

c)        Right-click on Default Web Site and select New -> Virtual Directory

d)        Click "Next"

e)        Enter "DotNetNuke" for the Alias and click "Next"

f)        For your local path Browse to C:\DotNetNuke\Website (or wherever you placed yours) and click "Next"

g)        Check all the following boxes: Read, Run scripts, Execute, Write. 

h)       Click "Next"

i)         Click Finish

4)       To finish configuring DotNetNuke Virtual Directory right click on the Directory in IIS, "Properties"

a)        Virtual Directory Tab

i)         Read, Write, Log Visits, Index this Resource.

ii)       Application Name: DotNetNuke

iii)      Execute Permissions: Scripts and Executables

iv)      Application Pool: DefaultAppPool

b)        Documents Tab

i)         Move Default.aspx to the top of the list

c)        Directory Security Tab. Only work w/this for enabling AD

d)        ASP.NET Tab: Confirm V2.0.5027 is enabled

e)        Click "Apply" and "OK"

5)       Set up File Access

a)        Open Windows Explorer (click windows symbol on keyboard & E together)

b)        Right click on DotNetNuke folder

c)        Select “Properties” > “Security” tab

d)        Click “Add”

e)        In the “Enter the object names to select”, type Network Services then Click “Check Names” then “OK”

f)        On the “Security” tab, click give network services full control

g)        Click “OK”

6)       Set up SQL Server Express

a)        Run SQL Server Configuration Manager

b)        Navigate to SQL Server 2005 Network Configuration -> Protocols for SQLExpress

c)        Enable everything (Shared Memory was enabled, I enabled Named Pipes, TCP/IP and VIA). I’m not sure if everything is necessary, but I went for overkill.

7)       Complete setting up SQL Server Express

a)        Open MS SQL Server Management Studio Express (downloadable from Microsoft)

b)        Right click on the server and select “Properties”

c)        Click “Security”

d)        Ensure “SQL Server and Windows authentication mode” is selected

e)        Click “OK”

f)        Restart the server to enable all the settings just changed (right click on the server and select “restart”)

8)       Create the Database

a)        Right click on “Databases” and select “New Database…”

b)        Enter Database name (DotNetNuke) and Click “OK”

9)       Set up DB login (Windows authentication) (not sure this step is necessary)

a)        Expand the Security folder in the tree, right-click on Logins and select “New Login…”

b)        Leave “Windows Authentication” selected, click ���Search” next to Login name.

c)        Enter “aspnet” in the text box and click “Check Names”; it should fill in with the ASPNET ID. (Please note that this is an extra step that I took just in case, you should only need the network services below)

d)        Enter “network services” in the text box and click “Check Names”; it should fill it in again.  Click “OK” twice to get back to the database tree.

e)        Expand database -> security. Right click on Users and and select “New User…”

f)        Click “…” next to “Login Name”

g)        Enter “aspnet” in the text box and click “Check Names”;

h)       Select the checkbox next to the ASPNET ID and click “OK”

i)         Click “OK”

j)         For User Name enter “DotNetNuke

k)       For “default schema”, enter “dbo

l)         For “schemas owned by this user”, check db_owner

m)      For “Database role membership”, check db_owner

n)       Click OK

10)    Set up another DB login (SQL server authentication)

a)        Expand the Security folder in the tree, right-click on Logins and select “New Login…”

b)        Select “SQL Server Authentication”

c)        Enter the login name (MyLogin)

d)        Enter the password (mypwd)

e)        Clear the checkbox for “Enforce Password Policy”

f)        Select the database from the “default database” dropdown (MyDB)

g)        Click OK

11)    Make a new copy of resources.config and name it web.config

12)    Update <appSettings> and <connectionStrings> in the web.config file.  There seems to be many different versions of the settings for this file, so I am just going to post mine and hope it works for you.  There are redundancies in mine.

a)        <appSettings> In red you will see the only items that I changed.  You may or may not have to change the database name.  If you put in the wrong username/password you WILL get a connection error, if that’s the case then double check your SQL settings and be sure you are correct.

<appSettings>

    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules   -->

    <add key="SiteSqlServer" value="Data Source=Arsenic\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" />                                 (my computer’s name is Arsenic)

    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules

    <add key="SiteSqlServer" value="Server=Arsenic;Database=DotNetNuke;uid=sa;pwd=password;"/>

    -->

b)       <connectionStrings>

 <connectionStrings>

    <!-- Connection String for SQL Server 2005 Express -->

    <add name="SiteSqlServer" connectionString="Data Source=Arsenic\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" providerName="System.Data.SqlClient" />

    <!-- Connection String for SQL Server 2000/2005

    <add name="SiteSqlServer"

      connectionString="Server=Arsenic;Database=DotNetNuke;uid=sa;pwd=password;"

      providerName="System.Data.SqlClient" />

   -->

  </connectionStrings>

13)    In the browser, navigate to http://localhost/dotnetnuke.  It *should* install.

14)    One last item I have to mention is an error message about a template missing.  Thanks to another post this is easy enough to solve. 

a)        Simply go to www.johnczimmerman.com then select “downloads.” (Thanks for sharing John!)

b)        Download the DotNetNuke_template.mdf file to corresponding directory.

c)        For me, it was installed in the SqlDataProvider folder: C:\DotNetNuke\Website\Providers\DataProviders\SqlDataProvider

Again, almost all of this work was done by KathrynRF, but I wanted to help others that needed a boost like I did.  So I really want to thank those whose work is in here.

 
New Post
5/31/2006 7:48 PM
 

Hey KimberlyRox,

I appreciate the step-by-step detail you provide in your post.  More people should spend the time doing like you did here, sharing details.  Nice job.  I used your post as a model for one of my posts; I even reference your post in mine.  If people reading your post have a system/situation more like mine, maybe they'd appreciate my link here:

http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/41044/scope/posts/Default.aspx

Tikkune


If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
 
New Post
5/31/2006 8:00 PM
 

Greetings,

               Thank you for the information. So far this information has got me furthere then before. I am stuck on this error though.

DotNetNuke Upgrade Error

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

ERROR: Could not connect to database.

An attempt to attach an auto-named database for file C:\DotNetNuke\Website\App_Data\Database.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

Have any idea?

 

                                           Rodney

 
New Post
6/2/2006 1:13 PM
 

Yeah, I got that one on one of my previous installs.  You will NEVER believe how it got fixed.  I don't believe it myself...   

Ok, according to posts, it is a problem with your sign on name in the web.config file.  What I did (and it basically fixed itself) was to change the logon name in the web.config file to the SQL administrator..  (sa) and entered the password for it (make sure to do this in BOTH places).  I opened SQL with that name and logon (to be sure it worked of course) and then I stopped IIS, restarted SQL, and then started IIS. 

For WHATEVER reason, problem was solved.  As before, it may have been extra steps stoping, restarting, starting..  blah, blah, blah...  but it worked and I didn't care! lol 

 
New Post
6/3/2006 5:21 PM
 

Greetings,

                THANK YOU!, THANK YOU!, THANK YOU! God bless you. That worked. Thank you for your help. This has been driving me crazy for days. I can't than you enough.

 

                                                                         Thank you,

                                                                                          Rodney Miller

                                                                                          World of Ours

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install DNN 4.0.3 on Windows Server 2003, SQL ExpressInstall DNN 4.0.3 on Windows Server 2003, SQL Express


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out