Thread: After upgrade to 5.0.1 Email Supplied is Invalid err on login

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...

?Kevin, there have been hundreds of changes sind DNN 4.3, one is a regular expression to validate email addresses. there might be a case, if the email address does not follow typcal standards, that a valid email address is not rcognized. Do you have some special address used? Sebastian Leupold        

Just an update to this issue to help others that might come across it. I just had the same problem and it was indeed the requiresUniqueEmail setting and I had two accounts with identical email addresses. When I changed one of them directly in the database I was able to log in. To check for duplicates you can run the following query: select email, count(*) from users group by email having count(*) >1 Richard Edwards www.dnnstuff.com...

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

Hi, I have the same problem but I think if I change requiresUniqueEmail=true to false isn't a right way. Any idea? Marco

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)