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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...2.12 to 3.nn Login Problems2.12 to 3.nn Login Problems
Previous
 
Next
New Post
8/12/2006 1:52 PM
 

I'm trying to upgrade a 2.12 installation to 3.nn (I've tried 3.0.13 and 3.1.1 from suggestions in different posts).  The upgrade process always seems to go fine with no errors.  I can even get to the home page and login page with no errors.  When I try to logon with any userId/password it says the the login is invalid.

I've searched several forums for two days and tried many things but nothing seems to work.  The only solution I see in any of the forums is to copy the old MachineValidationKey, MachineDecryptionKey and objectQualifier sections from the old web.config.  The only problem is that the web.config from 2.12 had no MachineValidationKey, MachineDecryptionKey keys to copy and the objectQualifier was set to "".

Is there anything else that I am missing?  This has been driving me crazy for the past 2 days.

 
New Post
8/13/2006 7:22 PM
 
The machine key doesn't get set until after the first 3.x install. If you then upgraded to 3.1.1 it is possible you overwrote these values. FYI, I have done 2.1.2 upgrades and took them directly to 3.2.2 without a problem. (Aside from custom modules, but that was to be expected)

Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
8/14/2006 4:34 PM
 

Crispy wrote
The machine key doesn't get set until after the first 3.x install. If you then upgraded to 3.1.1 it is possible you overwrote these values. FYI, I have done 2.1.2 upgrades and took them directly to 3.2.2 without a problem. (Aside from custom modules, but that was to be expected)

Thanks Crispy.  I'm not trying to go from 2 to 3.0.13 and then to 3.1.1 though.  I've tried upgrading directly from 2.1.2 to each version independently.  I can't log in right after the upgrade from 2.1.2 to whatever version of 3 I go to.

Correct me if I'm wrong, but the machinekeys don't actually get "set" during an upgrade do they?  They are just "there" in the release.config when you rename it to web.config.  That's all I am doing, of course then I go in and change my connection string info.  My 2.1.2 web.config was all the stock version so I'm not actually merging my old with my new.  I'm just using the new.  Maybe I'm wrong about this, but that is my understanding of it.

 
New Post
8/18/2006 6:08 PM
 

Bump...

Anybody?  It's been a week and I'm still stuck on this.  :|

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...2.12 to 3.nn Login Problems2.12 to 3.nn Login Problems


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