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 ...Help with installation from scratch with 3 serversHelp with installation from scratch with 3 servers
Previous
 
Next
New Post
2/2/2011 2:58 PM
 
DNS runs on my SBS domain controller.
My local domain looks like this:
Name Type Data Timestamp
_msdcs   
_sites   
_tcp   
_udp   
DomainDnsZones   
ForestDnsZones   
(same as parent folder) Start of Authority (SOA) [378], acsbs.argosy.local., hostmaster.argosy.local. 10/14/2010 2:00:00 PM
(same as parent folder) Name Server (NS) acsbs.argosy.local. 1/30/2011 7:00:00 PM
(same as parent folder) Host (A) 192.168.221.5 1/30/2011 7:00:00 PM
aciis Host (A) 192.168.221.6 1/28/2011 3:00:00 PM
acsbs Host (A) 192.168.221.5 2/1/2011 8:00:00 PM
acsql Host (A) 192.168.221.7 static
Companyweb Alias (CNAME) acsbs.argosy.local. static
connect Alias (CNAME) acsbs.argosy.local. static
DEV Host (A) 192.168.221.11 1/31/2011 4:00:00 PM
LAW Host (A) 192.168.221.12 1/31/2011 12:00:00 PM
SBSConnectComputer Alias (CNAME) acsbs.argosy.local. static
SharepointSMTPServer Host (A) 127.0.0.1 static
Sites Alias (CNAME) acsbs.argosy.local. static

------------------------------
The three servers are acsbs, aciis, and acsql

IIS is bound as *, 80, *

I have tried having the DNN files in a virtual directory and in the root (inetpub\wwwroot) of Default Web Site

If I use a virtual directory, the extrenal site displays the Under construction page, and I have verified it's coming from this IIS by chaninging some of the colors.

But, when I add "\dotnetnuke" to the external URL, it gives me a 404 error.

When I don't use a virtual directory and put the DNN files straight into the wwwroot, I also get the 404 error.

the Default Web Site also has a Virtual Web for C:\WINDOWS\web\tsweb, and that works.

"All the solutions are simple, but only after you already know them" Robt. Pirsig
 
New Post
2/2/2011 10:44 PM
 
My next attempt was to download the DNN installation zip files again in case something went corrupt.. This did not produce any improvement.

I'm at a loss as to what to try next. This is why I've flattend and rebuilt these servers numerous times.  If I try enough different  things and they all don't work, the systems eventually get fouled up beyond all going back.

There's got to be just one little thing that I'm overlooking. I don't want to lose my sense of humor about this, so yes, I have checked to see that the power cord is plugged in..

"All the solutions are simple, but only after you already know them" Robt. Pirsig
 
New Post
2/3/2011 2:58 AM
 
IIS: did you specify default.aspx as default document? Which user do you use for your application pool? I suggest using ASP.Net 2.0 Integrated. Your connection string should follow one of the samples in release.config. HTH

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/3/2011 4:43 AM
 
ok – lets go back a few steps
 
** you should as a rule never use your default webserver instance for anything
 – small business server used to have an annoying habit of stuffing elements in there.
 
** you should always define explicit bindings for each web server – domain and port
 
** you should not use \inetpub\wwwroot  or any subfolder below it
 ===========================================================

1. on any machine:
 
open the cmd line
 
>>  ping   aciis.argosy.local
 
and make sure you get the correct ip address or
 
>>  nslookup   aciis.argosy.local
 
2. on your iis server
 
your can create a folder anywhere – but for consistency
 
lets call it  \inetpub\dnn  - note it does not even need to be in \inetpub\ but for consistency lets put it there. 
 
unpack the DNN INSTALL.ZIP contents into this folder.
 
3. create a new user account on your server and call it dnn_APPPOOL
 
we will use it later
 
4. in your iis manager
 
create a New Web Server
  ( not a virtual folder  of your default web )
  ( not a sub folder of \inetpub\wwwroot )

assign it to its own application pool
make sure the application pool is asp.net 2.0 integrated
 
point the folder for this web server to \inetpub\dnn
and set its bindings to   aciis.argosy.local   port 80

you do NOT want to use the default bindings – too many other things can clash with them especially in sbs land
you want to set up explicit binding directly to a domain name.
 
make sure default.aspx is the default document for this web server.
 
5. in your application pool
assign dnn_APPPOOL as the user identity.
 
6. in the security settings for the folder \inetpub\dnn
assign dnn_APPPOOL full access rights to the folder and its descendants
 
7. you should now be able to open a web browser on any computer inside your local domain and type
http://aciis.argosy.local/  and see the dnn installer appear.

You can edit your web.config file and setup your sql settings before running this depending on how you feel
but most people find it just as easy to let the installer handle this process.
 
8.
note - i would have thought that a pointer to a smtp server should not resolve to 127.0.0.1
SharepointSMTPServer Host (A) 127.0.0.1 static
 
would have thought it should be something like
 
SharepointSMTPServer Host (A) 192.168.221.5 static
 
9.
the same would go for the smtp mail server – which dnn is going to ask you for during setup.
 
mail Host (A) 192.168.221.5 static
 
or some such – assuming exchange is running on your sbs server.
 
Westa
 
ps - there is a reason why people call in a specialist to build these sort of things.
 
 
Sent: Thursday, February 03, 2011 6:53 AM
Subject: Installing DotNetNuke : Re: Help with installa...
 
 You can view this post by clicking here.
 Getting Started
 Re: Help with installation from scratch with 3 servers
 by Richard Burr On 2/2/2011 2:58:09 PM  
New post in Installing DotNetNuke:
DNS runs on my SBS domain controller.
My local domain looks like this:
Name Type Data Timestamp
_msdcs   
_sites   
_tcp   
_udp   
DomainDnsZones   
ForestDnsZones   
(same as parent folder) Start of Authority (SOA) [378], acsbs.argosy.local., hostmaster.argosy.local. 10/14/2010 2:00:00 PM
(same as parent folder) Name Server (NS) acsbs.argosy.local. 1/30/2011 7:00:00 PM
(same as parent folder) Host (A) 192.168.221.5 1/30/2011 7:00:00 PM
aciis Host (A) 192.168.221.6 1/28/2011 3:00:00 PM
acsbs Host (A) 192.168.221.5 2/1/2011 8:00:00 PM
acsql Host (A) 192.168.221.7 static
Companyweb Alias (CNAME) acsbs.argosy.local. static
connect Alias (CNAME) acsbs.argosy.local. static
DEV Host (A) 192.168.221.11 1/31/2011 4:00:00 PM
LAW Host (A) 192.168.221.12 1/31/2011 12:00:00 PM
SBSConnectComputer Alias (CNAME) acsbs.argosy.local. static
SharepointSMTPServer Host (A) 127.0.0.1 static
Sites Alias (CNAME) acsbs.argosy.local. static

------------------------------
The three servers are acsbs, aciis, and acsql

IIS is bound as *, 80, *

I have tried having the DNN files in a virtual directory and in the root (inetpub\wwwroot) of Default Web Site

If I use a virtual directory, the extrenal site displays the Under construction page, and I have verified it's coming from this IIS by chaninging some of the colors.

But, when I add "\dotnetnuke" to the external URL, it gives me a 404 error.

When I don't use a virtual directory and put the DNN files straight into the wwwroot, I also get the 404 error.

the Default Web Site also has a Virtual Web for C:\WINDOWS\web\tsweb, and that works.
 You can view this post by clicking here.

If you no longer wish to receive notifications, please visit Your Profile and change your notifications options.

 
New Post
2/3/2011 12:37 PM
 
Sebastian Leupold wrote:
IIS: did you specify default.aspx as default document? Which user do you use for your application pool? I suggest using ASP.Net 2.0 Integrated. Your connection string should follow one of the samples in release.config. HTH

 Hello Sebastian, Yes, default.aspx is specified as the default and at the top of the list.

Under Application Configuration, I have tabs for Mappings, Options, and Debugging.

Under Mappings, I have Application extensions, and a long list of application extension types, the paths to the application that handles them, and the verbs that are supported. There is also an area for Wildcard Application Maps, which is empty.

Under Options, I have checkboxes for session state, buffering, parent paths, and side-by-side assemblies. The first two are checked. The timeout is specified as 20 minutes, the Default ASP language is specifed as VBScript, and the ASP Scrpt Timeout is set to 90 seconds.

Under Debugging there are checkboxes for Debugging flags and for Error messages, the radio button for Send detailed ASP error messages to client is selected.

I dont see a place to specify a user for the Application Pool.

Where is release.config.HTH found? There are a number of releaseNotes.txt files that are in the download directories, but these do not talk about the installation configuration string.

Thank you for your assistance.
RB


"All the solutions are simple, but only after you already know them" Robt. Pirsig
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Help with installation from scratch with 3 serversHelp with installation from scratch with 3 servers


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