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 Problem/Requirements for 4.0.3Install Problem/Requirements for 4.0.3
Previous
 
Next
New Post
6/16/2006 10:18 AM
 

3 basic ideas.

1) Open IIS Manager. Go to computer | web sites | myWebSite & right-click to get Properties dialog. Under there should be a ASP.NET tab that will tell you what version of ASP.NET is in use for that particular web site.

2) Under the documents tab, verify it is looking for default.aspx, if you just enter a URL with only a directory specified

3) Under Home directory tab, ensure it is going to the directory that has the default.aspx file in it. Then you SHOULD be able to browse to http://mywebsite (not some sub directory from here).

good luck!

 

 
New Post
6/16/2006 10:50 PM
 

I was finally successful in getting the default DotNetuke page to appear!     I have come to the conclusion that the order of installing the OS, patches and applications are VERY IMPORTANT.    I say this because the first install of the OS was in this order:

Install OS with no patches

Install additional applications

Get all patches for evrything already installed.

Then setup DNN exactly as the Installation Guide says for a Source install.

Then under the IIS Manager right clicking the website(DNN) and going to ASP.NET properties tab ONLY 2.0.5... was displayedAnd the install of DNN would not happen because of a "Page not found" error.

After bouncing around on this for a couple of days, I wiped the hard disk and started over.    On the second install of OS things were done in this order.

Install OS with no patches

Get all patches for the OS (and I mean all)

Install additional applications

Get any additional patches for OS and applications combined.

Then setup DNN exactly as the Installation Guide says for a Source install.

Then under the IIS Manager right clicking the website(DNN) and going to ASP.NET properties tab BOTH 1.1... and 2.0.5... were displayed.   The the install of DNN at least happened, it was not correct but the web page would display. 

Getting the web page to display the correct data took another three tries.

When I say the correct data I mean the same data that was displayed on my XP system after only 1 install of DNN.

Oh YES, on my Windows 2003 Server system, going back to Control Panel/Add Remove Programs display, ONLY .NET 2.0 shows, there is no entry for .NET 1.1

Thanks for your help.

 

 
New Post
6/16/2006 11:30 PM
 
msnodgrass wrote

I'm setting up DotnetNuke 4 on a new Windows Server 2003 box.  This is a new install of 2003 Server.  I have installed SQL Sever 2000, Visual Studio 2005 and MS Office 2003.  SP1 has been applied to this server as well as any patches MS has as of 2 days ago.  Only .NET 2.0 has been installed.  The virtual directory is setup and running under the default web site, since I'm doing everything locally for this box. ....... it is in a workgroup.  Now when I try to browse to the site using the URL http://localhost/DotNetNuke or from the browse menu option in IIS for the virtual directory I get the error message HTTP Error 404 Page Not Found. 

Having dot net 1.1 on the box is not a problem - you can run both simultaneously, but only if you create a new application pool for the second version. This has nothing to do with the problem. 

A couple of things to check:

  1. Your url above says localhost/dotnetnuke - is this the the folder name for the virtual web under the default website?  Is that the website definition?  (name under properties)
  2. Any reason why you put this under the default website?  I normally create a new web site under the web sites folder, but not under the default website. Have you tried the other way (simply stop the default, create a new site pointing to the same folder and give it a new definition such as dnn, mydnn, etc. to avoid confusion, then start the site and try browsing to the site)
  3. You mentioned working on the server, but also mentioned not on a network (you meant domain I assume) but on a workgroup.  You are browsing in IE on the actual server with IIS6 when you browse to localhost - correct?  (obvious but people do try to reach localhost on another machine from their PC).  Try browsing from any PC or even better the server by referencing the IP of the macine. This is especially more clear if you specify an IP on the website settings. 
  4. If you've set this up correctly as its own site with an IP, and have set default.aspx as the default document (remove all others), then all you need to do is type in the IP address for the site after http:// and it should work. 

If for some reason you want to keep it under the default web site folder as a virtual web, then first create a simple html page, create a new virtual web, put that page in the web folder, set it as the only default document and see if you can browse to that web.  Your problems are around IIS at this point from what you state - nothing to do with .net or DNN that I can tell.  It's probably a simple problem or step overlooked, but one that is frustrating to find. 

 

 

 
New Post
6/17/2006 8:31 AM
 

I can see that my previous posts were not as clear as I thought.

Yes, having .NET 1.1 and .NET 2.0 on a machine is not a problem, my development environment at work is that way.   The NOT being able to install DNN 4.0.3 at all was because of .NET 2.0.    As I said in my previous post I installed Visual Studio 2005 and then got all the patches.   VS 2005 will install it's own version of .NET 2.0, which apparently has some differences from the .NET 2.0 the MS will download when you check for updates/patches.

However, if you get all updates/patches first, then install VS 2005, .NET 2.0 is not installed by VS 2005. Since VS 2005 thinks/knows .NET 2.0 is already on the computer.

On the web.config, even if the connectionStrings settings and the appSettings have errors, you will still get messages that tell you there is a problem, not a 'page not found'.  Which is the error message I got on my first install of the OS on this computer.

Putting DNN under the 'Default web site' does not require any html page in order to work.  You only need to put default.aspx as a document type in the Document tab under Properties of the virtual directory in IIS manager.

All the web sites I have developed at work have been created on my development computer this way.  When we move to a test or production box then the web site gets a 'real web address'.   Since at that point an entry is needed in DNS for any one to be able to see it.

One other reason I did it this way is because of the Installation Guide in the 4.xx section page 34 it quite clearly shows creating a virtual directory under the default web site, NOT as a seperate website.

As I said in my previous post, I have solved the install problem.

Thanks for your help/input.

 

 
New Post
6/17/2006 1:13 PM
 

The reference to a plain html file was purely a baseline test to ensure your IIS and website settings were correct. 

I guess I missed the solved part - congrats.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install Problem/Requirements for 4.0.3Install Problem/Requirements for 4.0.3


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