Call Us 203.687.6053

Blog with a focus on DotNetNuke news, tips and tricks, DNN SEO, and insights and opinions about the DNN community at large.

A Newbie’s Guide to Installing DotNetNuke

Posted by Mary on Monday, September 10, 2007 to DotNetNuke, DNN Tips and Tricks

Welcome to my first contribution to the Seablick Consulting blog! When Tom Kraak first asked me to write a “how-to style” blog post, I was thinking to myself, “what can I offer in regards to DotNetNuke? I’m a newbie!” Then I began to realize how much I have learned in a very short amount of time. I also realized that I am looking at DNN from a different point of view than someone with years of experience. So I may (and will) ask a lot of questions and I DO like feedback. One thing that I was very impressed with right from the beginning was the community’s assistance and reassurance of my success. So for my first post, I decided to detail my experience of learning how to do a local DNN install.

Installation is murky when you are new. As a developer, I like to know what is going on, where it’s going on and who it’s going on with. At first, I didn’t understand how the database “fit” into the architecture of a DNN site. Once I had a clean install up and running, I was able to go into SQL Server Management Studio (or the like) and actually look at the tables, select on them and see what the install had created. That’s when I began to get a bigger picture of how DNN works.

My local setup consists of a Windows XP Pro machine running IIS 6, SQL Server 2005, and the .NET 2.0 Framework.

There are 5 basic steps to a clean install. I will cover each individually in more detail below.

  1. Download the .zip file from dotnetnuke.com.
  2. Create the database and a SQL Server login
  3. Create the website folder and unzip the downloaded .zip file.
  4. Create virtual directory in IIS and configure the website
  5. Run the DNN install wizard in your favorite web browser.

1. Download the .zip file from dotnetnuke.com.

After you have logged into dotnetnuke.com, navigate to “Downloads”, select the desired file and save to your C: drive (for our example, I selected and downloaded the 4.5.3 INSTALL (DotNetNuke_04_05_03_Install.zip.)

2. Create the Database, SQL Server Login, and Database User

There are two things you need to do in SQL Server Management Studio. First, create a database. Second, create the SQL Server login for that very same database. Make sure that your database server runs in “mixed authentication mode” (SQL Server and Windows Authentication mode” is checked.) You can find this setting by right-clicking on your server (first node in the SQL Server Management Studio tree on the left), then Properties | Security.

Create the Database

  • Open SQL Server Management Studio
  • Select your desired server from the drop-down list and connect
  • Expand the tree on the left-hand side so you can see “Databases”
  • Right-click on "Databases"
  • Select “New Database”
  • In the "Database Name" field enter a name for your database and click OK. For this example, I entered “DNN453”
  • You now have an empty database called DNN453

Creating a login for your database:

  • Expand the Security node of your server
  • Right-click on Logins
  • Select “New Login”
  • Enter your desired login name. You must remember this login name and password as we will use it later. For my purposes here, I’ve entered “DNN453Login” (without the quotes) as my login name.
  • Select “SQL Server Authentication” and enter a password. I entered “test” as my password.
  • Uncheck “Enforce Password expiration/User must change password at next login”
  • Click “User Mapping” on the left
  • Select/Check the new database you created in the top grid “Users mapped to this login:”
  • Select/Check db_owner in the bottom list “Database role membership for: “
  • Click OK
  • Now look in the Security node under your database (DNN453) and you will see a newly created database user listed, meaning we also created a new database user by mapping our SQL Server login to our database.

The database portion is now complete.

Create the site folder and unzip the downloaded .zip file.

In this step, we create a folder and unzip the DNN install .zip file to this directory. You can put it directly under C:\inetpub\wwwroot or C:\foldername. For this example, I used C:\DNN453.

  • In Windows Explorer, create a new folder called DNN453 on your C: drive. This will be the folder where your website files will live.
  • Extract (unzip) the DotNetNuke_04_05_03_Install.zip file that you downloaded earlier into your desired folder (C:\DNN453 in our example)
  • After extraction is complete, the folder contains a web.config file that needs to be modified. Remember how I stated in the beginning that DotNetNuke and the database “fit” together? We must now tell DotNetNuke which database our website is using. We do this in the web.config file. The default web.config file even gives us “samples” of connection string entries so that we only need to modify these based on our database setup.
  • Open the web.config file and find the <connectionStrings> tag. You can use Notepad, Visual Studio or any other text editor to accomplish this. There you see two entries of connection string statements – one for SQL Server Express and one for SQL Server 2005. By default, DNN uses SQL Server Express. The connection string for SQL Server 2005 is commented out. For our example (we are using SQL Server 2005), we must reverse this and comment out the SQL Server Express statement and “uncomment” the SQL Server 2005 statement. After that, we need to enter the correct values for server, database, uid and pwd according to the database we set up above. In the below screenshot, XP1234 is my machine/my local SQL Server (please note, if you are using server instances, it is entered as: XP1234\MYINSTANCE where MYINSTANCE is the name of the SQL Server instance). DNN453 is the database name (as specified in step 2.) Enter "DNN453Login" and “test” for uid and pwd, respectively.
  • We must also modify the key for the “SiteSqlServer” under the <appSettings> tag. Again, SQL Server Express is the default, with SQL Server 2005 commented out. We must comment out SQL Server Express and uncomment SQL Server 2005 and again, enter the correct values for server, database, uid and pwd for our database.
  • Save and close the web.config file
  • Lastly, you must change the access permissions of your folder. The Windows account that is used to access your site must have full control over your DNN root folder. To set this, right-click on the root folder of your site (C:\DNN453). Click Sharing and Security. Click the Security tab. If you do not see the Security tab, you must “turn off” simple file sharing for the folder. To do this, select the root folder (C:\DNN453) in Windows Explorer. Click Tools | Folder Options. Select the View tab. Uncheck “Use simple file sharing.” Click OK. You can now right-click the folder and access the Security tab.
  • On the Security tab, you will see a list of users who have access to your folder. Windows XP uses the ASPNET account and Windows 2003 uses the NETWORK SERVICE account. Add the account and give it full control permissions.

4. IIS – create virtual directory and set-up

Now that the database and file system are in place, we can create the virtual directory in IIS.

  • Open IIS and expand the tree to see “Default Web Site”. (You can find IIS in Start | Control Panel | Administrative Tools.)
  • Expand the "Default Web Site" node.
  • If you have placed your DNN root folder under C:\inetpub\wwwroot, you will already see your website and can bypass this step. If not, you will need to add a virtual directory.
  • Right-click on "Default Web Site"
  • Click New | Virtual Directory
  • Enter an alias – "DNN453" will do
  • Click Next and enter/browse to the path to the root folder of your website.
  • Click Next and leave access permissions as is (should be set to Read/Run Scripts.)
  • Click Next and Finish

Now that a virtual directory is in place, you’ll need to modify its properties.

  • Click on the "Documents" tab
  • An entry for “default.aspx” needs to be added. Add default.aspx and move it to the top of the default documents list.
  • Click on the "Directory Security" tab
  • In the “Anonymous access and authentication control” group box, click "Edit"
  • Make sure that “Anonymous Access” is checked as well as “Integrated Windows authentication”
  • Next, click on the "ASP.NET" tab and make sure that “2.0.50727” is select for the ASP.NET version
  • Click OK to save your changes

5. Run the DNN install wizard in your favorite web browser to complete the installation process.

The very last step is to initiate the DNN install via a web browser. The install wizard takes over. In doing so, it creates tables and stored procedures in your database and adds the needed data rows to these tables to house your site. You will be prompted to test your folder’s permissions, test the database connection and lastly, enter your desired user name and password for your host and admin user. Write these down!

  • Open your web browser of choice and navigate to http://localhost/DNN453 (replace DNN453 with the name of your IIS virtual directory)
  • You will be guided through an install wizard. Test your folder permissions when requested.
  • Verify your database connection when asked.
  • You will see the wizard running the script for each version.
  • On successful completion, click on “Access your Portal” and your new DNN-based website appears.

I hope that this tutorial offers DNN newcomers a better understanding of the DotNetNuke installation process on Windows XP Pro and SQL Server 2005.

Lastly, I would like to thank Tom for giving me this opportunity and for his patience and guidance. I’m hoping for a bright future with DNN.

Did I miss something or got something wrong? If so, I want to hear about it. Please leave your comments below as feedback is much appreciated!


Permalink Permalink      Comments 62 Comments      RSS feeds RSS feeds      Email updates Email updates

 

Comments

Comment By mq on Monday, September 17, 2007 at 1:15 AM

This installation guide was very helpful. I had been struggling the whole weekend to get dnn installed even though I had the DotNetNuke 4 book and reading various forums. This finally did it for me. THANK YOU!

Comment By MaryV on Monday, September 17, 2007 at 8:49 AM

I'm so very glad it helped! ~ Mary

Comment By Exiton on Tuesday, September 25, 2007 at 3:51 PM

I'd hate to spoil your enthusiasm and everything, but since you write this article for the newbies you should remember that newbie wouldn't know what IIS is. Also IIS is never present in any version of WinXP by default.

So the first order of business is to tell how to install IIS.

You start with the creation of the database, but neigther MSSQL Express, nor Management Studio would run without .NET Framework. Obviously you also have to instruct the user to install .NET Framework (especially considering the fact that .NET Framework is not their by default eigther).

But .NET Framework configures IIS during install and it would be improper to install it before IIS.

So we have it: install IIS, then download and install .NET Framework.

MSSQL Express and Management Studio don't fall from the sky eigther, and your typical newbie wouldn't know what it is, where to get it and how to configure it. You have to instruct him how to acomplish this.

Other than that everything is quite right. :)

Comment By Exiton on Tuesday, September 25, 2007 at 3:53 PM

Typo. "...is not their by default..." should be "...is not there by default..."

Comment By MaryV on Tuesday, September 25, 2007 at 4:02 PM

Thanks Exiton for your comments and honesty - my intention for this article was only on installing and it was geared toward developer's beginning in dnn with a programming base of knowledge. Maybe I should have put a beginning footnote of what is already assumed in the article. please keep the comments coming!

MaryV

Comment By Exiton on Tuesday, September 25, 2007 at 4:12 PM

Frankly, I can't imagine ASP.NET developer that would not know how to install ASP.NET application. So when I see "Newbie’s Guide to Installing DotNetNuke" I just assume we are talking about a _complete_ newbie here. :)

Comment By MaryV on Tuesday, September 25, 2007 at 4:59 PM

...maybe i should be calling these "A Newbie-Developer's Guide..."! :)

Comment By Tom Kraak on Wednesday, September 26, 2007 at 4:21 PM

Thanks to all for the comments.

Part of it was my fault as I picked the blog post title. I'll be more "careful" down the road.

Comment By GRR on Friday, September 28, 2007 at 8:52 PM

I followed your instruction to a t and I get this error when try to run:
"Server Application Unavailable - The web application you are attempting to access on this web server is unavailable. Please hit the "Refresh" button to try again..."

Am I missing something? Are you able to help?

Comment By Tom Kraak on Friday, September 28, 2007 at 8:57 PM

Just to be sure ... are you attempting a local install or a remote install at a hosting company?

Comment By Elliot S. Grossman on Sunday, September 30, 2007 at 10:37 PM

I'm trying to install 4.5.5 locally on Win XP Pro. I unzip the install package to c:/inetpub/wwwroot/dnn_sfcbsa. The unzipping does not create any sub-directories! The install process doesn't work. I keep getting thi sparser error: Parser Error Message: Could not load type 'DotNetNuke.Common.Global'.

I appreciate your installation notes, which I hope I followed to the letter. Maybe you can help me with this problem.

Many thanks.

Comment By MaryV on Tuesday, October 09, 2007 at 9:50 AM

Is this still a problem? sorry - been away - it sounds like you did not extract the entire install?? there are subfolders under the DotNetNuke (or in your case dnn_sfcbsa).

Comment By Tom Kraak on Tuesday, October 09, 2007 at 11:17 AM

Thanks for checking in Mary.

We've since resolved the problem, which was due to issues with WinZip.

Comment By RG on Saturday, October 13, 2007 at 1:01 PM

One item of note you left out. If your NOT creating a virtual directory (ie: putting DNN in your inetpub folder) the user needs when setting up IIs needs to make sure he/she clicks "Create" next to "application name" and that script source is checked.

Comment By John on Monday, October 22, 2007 at 5:22 PM

I'm going to be installing remotely in a few days. I noticed you specifically state "local" install... is there a big difference?

Comment By Tom Kraak on Monday, October 22, 2007 at 5:26 PM

Yes John, there are a few differences.

Who will be hosting your site? Is it "shared hosting," or will you have more control over the hosting environement?

Comment By John on Tuesday, October 30, 2007 at 10:26 AM

Hi Tom, thanks for the reply. It's hosted by Go Daddy. SQL2005. Not sure how much control I'll have as this is the first time I've tried to set a database up. I've built and managed a DNN site for 5 years, but always had an IT guy to do the SQL, IIS, installation, etc... all the techie stuff. This time I get to eat the whole enchilada.

Comment By Tom Kraak on Tuesday, October 30, 2007 at 10:52 AM

I do not recommend GoDaddy for DNN hosting, primarily because they have no clue about DNN.

You'll also have very little control especially over the database unless you are getting a dedicated box from them.

Comment By John on Tuesday, October 30, 2007 at 11:24 AM

Hmmmm. That's unfortunate. However, that's what I've got to work with for the time being. Hopefully I'll be able to figure it out. Thanks for the heads-up though.

Comment By Muthusree on Wednesday, October 31, 2007 at 5:16 AM

Nice article. Well,I have installed DNN in server. So localhost/DotNetNuke works.. But I couldn't access it from another computer.

Any Idea?

Comment By Déclic Vidéo FX on Tuesday, November 20, 2007 at 10:36 AM

Hello,

I have strictly followed the tutorial, but all my images are references as:
DNN453/Portals/0/images/myimage.gif
instead of
/Portals/0/images/myimage.gif

Where is my mistake ??? (I would like to backup my live website and use it in local to synchronise live and local, but unfortunately, I have this problem of path which is not correct and always show the .../"folder-name"/Portals/...
Why ??? I certainly make something wrong in the IIS, but I do not see where...
:-(

DV

Comment By Tom Kraak on Tuesday, November 20, 2007 at 10:51 AM

DV - I assume you are running XP locally as opposed to Win 2000/2003 Server. If so, that's where the issue is. IIS on XP won't allow you to create multiple websites, which is why you have to go the virtual directory route which then show up as a "folder" in your paths.

Clear?

Comment By Exiton on Tuesday, November 20, 2007 at 10:56 AM

You should have copied DNN scripts into the local site's root folder, so that the site could be opened by calling "localhost".

Comment By SEO Company Canada on Wednesday, December 05, 2007 at 2:57 PM

Great tutorial, I've been meaning to play with DNN for a while now!

Comment By meenu on Wednesday, January 09, 2008 at 1:33 AM

Dear friend now i am thinking you are my god .because i am struggling with this installation from last 1 week.my goodness today i got this link and tried everything is working properly.thanks a lot.only one problem i found that in my folder option i have no any aspnet user account .i added this using http://kbalertz.com/919075/Error-message-request-Application.aspx link
anyway thanks a lot
bay
meenakshi

Comment By Tom Kraak on Wednesday, January 09, 2008 at 10:56 PM

Excellent ... I'm glad you found it helpful.

Comment By MJZ on Thursday, January 10, 2008 at 4:25 PM

I'm doing this install with SBS 2003 R2 Premium and I've encountered a few issues:
1. I cannot simply create a directory DNN under inetpub/wwwroot. I get the error about the virtual directory not being configured as a separate application. When I create a virtual directory, I need to go to the VirtualDirectorty tab and click on the "Create" button next to the application name section.
2. Once I do that, I can get to the dnn install page. Currently, I'm stuck at the configure database. I get login failed because the user is not associated with a trusted SQL Server connection. I've verified that the user/password are identical... any ideas?

Comment By MJZ on Thursday, January 10, 2008 at 4:39 PM

Ok, I fixed (2) by right-clicking on the machine name in the management studio, bringing up properties, selecting security, checking Sql Server and Windows Authentication (it was Windows only) and restarting SQL.

Comment By mark richardson on Thursday, February 28, 2008 at 9:08 AM

Thanks for your dnn instructions (they are clearer than most).

I have installed DNN before on a development server, last year on SQL express , windows xp (it took ages and not exactly sure how I got it to work in the end, just kept trying it over and over).

Anyway, now I need to install it again on a live server. (on SQL Server express, windows 2000).
This time I would rather know how to get it working rather than trying the sheer mass install bombardment method and hoping that eventually 1 install would be successful.


I have followed your instructions:

1. Download the .zip file from dotnetnuke.com
2. Create the Database, SQL Server Login, and Database User
3. Create the site folder and unzip the downloaded .zip file. (also edit web config)
4. IIS – create virtual directory and set-up

I am stuck on this bit:

5. Run the DNN install wizard in your favorite web browser to complete the installation process.

The install wizard won't start. (page can't be found/doesnt exist thingy error)

* I have also added ASPNET in the security tab (in properties on the dnn website folder)

any ideas?

regards,
mark


Comment By Tom Kraak on Thursday, February 28, 2008 at 9:56 AM

Thanks Mark.

What URL are you using in the browser to start the install wizard?

Do you have DNS in place or are you trying to get this up and running via localhost from the server itself?

Also, IIS on Windows 2000 supports multiple websites, so no need to deal with virtual directories.

Comment By mark richardson on Thursday, February 28, 2008 at 11:39 AM

1. 'URL to start the install wizard'

I don't think this is the problem - tried all sorts:
//localhost/myIISname
//localhost/myIISname/install/installwizard.aspx
myServer/myIISname/
myServer/myIISname/install/installwizard.aspx

2. ... I am trying from the actual server itself.

3. 'Windows 2000 supports multiple websites' - oh, had no idea. what do you recommend instead?

thanks.

Comment By Exiton on Thursday, February 28, 2008 at 2:16 PM

You must have installed .NET before you IIS. Reinstall.

Another possibility is that you do not have "default.aspx" as your default document type. Add it by hand in the site's (or virtual directory) properties.

Comment By mark richardson on Friday, February 29, 2008 at 4:32 AM

thanks,

IIS was already on the server.
.NET framework was not on the server initially so this was the first thing I did (installed the .NET 2 framework ).

Then I installed SQL express.
Then SQL server management studio.

Then I followed the steps above.

(default.aspx is my default)

Comment By mark richardson on Friday, February 29, 2008 at 7:03 AM

further to the above...

I wonder if this problem could be related to my authentication.

In step 2 (above) it says:
'Make sure that your database server runs in “mixed authentication mode” '
When I right-click on server >> Properties >> view connection properties - it says "Windows authentication" (and so does our working installation on the development server).

I am not sure where to select this mixed mode authentication?


(When creating a login for the database,
I have selected SQL server Authentication)

Comment By alok on Wednesday, March 26, 2008 at 2:26 AM

Nice article. Well,I have installed DNN in server. So localhost/DotNetNuke works.. But I couldn't access it from another computer.

Any Idea?

Comment By alok on Wednesday, March 26, 2008 at 2:34 AM

I have installed DNN in my computer. So localhost/DotNetNuke works.. But I can not access it from any other computer in network like asp.net applications,which are able to be run in network by specifying the url of application's path. is there any settings to do or dotnetnuke applications are unable to be run in network..please guid me
thanx in advance



Comment By Tom Kraak on Wednesday, March 26, 2008 at 8:35 AM

Add the IP address of the host machine to DNN as a portal alias (xxx.xxx.xxx.xxx/DotNetNuke) and you should be able to browse to your local DNN installation from any PC on your LAN.

Comment By Leo on Wednesday, April 16, 2008 at 2:22 AM

Thanks for the article... It helps me a lot.

Comment By Tom Kraak on Wednesday, April 16, 2008 at 8:05 AM

You are very welcome Leo.

Are there other DNN related topics you would like to see covered?

Comment By Scott on Wednesday, June 11, 2008 at 9:56 AM

I get this error. I've installed DNN at least 5 times and cant figure this one out.

Installing Database - Version 4.4.0...Upgrading Database to Version ERROR: See C:\ARF\Providers\DataProviders\SqlDataProvider\04.04.00.log for more information...Success
undefined...Success
undefined...Success
undefined...Success
undefined...Success
undefined...Success
undefined...Success
undefined...Success
undefined...Success


Any pointers?

Comment By Tom Kraak on Wednesday, June 11, 2008 at 2:13 PM

Scott - there are 2 connection strings in web.config. Make sure they are both correct.

Comment By yy on Wednesday, June 18, 2008 at 1:38 AM

scott,
I got the same error as you did. If you started from a new database when installing DNN and only have DNN object ie not other data, remove all user tables, user stored procedures, user views and user functions (leave all the system objects) and then I followed the instructions in this website and it worked for me. Very helpful website this one. Many thanks.

Comment By Luis on Wednesday, June 25, 2008 at 3:39 PM

I followed all steps, but when I try to login to my web site, the redirected url is something like ".../Home/tabid/36..." and show the message 404 file not found.

Comment By Tom Kraak on Wednesday, June 25, 2008 at 9:17 PM

Luis - make sure asp.net is enabled in IIS. Can you browse to a .html file?

Comment By sai on Thursday, July 03, 2008 at 7:53 AM

hi,
Can any one help me with the error
Server Error
HTTP Error 500.19 - Internal Server Error

Description: The requested page cannot be accessed because the related configuration data for the page is invalid.

Error Code: 0x80070021

Notification: BeginRequest

Module: IIS Web Core

Requested URL: http://localhost:80/DNN453

Physical Path: C:\DNN453

Logon User: Not yet determined

Logon Method: Not yet determined

Handler: Not yet determined

Config Error: This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".

Config File: \\?\C:\DNN453\web.config

Config Source:

70: </modules>
71: <handlers>
72: <add name="AJAX_ScriptResourceHandler" path="ScriptResource.axd" verb="GET,HEAD" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" preCondition="integratedMode,runtimeVersionv2.0" />

More Information... This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
Server Version Information: Internet Information Services 7.0.

Comment By prajna karkal on Thursday, July 17, 2008 at 1:13 PM

Hi I get the following error can someone help me
Line 65: ''' -----------------------------------------------------------------------------
Line 66: Private Sub Application_Start(ByVal sender As Object, ByVal e As EventArgs)
Line 67: If Config.GetSetting("ServerName") = "" Then
Line 68: ServerName = Server.MachineName
Line 69: Else


Source File: C:\Websites\DotNetNuke_04.08\App_Code\Global.asax.vb Line: 67

Comment By Prajna Karkal on Thursday, July 17, 2008 at 5:06 PM

what i meant is when i followed all the steps and went to the url http://localhost/DotNetNukeP I get the above mentioned error for the config object and not the server name.

Comment By Brian on Monday, September 08, 2008 at 9:00 PM

I am having a similar problem to another poster. I installed locally to an xp sp2 pc on my 2003 server domain.

How do i access the localhost site on the xp machine from another computer? I am trying to use this as a company intranet site.

Thanks, Brian

Comment By Tom Kraak on Monday, September 08, 2008 at 9:33 PM

Brian - is your DNN install running fine locally on that XP machine? If so, add the XP's IP address or host name as a DNN portal alias via Admin > Site Settings > Portal Alias (scroll way down) and you should then be able to reach DNN across your LAN.

Comment By Michael Beunckens on Wednesday, September 17, 2008 at 5:21 AM

Very, very helpfull tutorial!
Worked the first time...

Thank you for clear and good instructions.

Comment By Lee on Wednesday, September 17, 2008 at 7:30 AM

Is it possible to set DNN up with integrated security rather than SQL security - I seem to have tried everything to no avail :(

Comment By Mattias on Saturday, September 20, 2008 at 6:05 PM

@Scott: Im sure you have solved this by now but if not i have a tip for you.

Take a look at the ObjectQualifier attribute in the SqlDataProvider key in web.config.
When i installed my site for the first time the attribute was set to "dnn_" and all my tables was named dnn_TableName.

In the upgrade package the ObjectQualifier was set to "" which didnt match my current tables in the db.

When i set the ObjectQualifier to "dnn_" in my web.config (from the upgrade package) it worked fine.

Comment By Twetee on Wednesday, October 01, 2008 at 3:53 PM

This was really really helpful... I really appreciate you for writing down each and every step in a very crystal clear manner..

Thank u soooo much!!!

Comment By Tom Kraak on Friday, October 03, 2008 at 11:35 PM

Thanks, I'm glad you found it helpful.

Comment By Shane on Thursday, October 16, 2008 at 5:13 AM

Hey all
Has anyone made a VMware or Virtual PC 2005/07 image with .netnuke running.......ive tried installing this so many times now im almost ready to throw my pc out the window.
If anyone has a image of this working PLEASE msg me
sicnics@hotmail.com

Comment By Jaffer Abbas on Tuesday, October 21, 2008 at 8:58 AM

Excellent guide. Worked as expected.

Thanks

Comment By Shane Small on Sunday, October 26, 2008 at 9:05 AM

Hey all
Ive successfully got a Win 2003 SQL 2005 (non express) dotnetnuke install setup under a virtual directory and can access the pages from inside my lan....If i wish to view from outside the lan how do i do this....what changes are required

thanks all

Comment By Tom Kraak on Sunday, October 26, 2008 at 10:47 AM

Shane - for one thing, you would have to configure your firewall to allow for incoming traffic on port 80. The, you will need to run DNS to map your website's internal IP address to an IP address accessible from outside your LAN. See dyndns.com or similar service.

I don't recommend any of this though as I think web hosting is in better hands with a web hosting company.

Comment By asphaltjesus on Thursday, December 11, 2008 at 2:33 PM

Hi,

I ran into an odd issue setting up dotnetnuke as a local dev platform on Windows XP.

**IF** you install .net runtime BEFORE you install XP's IIS, then the .net runtime is not set up for serving anything. You'll get strange permission denied errors because the user ASPNET isn't created.

The fix that worked for me is reinstalling the .net runtime. There's the possibility that clicking on the modify button under programs will do it, but I didn't bother to test it.

Comment By asphaltjesus on Thursday, December 11, 2008 at 2:41 PM

One more comment.

I completely buggered up my production host by installing "Visual Web Devloper 2008."

It seems the installer breaks the .net setup if you don't allow it to install everything and the kitchen sink. For example, if you decline to install .net 3.x, the host is configured as if .net 3.x exists anyway. This will break a functioning dotnetnuke (.net 2.x runtime) install.

Thanks for the production downtime Microsoft. Thanks a whole lot.

Comment By prasad on Tuesday, December 16, 2008 at 1:53 AM

Thanks for your Help
But I got a error while executing on web browser "The stored procedure 'dbo.GetPortalAliasByPortalID' doesn't exist." I spend 4 days for this installation of dnn.....Plz help me....

Comment By Tom Kraak on Tuesday, December 16, 2008 at 10:06 AM

Prasad - either your database objects (tables, stored procedures, etc) were never created or your db login/user does not have the proper permissions (needs to be dbo at least for the install.)

Add a comment