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 on AWS ec2 serverInstall problem on AWS ec2 server
Previous
 
Next
New Post
10/28/2015 10:49 AM
 
Yes, we have installed as a website before and used bindings in IIS, in fact this is what we do on our internally hosted webserver.  And it is what I want to do in AWS,  but I cannot install as a website to take advantage of this.
We have 12 portals we want to build that share same modules and some shared news articles  and events. So it is desirable to have one instance where modules are installed only once and information can be shared across them. I do not want to have to have 12 instances if at all possible.
It must be a 2012 server issue or maybe my instance of AWS as we have successfully installed DNN as a website on other versions of IIS,  but at the moment I cannot find a solution.. very frustrating as this is is exactly why we chose DNN for its multiple portals ability.
 
New Post
10/28/2015 12:57 PM
 
I do not recognize the phrase "...Installed DNN as a website..." as having any special meaning.

Step 12 of my article ("In IIS Manager create a Site/VirtualDirectory for your site and point it to the web site folder") says that you can either add a Site or a Virtual Directory. The two are interchangeable.

Can you explain what you mean by "...install as a website..."?

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
10/29/2015 4:29 AM
 

Sorry Richard, I am probably not explaining things welI, or my terminology is confusing.
As you know,  In IIS you can either point the default web site or if you right click on the  sites node you add a new web site and point that to the folder where you install is. After install , you then have the option in IIS to add bindings and apply https certficates for all your portals.

This is what we have done in our other 2 DNN sites on our virtual servers 2008 R2,  and I am certain this is the approved method by DNNCorp .

BUT , in our new AWS 2012 server, we cannot install into either the default website or any other site we create in IIS as we encounter "It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS." 

We were only able to install by creating an application and installing into it (as per you excellent post), however an application or a virtual directory has no options in IIS for adding multiple bindings  and as we want to make use of multiple parent portals and share modules / data across them an application wont work for us.

Unless I am missing something (I hope)?

 

 

 
New Post
10/29/2015 8:58 AM
 
Hi Stuart,

I cannot say why it is not working for you; but I have nine sites configured as you describe on my AWS box. In my post (which you kindly referred to) I find using a new site, works fine. It's my default choice.

It certainly *can* be done. Sorry I cannot spot your problem.


Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
10/29/2015 10:56 AM
 
Richard Howells wrote:
Hi Stuart,

I cannot say why it is not working for you; but I have nine sites configured as you describe on my AWS box. In my post (which you kindly referred to) I find using a new site, works fine. It's my default choice.

It certainly *can* be done. Sorry I cannot spot your problem.

 Yes, that is the bit that was confusing me, the very fact you have installed as we want at least gives up hope. We intend to build a new server in case we missed something in the set up and try again
Thanks

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install problem on AWS ec2 serverInstall problem on AWS ec2 server


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