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 ... It is an error to use a section registered...I know, I know It is an error to use a section registered...I know, I know
Previous
 
Next
New Post
3/24/2014 4:30 PM
 

I realize that this problem has surfaced before. And I have all the possible resolutions I have tried below. I have done my homework on this and I have still come up empty. I really have no idea anymore what to try or how to proceed. The computer is still in the room, but it's right beside the window and.....

The error is...

 It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.

...and seems to be a wide reaching problem for a lot of people.

I have gone through countless pages and sites and forums and have a list of so called resolutions.

I have tried...

Set this to 'True'...   <mvcbuildviews>false</mvcbuildviews>
Did that....no joy.

Extra or duplicate web.config file
Nope

Set as application.
Confirmed

"move your application to its own folder outside of the web root folder"
Did that...didn't work.

...modify your application's Web.config to remove the authentication, httpHandlers and httpModules...
Nope

Under 'Process Model'... change 'Load User Profile' to "True"
This was actually already set to 'True'

1- Open IIS 7.0
2- Select Default Web Site and Right-Click on it
3- Select Add Application... or Add Virtual Directory...
4- Select Contact as..
5- Change Path credentials: from Application user (pass-through authentication) to Specific user:
6- Add a Admin User with password like COMPUETRNAME\Administrator User

Tried this and when I click the "Test" button...SUCCESS!!!!!

But wait....no, still have the same configuration error.

Open the Feature View of your website.
    Go to Handler Mappings.
    Find the path for .cshtml
    Right Click and Click Edit Feature Permissions
    Select Execute
    Hit OK.
   Now try refreshing your website.

Had high hopes for this one....had
No joy

Sooooo

I have the physical path set to...

C:\inetpub\wwwroot\dnn7.com

and in IIS when I click "Browse dnn7.com on *:80"

it actually takes me to www.dnn7.com which is a dead site!

And in regards to physical path, I have set it to the following:

C:\inetpub\wwwroot\dnn7.com
C:\inetpub\wwwroot
C:\websites
C:\websites\dnn7.com

with apppool set to

dnn7.com (the project in question)
DefaultAppPool
Classic .NET AppPool
and well all the rest.

...and with all the combinations therein

And addressing the access possibility...

Authenticated users

System
forexbob (me)
Oolon (also me)
Administrators
Users
IIS_IUSRS
dnn7.com
Network Service

I have other sites up and running...html and php. Hell I got Wordpress running relatively easily.

Oh and yes. Whenever I made a change, I did restart the appPool.

If you haven't surmised already, I am a rookie at this stuff. I play with it from time to time and have learned an immense amount. But this one's got me on the verge of giving up.

Is there anyone out there that might have a different, unique solution to this problem?

 
New Post
3/24/2014 7:10 PM
 
this message occurs when asp.net is not able to read your website's configuration -as you've seen this can be very many reasons, all of which are IIS are windows related (the error is happening before any code in DNN get's ran). Whilst you've hit a few of the typical reasons, the most common is that you have not set your sites permissions correctly.

IIS now uses the concept of an application pool identity, which is a virtualised users that provides application isolation. This is a big stranger than previous versions which used a fixed user (such as networkservice), so easy to get wrong - I recommend reviewing http://www.iis.net/learn/manage/confi... -note: typically I recommend you set the application pool to network service initially (as it's easier to get right via the drop-down) - also take care to have the application pool use integrated pipeline and not classic pipeline. Next ensure that network service user has read, write and modify permissions for you website i.e. set it on the C:\inetpub\wwwroot\dnn7.com folder and allow it to propagate down. I find this is the most common user/permission configuration that resolves that particular error

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
3/25/2014 2:54 PM
 
Hi Cathal,

...and thanks for your response, I appreciate your help.

You've found some new ground for me, new stuff so that's always good.

I have read the article that you suggested and have added DefaultAppPool to the list having full access.

I have made sure that all access is minimum read/write.

I set the application pool to network service making sure to give it read/write permissions

I have confirmed that the app pool uses integrated and not classic pipeline.

I confirmed that C:\inetpub\wwwroot\dnn7.com includes permissions set as above.

No joy.

I have given "Full Access" to everything as opposed to just "Read/Write". I'm sure that can't be an issue, but I mention it just in case.

And I have confirmed in the process explorer...

w3wp.exe w3wp.exe 6356 < 0.01 109,028 K 46,044 K IIS Worker Process Microsoft Corporation IIS APPPOOL\DefaultAppPool

I am now opening the window....
 
New Post
3/25/2014 3:10 PM
 
In your original post you said:
>>and in IIS when I click "Browse dnn7.com on *:80"
That sounds like you have a binding set on the site for www.dnn7.com else it would not offer you that option.

>>it actually takes me to www.dnn7.com which is a dead site!
...and that sounds like you have no hosts file entry to point www.dnn7.com back to your machine.

Try the next option up - I hope it is Browse *:80

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
3/25/2014 4:01 PM
 
Hi Richard,

More input, excellent. I do appreciate it. And I'm always into learning more stuff.

I haven't actually dumped the computer out the window...yet.

When I check the advanced settings for my local dnn7.com the bindings are set thus:
http:*:80:dnn7.com

When you wrote, "Try the next option up - I hope it is Browse *:80" I'm not sure what you mean. Are you suggesting that there is another option other than 'http:*:80:dnn7.com' that should be just 'Browse *:80'? If so, I don't have it.

I don't play with the hosts file much but what I've learned I applied as follows:

127.0.0.1 www.dnn7.com
127.0.0.1 dnn7.com

This returns:

500 Internal Server Error
The requested Url does not return any valid content.
Administrators
Change this message by configuring a specific 404 Error Page or Url for this website.

Progress! I understand why this is happening.

However when I go to localhost/dnn7.com I still get the same error that started this whole mess. Though I knew the hosts file wouldn't correct the main problem.

Thanks to both you and Cathal for trying to help.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ... It is an error to use a section registered...I know, I know It is an error to use a section registered...I know, I know


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