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 ForumsAuthenticationAuthenticationAD Provider 0100.03AD Provider 0100.03
Previous
 
Next
New Post
3/5/2008 4:41 PM
 

Hi -

New install of DNN 4.8.1 - all was fine until I got brave and tried to intstall the AD Provider 0100.03 that I dowloaded form dnn.gmss.org...

I used the instructions from the prior version and the install was reported 'successful'.  However, after I went into the authentication settings and clicked on update I got an error.  I was called away and when I came back, DNN had logged out.  Then I couldn't get back in using HOST or ADMIN or even an AD account.  I found in another post about changing the DNN_ENABLED in the table back from false to true, so I did that. 

Now I get this error:

Any help you can give me to get me back to before installing the AD provider would be appreciated....  ThanksDescription: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

Server Error in '/' Application.

Runtime Error

 

 

 

 
New Post
3/5/2008 5:41 PM
 

Rick, open your web.config and go to the section it mentions and turn customErrors to Off. That way you'll get the actual error message which should point you in the right direction.

To get back to before you added the provider:

  1. Open the Authentication table in the database and change IsEnabled to True for the DNN authentication line (should be the first line) and IsEnabled to False for the ActiveDirectory line
  2. In your web.config make sure all instances of <add name="Authentication" type="DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule, DotNetNuke.Authentication.ActiveDirectory" /> are commented out in the <httpModules> section.

That should get you back to where you were before adding the provider.

Could you give more information on the error you found when you clicked on Update on the Authentication page?

 
New Post
3/5/2008 8:42 PM
 

Thanks Mike.  I was able to get it back into it.  Seems like the permissions to the APP_DATA\database.mdf and other files in that folder lost the permissions when I attached to the file in sql visual studio express.  once i reset the permissions it worked.    i removed the AD module, and will try it again, but this was the error i get after the with update on the authentication page;

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

working on this issue, i was surprised to find that DNN is using the app_data\database.mdf file and not the database i created in sql 2005 express...  i thought i had made the necessary changes to web.config before installing.  is it possible to move the database and get it where it should be?

thanks again - rick

 
New Post
3/6/2008 10:51 AM
 

That error is usually generated when you need to use impersonation in your web.config. The documentation covers how to do this.

I've never attempted to move the database from the database.mdf file to SQLExpress. If you haven't done too much to it so far I'd consider just starting from scratch.

 
New Post
3/10/2008 1:39 PM
 

Setting the correct impersonation string did the trick.  I was able to install / configure the ad provider .  Thank you!

Sync appears fine so far - it's bringing over names, addresses, phone number, email.  Is there anyway to get it to syncronize other AD fields - specifically department and title?

rick

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD Provider 0100.03AD Provider 0100.03


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