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/27/2015 6:05 AM
 

Hi, we are trying to install 7.4.02 onto an AWS server, we have created a new database, created a new website in IIS, set the new App pool as security etc etc.But when we navigate via local host or external browser we get a 500 error. (details below). Can anyone point me in the right direction??

HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information:
Module   IIS Web Core
Notification   BeginRequest
Handler   Not yet determined
Error Code   0x80070021
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:\inetpub\wwwroot\mysitename\web.config
Requested URL   http://localhost:80/mysitename/
Physical Path   C:\inetpub\wwwroot\mysitename\
Logon Method   Not yet determined
Logon User   Not yet determined
Config Source:
  103:     </modules>
  104:     <handlers>
  105:       <remove name="WebServiceHandlerFactory-Integrated" />
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.
View more information »
 
New Post
10/27/2015 7:27 AM
 
is there a reason, why you didn't install DNN in the root of the website?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/27/2015 7:52 AM
 
Hi Sebastian, No specific reason, but we usually install into specific server folders to separate our websites.  I did try installing direct in wwwroot and as a subfolder within root to see if that would work but it still gave the same errors.
Is there a reason why this should affect the install.  We have installed this way many times on many servers but I am always open to a bit of knowledge
 
 
New Post
10/27/2015 9:10 AM
 
the error indicates issues with an inherited web.config or machine config, which prevents some of the settings in your web.config.
if this is not caused by web.config in parent folder, it must be some setting in machine.config of your IIS.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/27/2015 9:40 AM
 
I have a bunch of sites happily on an AWS instance. I wrote about it here.

http://www.dnnsoftware.com/forums/thr...

update - the small instance does not have enough grunt for more than one low volume site.

I'm with Sebastian. I put site folders well away from C:\anything. I prefer them on another drive one folder per site.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
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