Hi,

I've read through most of the recent posts on this forum and I remain confused with one thing.  Even when I disable the AD authentication provider, I still am able to achieve an automatic sign-in with my windows credentials passing through.  I think this must be normal and outside the scope of what the AD provider offers -- something made possible by configuring IIS for windows authentication and correctly applying the security settings to the windowssignin.aspx as documented.  Someone please confirm that this is normal behavior and that the AD provider isn't somehow doing work while disabled.  Note it even happened after uninstalling the provider all together, so I'm pretty confident.  I *thought* the provider was working when a new user could hit the site and a new account was added with their domain credentials etc... but I began to suspect something when I read a post suggesting that fields like first name, last name, etc. should have been pulled from the AD profile (the fields are indeed populated in the Active Directory).

Also, I'm getting this error when trying to update the provider settings (Domain/Username/password screen).  I reinstalled the provider with the same results...

Error: is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Authentication.ActiveDirectory.ADSI.Utilities.AddADSIPath(String Path, Path ADSIPath) at DotNetNuke.Authentication.ActiveDirectory.ADSI.Utilities.GetRootEntry(Path ADSIPath) at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetNetworkStatus() at DotNetNuke.Authentication.ActiveDirectory.Settings.UpdateSettings() --- End of inner exception stack trace ---

Big thanks! Kel

I  have the same error occuring when I attempt to "update settings", adding Active Directory settings.  This was a fresh install of DNN 4.6.2.  I did check the AD_ProviderTypeName cell and found the entry you mention already there.  Not quite sure where I should go next.

Error: is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Authentication.ActiveDirectory.ADSI.Utilities.AddADSIPath(String Path, Path ADSIPath) at DotNetNuke.Authentication.ActiveDirectory.ADSI.Utilities.GetRootEntry(Path ADSIPath) at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetNetworkStatus() at DotNetNuke.Authentication.ActiveDirectory.Settings.UpdateSettings() --- End of inner exception stack trace ---

Hi Mike,

Thanks again for your help.  I'm drowning a bit with all the various setting combinations.  As I recall from yesterday, this error occurred when entering the domain in the format: dc=domain,dc=org as documented in 33% of the posts on the matter (I see some LDAP, some domain.org too) -- domain.org worked.  I had tried the impersonation setting with positive results (all OKs on the provider configuration page).  Then, I started having other errors, which I remedied by affording access to the account I used in the impersonation string to the .NET framework folders (read to the root of the .net 2.x folder and write to the nested temp directory.  This seemed to work for awhile and then I had problems with the database (I think a user instance issue).  I recall one about the impersonated user needing a local profile (so I logged on my development XP machine with that user to create one).  That worked, then I saw another error maybe 4 minutes later about the database being in use or something.  I can tell you, every time I solved one problem, another would creep up.  I saw the one where  the user is logged off after a random  amount of time (as posted on your project blog -- but I thought fixed in 4.7).

I'm using the new 4.7 (no upgrade).  My goal is to create a company intranet with 100% AD account access.  I don't need mixed mode.  Is there an authoritative procedure for this setup on 4.7 anywhere you can point me to?

Some questions:

1. Should I keep the User Instance=true (web.config) database setup in place with impersonation?  If so, is it normal for me to need to log in as the impersonated user to create a profile?

2. Is the "random log off" bug you highlighted on your project blog still be present in 4.7?

3. Is there a way to gain access to the 1.00.1 (or whatever it was) build of the provider?

Mike, I really appreciate your help...  I know I probably ask questions that are already answered, but compiling info from all these different sources with conflicting information and various versions is, as I know you know, difficult.

Kel