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 ForumsAuthenticationAuthenticationActive Directory Login problemActive Directory Login problem
Previous
 
Next
New Post
4/26/2011 11:41 PM
 
Whenever a user tries to login with AD, they get "A critical error has ocurred.  Object not set to an instance of an object."

The DNN Event Viewer shows

AssemblyVersion: 5.6.2
PortalID: 0
PortalName: Gray-ICEB
UserID: -1
UserName:
ActiveTabID: 36
ActiveTabName: Home
RawURL: /login.aspx?ReturnUrl=%2fdefault.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.gray-iceb.net/login.aspx?ReturnUrl=%2fdefault.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; Trident/4.0; .NET CLR 1.0.3705; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 910f4910-f305-4dcc-b852-14bce4c933b2
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.RandomizePassword
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: 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.AuthenticationController.RandomizePassword(UserInfo objUser, String& strPassword) at DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.ManualLogon(String UserName, String strPassword, UserLoginStatus& loginStatus, String ipAddress) at DotNetNuke.Authentication.ActiveDirectory.Login.cmdLogin_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---


Any help would be appreciated.
 
New Post
4/27/2011 10:34 AM
 
Has anyone ever been able to login? Does this happen on manual logins, automatic logins, or both? Have you tried using impersonation in your web.config (that seems to fix about 95% of the problems people have)?
 
New Post
4/27/2011 11:27 AM
 
This dnn site was upgraded to 5.6.2 from 4.5 in steps.  AD sync was working perfectly on DNN 4.  After upgrading to dnn 5, the AD provider was installed.  After configuring the AD provider in extensions, it displays all green OKs at top of extension settings page.  Users who were previously synced in DNN 4 still auto login properly, but all new users and users whose passwords have changed get the error above.  This error ocurrs both for automatic login and manual login.  I have tried adding impersonation to the web.config - no change.  I have tested AD access using the ldpabrowser tool as you recommended in another forum post.  The account has access to AD successfully.

Thank you for your assistance. Hope this information helps.
 
New Post
4/27/2011 5:54 PM
 
Hmmm, you're the second person in the last week that's had an issue going from 4.5 to 5.x. I'm pretty sure the problem has to do with going through 3 different versions of the provider. Below 4.6 it was part of the core code and was separated out to be a standalone provider for the 4.6 release. Then when DNN 5 was released there was a change on where the settings were stored (they moved from the ModuleSettings to the PortalSettings table.

Is it possible to setup a secondary DNN site and get some of your users who are having problems try to login in on there? That'll narrow down whether it's something that changed in the 5.0.2 version or something else.
 
New Post
4/29/2011 2:01 PM
 
I have setup a clean blank dnn 5.6.2 install with the AD authenticator.  It works perfectly.  Users authenticate properly with no errors.  It is configured with the same settings as the site receiving the error. 

Any thoughts on how the upgrade process caused the issue and how to fix it?
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationActive Directory Login problemActive Directory Login problem


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