Thanks for the reply.
So in order to work on this issue, I have done some more troubleshooting.
I realized that while I have other sites working on this box I dont have other 6.0 sites working on this box.
I installed a fresh 6.0 install, fresh database, no content, no modules, nothing except AD authentication.
I'm getting the exact same error.
AD Users can login ONCE! User object is created. Then any subsequent login attempts it will simply sit at the login prompt and do nothing after pressing login. No error messages to the client.
Server is Windows 2008 R2 (no SP1, installing that tonight)
Here are the messages from the DNN error logs, same as before:
AssemblyVersion: 6.0.0
PortalID: 0
PortalName: SA DNN DEV
UserID: -1
UserName:
ActiveTabID: 55
ActiveTabName: No
RawURL: /login.aspx?ReturnUrl=%2f&popUp=true
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://sa-dnndev/login.aspx?ReturnUrl=%2f&popUp=true
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 4466b271-806f-42ba-8ba2-108ab84a3811
InnerException: Value cannot be null. Parameter name: oldPassword
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.Security.MembershipUser.ChangePassword
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Value cannot be null. Parameter name: oldPassword ---> System.ArgumentNullException: Value cannot be null. Parameter name: oldPassword at System.Web.Security.MembershipUser.ChangePassword(String oldPassword, String newPassword) at DotNetNuke.Security.Membership.AspNetMembershipProvider.ChangePassword(UserInfo user, String oldPassword, String newPassword) at DotNetNuke.Entities.Users.UserController.ChangePassword(UserInfo user, String oldPassword, String newPassword) 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.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:
Server Name: SA-WEB1
Here's what the line for that user in the aspnet_Membership table looks like:
| e53be025-1bc6-47f4-ac30-edac43b35545 |
66b55d2b-1b8f-40b9-b946-9dbead015a83 |
v+ej1f5npzm5555555Od12X1CExT555555Z64ZIcdx3Kx555555lgeskGwuw9zm8K4FT86GI5YUuxJ/ZmfWH |
2 |
wP5555eQPwc555/A5= |
NULL |
xxx@uoregon.edu |
xxx@uoregon.edu |
NULL |
NULL |
True |
False |
2011-08-11 16:43:54.000 |
2011-08-11 16:43:54.000 |
2011-08-11 16:43:54.000 |
1754-01-01 00:00:00.000 |
0 |
1754-01-01 00:00:00.000 |
0 |
1754-01-01 00:00:00.000 |
NULL |
Here is what the line for that user looks like in the aspnet_users table
| e53be025-1bc6-47f4-ac30-edac43b35545 |
66b55d2b-1b8f-40b9-b946-9dbead015a83 |
ad\xxx |
ad\xxx |
NULL |
False |
2011-08-11 16:43:55.677 |
Here is the entry from the Users table
| 3 |
ad\xxx |
Mxxx |
Bxxx |
False |
NULL |
xxx@uoregon.edu |
Mxxx Bxxx |
False |
xxx.171.76.124 |
False |
-1 |
2011-08-11 09:43:54.760 |
-1 |
2011-08-11 09:43:56.197 |
Is there any other information I can give you that might help you to pinpoint the cause.
I notice there is one other thread that is complaining about this similar problem - users can login once, then cannot login again.
Again, the server is WIndows 2008 R2 Standard, no service pack 1
Sites application pools are running in ASP.NET 4.0, integrated mode
AD authentication does work with 5.06.03 sites using the 5.0.2 provider on the same machine.