I am running DNN 3.2.2.  I had AD working, but then about 2-3 days ago, it just stopped.  Coincidentally, it just happened to stop working after I added a new module to DNN through the Host|Module Definitions menu.  However, I had not actually added the new module to any pages.  On the final Update/Save (whatever the link is to upload a new module) is when the problem started.  I got and still get the following error message:

[ArgumentOutOfRangeException: StartIndex cannot be less than zero.
Parameter name: startIndex]
   System.String.Substring(Int32 startIndex, Int32 length) +118
   DotNetNuke.Security.Authentication.Configuration..ctor() +177
   DotNetNuke.Security.Authentication.Configuration.GetConfig() +70
   DotNetNuke.HttpModules.AuthenticationModule.OnAuthenticateRequest(Object s, EventArgs e) +25
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +60
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87

Since then, I have deleted the module from DNN and not surprisingly, it makes no difference.

Now, if I comment out the following line in web.config to disable AD, DNN works just fine and I can login with host/admin.  But if I keep the line in, I get that error message.  Here is the web.config line I am referring to:

<add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" />

So, anyone know what is wrong?

Thanks.
 

dotnetnuke\Components\Authentication\Configuration.vb is where that module is located on my 3.2.2 source installation.  (I've been trying to figure out if a failure to read LDAP is what is causing my woes with the AD support.)

Sorry to hear about the error on your system- that's not something I've seen before, though.  If I had to start tracing, I'd remove the AD from the mix if I could and see if it's integral to the error - go back to Forms and comment out the HTTP module for ADSI even.  Good luck.

Hallelujah!!!  Hallelujah!!!  Hallelujah!!!

First, thanks to all that responded, especially rfreese who sent me the source code I requested.  I now realize that the source code distributon is a different distribution than the install version.

I finally got around to looking at the source code today and examining the dump I posted above.  The problem was that somehow, the admin user's email address was set to "admin".  The code is expecting/demanding an email address with an @ sign in it.  I consider this a bug and will post it in the appropriate place.  The code should handle this problem better.

From the Configuration.vb module, here is the offending line in the DefaultEmailDomain() property:

                Return _portalEmail.Substring(_portalEmail.IndexOf("@"))

Obviously, if your admin user's email address doesn't have an @ sign, you are in trouble here.

I can't really say what the admin's email address was from the begining of my installation, but since my DNN install worked for months, even weeks since the last upgrade to 3.2.2, I will assume it got changed somehow.  Furthermore, although I considered it a coincidence at the time, I now suspect the module I installed when this first happened is the culprit.  Unfortunately, that was long enough ago that I don't remember which module it was.  Darn it.

Also, the error above is what I saw when I had AD turned on and I got it just trying to get to the site.  Coincidentally, and I never noticed this, I also got the same error message, but presented differently, if I had AD turned off and gave the wrong password or an invalid user id.  In this case, the error only occurs when you actually try to login, and it's handled differently.  Apparently the code is catching this exception in this case and just presenting the error message in one of the skin's panes.  You can read more about this scenario in this post:

http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/89/threadid/23110/scope/posts/Default.aspx

Thanks to all those that helped.