Checked the DB three times now, every table that made sense, and some that didn't.

Still no invalid email. Since this is effecting all log ins, including log ins to the child portal, I suspect that the issue lies at the hosting level.

Let's assume for  a minute that I not an idiot, (big assumption, I know), and that the problem isn't an invaid email.  What changed between version 4.3 and version 5.1that would triger the need for the email address? Would any of the upgrade steps have altered the email addresses or start looking for it in another table or field?

Since I've already started on an new instance of , this is more of an acedemic exercise for me at this point.  I just hate to be stumped.

And if you DO think I'm an idiot, join the club.  They meet every Tuesday.  My wife is the president, and if you join now you get a free T-shirt and bumpersticker!

I had the same problem, in my case both the host and admin accounts had the same email address which violated the "requiresUniqueEmail=true" setting in my web.config. I changed this to "false" and was able to login.

Paul

If you look at the error message that was supplied, you'll notice that it is in the Authentication Provider. The problem is that the email address for that account is a duplicate in the aspnet_Membership table and you probably have requiresUniqueEmail=true. The two solutions are: 1) Remove the Unique EMail requirement 2) Remove the duplicate account from the aspnet_Membership table (or change one of the email addresses)