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 ForumsAuthenticationAuthenticationStep By Step AD Authenticator in IIS 7 on Windows Server 2008 Standard (NOT R2)Step By Step AD Authenticator in IIS 7 on Windows Server 2008 Standard (NOT R2)
Previous
 
Next
New Post
3/7/2011 3:02 PM
 
 OK I am starting this thread for I am missing something in the installation process. I want to be able to come out of this with a community installation howto that anybody can use. Here are the steps I am doing right now. 
  1. Installed DNN and configured
  2. changed .Net Trust Levels for website in IIS to be Full(Internal)
  3. changed application pool for website to classic .Net AppPool (This can be a new pool created as long as the Managed Pipeline Mode is set to Classic)
  4. Installed AD authenticator
  5. Went to Admin>Extensions>DNN_ActiveDirectoryAuthentication and found the following error
    Error: is currently unavailable.
    DotNetNuke.Services.Exceptions.ModuleLoadException: Access is denied. ---> System.Runtime.InteropServices.COMException (0x80070005): Access is denied. at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_IsContainer() at System.DirectoryServices.DirectoryEntries.ChildEnumerator..ctor(DirectoryEntry container) at System.DirectoryServices.DirectoryEntries.GetEnumerator() at DotNetNuke.Authentication.ActiveDirectory.Settings.CheckPipelineMode() at DotNetNuke.Authentication.ActiveDirectory.Settings.Page_Load(Object sender, EventArgs e)
    --- End of inner exception stack trace ---
  6. Configured the settings that represent the domain and authentication settings. Did not set any Auto login Addresses
  7. The global catalog, root domain etc, all came back OK. (Green sign and everything! :) )
  8. went to the site address and found;

    The Active Directory Provider requires the site to be running

    under Full Trust and/or in Classic mode in IIS 7.0


I was under the impression that I had set both of these up correctly in steps 2 and 3 shown above.

It is obvious I am missing something. I have read the post from Dan Bell (Using DNN with Windows Server 2008 R2 w/AD Authentication) and I understand that when you change the settings in IIS that it edits the web.config and that you should copy a backup into the folder. I am replacing the web.config with the backup (In my case I am not seeing IIS rewrite the web.config but it cant hurt)

I have combed the other posts here for last couple of days looking for what I am missing. I need some direction as to where to go next.

Thanks in advance for everybody's help.

Richard


 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationStep By Step AD Authenticator in IIS 7 on Windows Server 2008 Standard (NOT R2)Step By Step AD Authenticator in IIS 7 on Windows Server 2008 Standard (NOT R2)


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