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

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationIIS error on Windowssignin.aspx setting up AD Auth moduleIIS error on Windowssignin.aspx setting up AD Auth module
Previous
 
Next
New Post
9/4/2012 9:37 AM
 

Hi All,

I'm attempting to set up the AD authentication module on my production website after successfully installing it on my development website but ran in to an issue.

When I attempt to set the pernissions on Windowssignun.aspx within IIS, I see the following error in a pop-up:

"There was an error while performing this operation

Details:

Filename: \\?\c:\inetpub\wwwroot\dotnetnuke\web...

Line number: 564

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""

There is no line 564 in my web.config file and a google search suggested changing my applicationHost.config file.  However, when I opened this file, all lines referring to "overridemode" were already set to "Allow".

Although I see this error and cannot set the authentication properties of WindowsSignin.aspx, DNN lets me sign in using my network credentials.  I'd almost be willing to ignore this error but the login isn't happening automatically and I can't ask every company employee to manually log in every day to our intranet.

Any ideas on how I can resolve this?

Thanks,

Mark

 
New Post
9/4/2012 10:25 AM
 
You don't say what server OS you're using but I'm guessing that it's Server 2008 (either the original or R2) and you're running your site in the Integrated Pipeline mode. At the bottom on the documentation found on http://dnnauthad.codeplex.com it covers the different scenarios for IIS 7.x.
 
New Post
9/4/2012 10:43 AM
 
Hi Mike,

Sorry, yes, Windows Server 2008.

I was but I changed my apppool (called Dotnetnuke) to classic and .net 4.0 but I still see the same error when I attempt to change the authentication on WindowsSignin.aspx.

Thanks,
Mark
 
New Post
9/4/2012 10:49 AM
 
It may be worth noting that there is no default website set up in IIS and that the apppool I'm using has the following properties:

Name: Dotnetnuke
Status: started
.Net Framework: v4.0
Managed Pipeline mode: classic
Identity: Network service

Mark
 
New Post
9/4/2012 10:54 AM
 
There doesn't look to be anything wrong with the settings you have (and a default website isn't necessary). What happens when you use the default Classic settings (I think there are two .NET 4 and just classic)?
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationIIS error on Windowssignin.aspx setting up AD Auth moduleIIS error on Windowssignin.aspx setting up AD Auth module


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