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 ...DotNetNuke on Fasthosts.co.ukDotNetNuke on Fasthosts.co.uk
Previous
 
Next
New Post
5/28/2008 7:42 AM
 

Hello,

I have managed to install and run DNN locally without any problems. I wanted to try it out Online, so i uploaded an out-of-the-zip fresh instance of DNN, with necessary web.config changes, to my server on Fasthosts. However I keep stumbling on to the same error everytime time:

 


Server Error in '/' Application.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: 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.

Source Error:

Line 87: 	<system.web>
Line 88: <!-- Ensure validationkey is not set to AutoGenerate,IsolateApps so it correctly supports webfarms -->
Line 89: <machineKey
Line 90: validationKey="AutoGenerate,IsolateApps"
Line 91: decryptionKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC"

Source File: e:\domains\p\domain.com\user\htdocs\dotnetnuke2\web.config    Line: 89

 


I have spent hours on the phone with Fasthosts trying to resolve this issue. Basically what they're saying is it's my code that's not being configured correctly. They have uploaded an aspx page into the same folder and it's running apparantly. But I personally think that this has nothing to do with an individual aspx file, but is due to their IIS not configuring my dotnetnuke as an application. Or maybe even, it's a permissions problem and the server wouldn't let web.config file to be overwritten. That is what I wanted to ask you lot. Fasthosts have told me that they do not give support for DotNetNuke related queries so I'm kind of in a corner.

Changing hosts is the last thing I want to do. So before that I just wanted to know the opinion of experts in this forum, whether it's a config problem not being set correctly by me, or it's an issue with my host ? Any info will be greatly appreciated.

 
New Post
5/28/2008 8:28 AM
 

 

 

 

 

Make sure your IIS virtual folder is not called "dotnetnuke2". If you root a virtual folder in to the physical folder with the same name with in the same URL namespace the IIS server will always default to the physical folder. Also, ASP.NET applications often inherit settings from web.config of the root application despite the virtual folder acting as separate application. You may need to modify the web.config of the parent ASP.NET application to disable inheritance

<location path="." inheritInChildApplications="false">
  <system.web>
  ...
  </system.web>
</location>

 


Affordable DotNetNuke Hosting Affordable DNN Hosting & Support - www.ihostasp.net
Slavic Kozyuk
IHOST, LLC
Call toll-free: 1.800.593.0238
 
New Post
5/28/2008 9:03 AM
 

Thank you for your quick reply Slavic,

As you may have noticed from my previous post, I'm using a shared hosting called Fasthosts, therefore I have no control over their IIS. So what I'm asking was is there anything I can do from my end to fix this issue, or is this issue related to my host's IIS (which I have no control of) ?

I have tried putting inheritance to false as you have suggested, but the issue still remained and I'm 100% certain that I'm not viewing the "cached" web.config file.

This is my first time installing DotNetNuke on the remote server (a newbie), therefore if anyone have any suggestions please keep posting them I will try them out.

Thanks,

Bee.

 

 
New Post
5/28/2008 10:09 AM
 

The other thing I could think of is ...

I was reluctant to buy a new domain & hosting space for just testing DNN so I put it up on the existing website's child folder. So I'm trying to run DNN from a child folder. i.e. there is currently a classic asp website on: www.myDomain.com, but I've uploaded this /dotnetnuke folder to: www.myDomain.com/dotnetnuke/. I think this may be causing the issue as it's not being configured as an application, but just treated as a sub-folder of the Classic ASP application. Any expert comment on this will be greatly appreciated.

Thank you,

Bee.

 
New Post
3/30/2009 11:51 AM
 

Hello.
I added this

<location path="." inheritInChildApplications="false">

include web.config file. but I have a question. which path add in "." this area?? May you show me an example path, please...
thanks...

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DotNetNuke on Fasthosts.co.ukDotNetNuke on Fasthosts.co.uk


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