Hello,

I have successfully completed an manual upgrade to DotNetNuke v. 4.3.2.  I am unable to login with the traditional admin/admin or host/host combinations. 

After research the various forums that I am a registered member of, it seems the the admin/admin has changed from to admin/dnnadmin, or dnnadmin/dnnadmin.  Obviously these are username/password combinations.  I have tried various combinations of the above mentioned username/password and have had no luck.

Any information or assistance would be appreciated.

Thank you,

Tony Ventura 

I'll ask a quick question because I know Lee will ask this.

Did you try doing this on your local install first before doing this on your production machine to make sure there were no problems?

For other readers*************************************

My observation. 4.3 came out just a couple of weeks ago and they are already are on a second rev? You might want to rethink this upgrade until its stable. I don't know if you can revert to 4.03 but it is stable without any major problems I know of. When they announce that 4.3.X is the stable release then and only then you can use it. The coders that are writing DNN should be commended for their hard word but end users need to be reminded that DNN 4.X is a new platform with many new features. Changing one class can affect many others. Imagine the hurdles these guys are trying to accomplish with over 100K of installs. Just be patient. It will be out of the Beta in a short amount of time. But as warned about in many posts on this forum alone, it is a BETA and putting it on a production machine is careless at best.

To get the username:

Fire up your SQL Server manager, navigate to your Production Server ==> Databases ==> DotNetNuke db ==> Tables ==> Users

for Users table, rember to right-click and select "return all rows"

look for the Account with the Username where IsSsuperUser = 1. (note the userID number)

close table and open table UserRoles.

if the admin userID expiry date has passed, you'll never get in.

this may not fix the problem, but it may tell you what it is...

Hi Tony,

The other problem you may have is from not copying across the details needed in the web.config file correctly, mainly:

• Transfer from your server web.config file the settings to the release.config file, covering:
• <add key="SiteSqlServer" value="Server=7.8.2.1,23;Database=audio32xT;uid=Myuid;pwd=usm38fTJ;" />
• <add key="MachineValidationKey" value="DB02CB97BAE1814E49F1310895EC33B22FC70014" />
• <add key="MachineDecryptionKey" value="6E324A6FF2B87D590B71D61FDD95C82A137C980893117CF0"/>
• <add key="InstallationDate" value="11/19/2005" />

There is a tutorial for upgrading v3.x here:
http://www.dnncreative.com/tabid/20...fault.aspx

this is the basics for upgrading which you will be able to apply to a DNN4.x installation. Thanks,

I have actually noticed with brand new DNN 4.3.2 installs that some VERY strong password combinations cause problems.  For example when you first create a new DNN 4.3.2 portal the username password combinations are admin/dnnadmin and host/dnnhost.  It will allow you to change them to a very secure, strong password and you will stay logged in.  However with certain passwords, once you log out, you cannot log back in.  I reinstalled and created other Super user accounts and experimented with password, "weakening" them until I was able to successfully login and then changed the host and admin accounts passwords appropriately.  It seems to be a bug with the encryption methodology used to encrypt the passwords that does not correctly work with certain very, strong passwords.

Were you using a very strong password in the the portal you upgraded?

Hello Kaminari,

This sounds very interesting, could you provide further information on the experiments you have done? Which passwords cause problems and which passwords are ok?

Thanks,

Lee

I've got the same problem which was corrected after copying validationKey and decryptionKey from the older  web.config file to the newer web.config file.