I'd bet real money that you failed to copy the machineKey setting from your old web.config to the new one.

Hopefully, you made a nice backup before you did the upgrade, and you can look in the old web.config, copy the machineKey setting, and paste it into your new web.config.

If that is not the reason, ask for more help.

Hi jncraig,
You just won your bet !
I coppied the Machinekey over and login is ok now - Thanks a million!)

Cheers
glen

That one's almost too easy. So ... you only owe me half!

Hopefully you guys are still floating around somewhere...

I'm not programmer... Just a lowly author/trader running DNN... From all of the forums I've searched this thread seems to have the most direct, regular people answers yet!

Anyway, I recently upgrade my extensions and the Active Directory and Card Shark files dotnetpuked...

After spending five hours figuring out how to use SQL (not exactly intuitive for non-programmers), I was able to repair the Critical Error...

Now, I'm getting the same "Login Failed" error as above... I can register a user, but can't login... I tried registering a user and then converting that user (via SQL, though while logged in through the browser) a superhero, I mean super user... But obviously, without logging out, the admin and host settings won't show up... I've plundered the web.config file trying to follow the code, while checking to see if the appropriate files were in the right places via my ftp...as logically as I could.

Alas, I am defeated - sorely.

The machine key thing sounds like it could do the trick... Before bothering Los Grande Programmers such as yourselves, I read up on the whole machine key business (http://msdn.microsoft.com/en-us/lib...8288.aspx) and can only say, I fear I'm going to screw up the old (and new) web.config file jumping in...

It's a little lowbrow I know, but is there any way one of you fellers would be so kind as to fire up a screenshot showing where the actual key to the universe, I mean, machine key is in the web.config file?

With infinite gratitude,

Mark
www.wallstreetrockstar.com

I suspect that your problem is related to NOT having copied the machineKey from your old web.config to the new one when you did the upgrade.

You need to get that old setting and copy it into your current web.config. 

Now ... the good news is that you'll never have that problem again.  After you have upgraded to any version past 4.6.2, all future upgrades do not require manual adjustment of the web.config file.

Now, as to where the machineKey lives ... see the attached file.  It's the 62nd line in this particular copy of web.config.  But ... the key is specific to your installation.  That's why you need your old web.config.