Hello all,

I am running dnn 3.2.2 on a windows 2003 server running iis 6.0.

Windows authentication seems to be working fine except for 1 user (or that is the only person who has reported to me).

I investigated on the PC that was having problem and the user was being asked to logon to server and after login was able to open dnn portal.  I tested several times and later on the user was only going to login for dnn - so was not being logged in and authenticated by dnn.

I then deleted user account from dnn and tested login on users PC and another PC and came up with totally different scenario.  The following error message appeared

Server Error in '/DotNetNuke' Application.
--------------------------------------------------------------------------------

Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.HttpModules.DNNMembershipModule.OnAuthenticateRequest(Object s, EventArgs e) +1067
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +60
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87

 I have created test user on active directory and authentication is working.

Is this a problem with user account on active directory or some type of corruption in the authentication process?
Any advice or help would be greatly appreciated

Regards

Peter M
Bendigo Australia

Roberta,

I deleted cookies, tried accessing on another PC(using users login).  Still getting the same error message. 

I have checked the logs - nothing is out of the ordinary or different from other users.   The problem seems to be with windowsignin.aspx.  I have another dnn website on my test server - with identical setup of authentication and user is authenticated on this PC.

Please help

Regards
Peter M

Bendigo Australia

Update:

Renamed the original Active Directory account to username_new and authentication to dnn worked.

Seems the either something on server is caching original AD name or authentication process on DNN is caching somewhere.  I have done an IISRESET (thought this would have cleared any cached items in app pool).

Anyone have any ideas?

Thanks

Peter M
Bendigo