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 ...Can't logon (404 error)Can't logon (404 error)
Previous
 
Next
New Post
7/22/2012 3:00 AM
 

I have a fresh installation over which I have restored a copy of my production server database. I can browse the site, etc just fine. However, when I try to logon (http://localhost/login, which I can do on the production server just fine) I receive a 404 error:

"The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."

Which is a bit of a showstopper! Any ideas on how I can fix this? I am running 6.0.1.

Thanks.

Mark

 

 
New Post
7/22/2012 3:22 AM
 

I fixed this by navigating to http://localhost/ctl=login. I still can't logon but have a different issue now (the username/password I use on the productions site isn't working on this site, even though I am using a restored database). I will look into that and open a separate thread if I can't figure that one out.

 

 
New Post
7/22/2012 9:14 AM
 
Did you restore the files from the old site, especially the web.config file?
If not then this is the cause of the problem. The web config file contains a key used for password encryption. If the same key isn't used then the old password won't work.
If you still have access to the old web.config copy that to the new site. Rember to ensure the SQL connection string is updated for the new site.
If you don't have the old web.config then look at http://www.dotnetnuke.com/Resources/Wiki/Page/Recover-passwords.aspx on ways to regain access to the website.

When backing up and restoring a DNN install its usually preferable to back up both the database and files as not everything is in the database. Most of the time when restoring both the only items you have to remember is to change the SQL connection string in the web.config and ensure a portal alias exists in the database for the new site location.

HTH
Antony
 
New Post
7/23/2012 10:53 AM
 

Thank you, Antony. I actually thought I had restored both my database and the files (with an edit to the web.config file) but it seems I got confused somewhere along the line. I fixed the machine key and all is well. Thanks for your help.

Mark

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Can't logon (404 error)Can't logon (404 error)


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