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 failedActive Directory login failed
Previous
 
Next
New Post
10/30/2013 10:44 AM
 

Hello,

I have two servers, one production and one test/development server both with Windows Server 2008 R2 Service Pack 1 and latest DotNetNuke version 7.1.2. Both should be identically configured but I can not guarantee this, because I am not the only one with admin rights on both servers.

After update from 7.1.0 over 7.1.1 to 7.1.2 Active Directory authentication does no longer work on the production server but still works on test server. Both servers had AD provider 5.0.4 installed. Configuring the AD Provider did work on prod server and I got the list of domains in the AD forest when saving the configuration. When opening the configuration again, not all configured fields were filled, but I could find the field values in the database table. On test server there were no configuration errors. It was not possible to log into prod server using a AD account "Login failure" in log. And  page load exception after that

AssemblyVersion:7.1.2

PortalID:0

PortalName:#######

UserID:-1

UserName:

ActiveTabID:55

ActiveTabName:CPS Home

RawURL:/cps/CPSHome/tabid/55/ctl/Login/language/en-US/Default.aspx?returnurl=%2fcps%2fen-us%2fcpshome.aspx

AbsoluteURL:/CPS/Default.aspx

AbsoluteURLReferrer:http://###.###.net/cps/CPSHome/tabid/55/ctl/Login/language/en-US/Default.aspx?returnurl=%2fcps%2fen-us%2fcpshome.aspx

UserAgent:Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0; xs-eCIgvjYC69s;iwNdAU)

DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID:66d0f3c8-e1af-4cf0-8c2f-51588bdcd0f2

InnerException:Object reference not set to an instance of an object.

FileName:

FileLineNumber:0

FileColumnNumber:0

Method:DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.SynchronizeRoles

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.SynchronizeRoles(UserInfo objUser) at DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.AuthenticateUser(UserInfo objUser, ADUserInfo objAuthUser, UserLoginStatus& loginStatus, String ipAddress) 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.LinkButton.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

 

Source:

Server Name: #######

I updated AD provider to 5.0.5 but I still can not login using an AD account on prod server.

Many THX for any kind of help solving this problem.

Rainer Kroos

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationActive Directory login failedActive Directory login failed


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