Can't login after restoring DB to production

Last post 09-02-2005 1:17 PM by jksanford. 4 replies.

Sort Posts:

  • Can't login after restoring DB to production

    09-01-2005, 1:10 PM
    • Member
      125 point Member
    • jksanford
    • Member since 03-02-2003, 7:13 AM
    • Posts 25
    Hmm. I'm kinda stumped, and was wondering if anyone could point me in the right direction...

    I have a DNN 3.1.1 install on my laptop that I've been using to 'sandbox' a site.  Everything works fine on the laptop. Now, my challenge:

    1)  I bought a webhost4life account, ftp'd everything up, let the installer build a new DNN 3.1.1 enviornment, etc.  
    2)  I backed everything up from webhost4life.
    3)  I went to my laptop dnn and included the portal name that was in the webhost4life dnn site into this sandbox
    4) I backed up the laptop dnn database and restored it over the webhost4life db.
    5) My site shows up (except for the images), but I can't login.  I've clicked the send password button, and the smtp info is setup (I was thinking maybe it thought my password was different or something).

    Any ideas?

    Thanks in advance
  • Re: Can't login after restoring DB to production

    09-02-2005, 8:04 AM
    • Member
      125 point Member
    • jksanford
    • Member since 03-02-2003, 7:13 AM
    • Posts 25
    Does this have something to do with the machine keys?  I'm trying to find docs on how the password works.  I should be able to have an area to setup the website, then restore the db to production, right?  Was I supposed to copy over the whole site structure in addition to the db?  The site comes up, and I was able to register a new user, I just can't login with the old user accounts.

    Maybe I'll restore the original db and see if I can login...

    James
  • Re: Can't login after restoring DB to production

    09-02-2005, 10:23 AM
    • Contributor
      5,570 point Contributor
    • DeveloperMCDBA
    • Member since 05-08-2005, 8:08 AM
    • Deltona, FL, USA
    • Posts 1,114

     jksanford wrote:
    Hmm. I'm kinda stumped, and was wondering if anyone could point me in the right direction...

    I have a DNN 3.1.1 install on my laptop that I've been using to 'sandbox' a site.  Everything works fine on the laptop. Now, my challenge:

    1)  I bought a webhost4life account, ftp'd everything up, let the installer build a new DNN 3.1.1 enviornment, etc.  
    2)  I backed everything up from webhost4life.
    3)  I went to my laptop dnn and included the portal name that was in the webhost4life dnn site into this sandbox
    4) I backed up the laptop dnn database and restored it over the webhost4life db.
    5) My site shows up (except for the images), but I can't login.  I've clicked the send password button, and the smtp info is setup (I was thinking maybe it thought my password was different or something).

    Any ideas?

    Thanks in advance

    yeah, what he said...the machine keys. Hopefully you still have the old ones like I did: http://forums.asp.net/1039876/ShowPost.aspx

     

  • Re: Can't login after restoring DB to production

    09-02-2005, 11:30 AM
    • Contributor
      2,238 point Contributor
    • alexdresko
    • Member since 06-04-2004, 7:48 AM
    • Easley, SC
    • Posts 463
    If you already have it set up and working fine on your laptop, you should upload your local copy of the site instead of forcing DNN to reinstall on the production server. There are plenty of threads on here with instructions on how to do that.
    Alex Dresko
    I'm not a player, I just code a lot.
  • Re: Can't login after restoring DB to production

    09-02-2005, 1:17 PM
    • Member
      125 point Member
    • jksanford
    • Member since 03-02-2003, 7:13 AM
    • Posts 25
    Thanks Alex.  I only let dotnetnuke install the very first time on production.  Since it was hosted at webhost4life, I figured letting it just run through the install might make it 'happier' in that environment and cause me less headaches with the portal alias setup.  Once it installed, I wrote down what it created as the alias and added it to my laptop install's dnn so that I wouldn't get stuck.  

    Thanks for taking the time to respond!

    James
Page 1 of 1 (5 items)