Dec10Written by:slhilbert
12/10/2008 8:11 AM 
Every now and then I see in the Dotnetnuke Forums that people are no longer able to login to their Dotnetnuke websites. This usually occurs after they upgrade their website or because they have moved the location of the login page. I thought I would put down a quick list of some issues and solutions to them.
If you are unable to login to your site after performing an upgrade the chances are very good that you didn't copy the MachineKey from your old Web.config to the new one. Dotnetnuke uses the machine key to encrypt passwords so if you have the wrong MachineKey in your Web.config then you won't be able to login because your password will always be wrong.
The second thing that happens often is that people change the location of the Login page through the Admin Settings. By mistake they change the page to a page that either 1.) doesn't have a login module on it. Or 2.) The page can't be accessed by unauthenticated users.
If for some reason you can still access the admin menu then you can fix this by:
Going to Site Settings, Advanced Settings, Page management, Login Page and selected 'none specified'.
If you can't login to the site then you are going to have to correct this through the database by doing the following:
Go to the Portals table and make sure that the LoginTabID is set to Null.
Please post in the comments your tips and tricks regarding login issues.