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 ...Hooking the DNN site to different DNN database , caused errorHooking the DNN site to different DNN database , caused error
Previous
 
Next
New Post
6/13/2007 1:18 AM
 

 

I tried attaching a DNN database (from another DNN site) to a DNN site which already was functioning with different DNN database, which affected login to the DNN web site.(host/dnnhost)

 
Login Failed, remember that Passwords are case sensitive
 
 Any help would be highly appreciated........
 
New Post
6/13/2007 1:27 AM
 

You'll need to copy the machinekey values from the other web.config as well, otherwise DNN won't be able to properly encrypt/decrypt passwords, thus you can't login.


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
6/28/2007 4:13 AM
 

I have tried to copy my production database from a hosting service to my local machine, and would like to be able to point my local copy of DNN (same version) at this copy.  Aside from the sql connections which now point to my local copy of the database, there appear to be pointers inside the database tables that also affect my ability to do this.  The HostSettings table contains a HostURL that points to the original site where the database came from, and the PortalAlias table also points to the original URL.  When I change these to point to my localhost/CopyOfDNN web site, it still refuses to run, and I get just a generic error page.  This is version DNN 4.4.1 if that makes a difference. 

The web.config file contains the machinekey / validationkey / decryptionkey values that were in place on the original server, and  I have validated that the login / pwd have access to the database just fine.

Do you have any ideas on what else could be the problem?


Gene W
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Hooking the DNN site to different DNN database , caused errorHooking the DNN site to different DNN database , caused 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