Hi

I've been using the AD provider for a couple of weeks now on a development machine and it seems to have been working well. Although I've now got to the point were I need to make the site live and i've been experiencing some logon problems with certain users.

I'm pretty sure that every thing has been setup correctly. I've added the site into the intranet zone, and removed anon. logon from the windowssignin.aspx page.

When some users open up the site they don't automatically get logged on. So I tried to direct them to the windowssignin.aspx page, and I get an error about Object Reference not set to an instance of an object error.

This is the output from the event log:

AssemblyVersion: 04.09.00
PortalID: 0
PortalName: LowriBeck Intranet
UserID: -1
UserName:
ActiveTabID: 36
ActiveTabName: Home
RawURL: /lbintranet/DesktopModules/AuthenticationServices/ActiveDirectory/windowssignin.aspx
AbsoluteURL: /lbintranet/DesktopModules/AuthenticationServices/ActiveDirectory/windowssignin.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 491d34b9-05c3-4432-8a1f-8b041364c99a
InnerException: Unhandled Error:
FileName: C:\Inetpub\wwwroot\DNN-4-9\Library\Providers\MembershipProviders\AspNetMembershipProvider\AspNetMembershipProvider.vb
FileLineNumber: 518
FileColumnNumber: 13
Method: DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUserMembership
StackTrace:
Message: System.Exception: Unhandled Error: ---> System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUserMembership(UserInfo user) in C:\Inetpub\wwwroot\DNN-4-9\Library\Providers\MembershipProviders\AspNetMembershipProvider\AspNetMembershipProvider.vb:line 518 at DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUser(UserInfo user) in C:\Inetpub\wwwroot\DNN-4-9\Library\Providers\MembershipProviders\AspNetMembershipProvider\AspNetMembershipProvider.vb:line 1366 at DotNetNuke.Entities.Users.UserController.UpdateUser(Int32 portalId, UserInfo objUser) at DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.SynchronizeRoles(String LoggedOnUserName, Int32 intUserID) at DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.AuthenticationLogon() at DotNetNuke.Authentication.ActiveDirectory.WindowsSignin.Page_Init(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.Page.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace --- at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP.desktopmodules_authenticationservices_activedirectory_windowssignin_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---
Source:
Server Name: GFROD-DEVTEST01

Any help would be appreciated.

Thanks

I had impersonation enabled, in the web config, and like you say it was only occurring for a few users. It seemed to be users on Vista machines but don't think that was the issue.

I tried creating a brand new install of a DNN site with no customisation apart from implementing the AD authentication and tested this on the machines that I was having problems with, and it worked. So I just re-created my site within this new DNN site and it all seems to be working fine at the moment.

I'm not sure why I was having the issues that I was having but I know that I had a bit of a knightmare getting rid of IE8 from my machine last week, so maybe that caused an issue.

It seems to be ok at the moment though.

Thanks

Martin.

Ok I think i'm getting somewhere.

It was a requirement of our intranet that every user should be present in the database when it went live, without the need for everyone to log on as we have a searchable staff directory that queries the user table. This wouldn't work too good if you only appeared in the directory if you had logged on.

So in true "it seemed like a good idea at the time" fashion I created an automatic import from AD module. This seems to be the problem. If I remove the user from the DNN db then the AD provider works. If I add the DNN user using my import page, then try to auto login this breaks the AD provider. Joy.