Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...CanCan't login after migrating DNN to new server
Previous
 
Next
New Post
2/26/2008 1:44 PM
 

I tried researching this, but couldn't find a solution as of yet.

I moved DNN from one production server to another and now no users/admins can login to the DNN installation.  This affecting DNN 2.x, 3.x and 4.x sites.  I believe it is an issue with the machinevalidationkey and machinedecryptionkey being different between servers.  I have already fixed the admin/host accounts with a post I found,  but am not sure how to fix the issue so that I don't have to reset all the users passwords.

 
New Post
2/26/2008 5:50 PM
 

Josh,

you need to keep your previously used machineencryptionkey.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/26/2008 5:55 PM
 

josh a good idea when migrating would be to run a merge application on you old web.config and your new one.
I just went through a similar process on a major installation we have running and this was one of the first issues I encountered.


John Nicholson
 
New Post
2/27/2008 2:15 PM
 

John,
All I did was to physically copy the root DNN folder from one server to another (different server names).  I then modified the web.config servername in the connection string - that was the only thing changed. 

Sebastian,
Do you mean the machineKey decryptionKey and validationKey?  On the websites I moved those are the same values as in the old web.config, but are of course different from DNN sites already existing on the new server.

 
New Post
2/27/2008 2:51 PM
 

Nice to see you around, Josh... welcome back ;)

For some who may not realize... Josh is the "Alex Shirley" of versions 1.x and 2.x!

Josh, it sounds like you are merging one set of files with another database?  If I read that correctly, this means that you need to be using the keys from the OLD web.config file... not the new one you are copying in.  The purpose of these keys is to enable encryption and decryption of data that is ultimately stored in the DB.  By changing that in web.config (to the newer one), you render all the old passwords inoperable because they will not be decrypted properly.  Similarly... any NEW ones will appear to work, but once you reapply the OLD key, they will be rendered inoperable because the old key won't decrypt them properly.  You need to resolve this as quickly as possible to avoid additional data loss.  Encryption/Decryption keys, once set (in web.config) should never be changed.

Cheers


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...CanCan't login after migrating DNN to new server


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out