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 ...DNN logins donDNN logins don't work after moving DB to new host
Previous
 
Next
New Post
9/24/2007 2:36 PM
 

Hi pseigers,

Like you I do all my dev work on the Dev machine.  I only update in reverselike that when I am getting ready to do a major change on the live site.  I keep all backups, etc., just like normal, but when I go for an upgrade, say from 4.4.1 to 4.6, like I am preparing to do, then I to a reverse update into a second Dev system, then I migrate all my Dev changes to that system for testing the uprgade to make sure things don't break on the live site setup.  This tests the upgrade against the entire live site setup, all poralt, all users, all content, etc.,

As for logging into the db, my suggestion is that if you can't login to the db on your host, ask your host to login and run that script.  Still though, if you attempt to login through SQL Espress, it should allow you in with the password and username without any problem.  The issue, a I understand it is that the account that permits those logins through the internet is the one that needs correction and is more than likely different.  If you use an SQL management software you should still be able to login normally TO THE DB DIRECTLY. 

It worked for me that way.  Still, if that fails, have your host run that script and it should solve the issue.  If not, then I'm at a loss too.

Clay

 
New Post
9/24/2007 5:23 PM
 

Hi Duncan, see my last (updated) post... I removed one orphaned user, created by myself. But no luck. I still am unable to install a fresh DNN 455 on my host, so this must be attributed to the processes that are needed to install and make DNN work. My host already confirmed that sometimes the install times out, and therefore it crashes later on. The install wizard may need more control over what exactly is going on on the web server, and more importantly, on the db server. I would suggest some kind of sql scripts feedback to the install wizard and keep timeouts out of range by increasing the their delays. Right now my host is taking care of things.... once installed correctly DNN is actually very stable.

 
New Post
9/24/2007 5:33 PM
 

Hi Clay, I see your dev / live structure is a bit more sophisticated than mine , anyways you made your point - I do see the need to set up something similar for myself. Can't be too sure about upgrading successfully.

PD: I use the same login in web.config as I do to connect directly to the DB, using SQL Server 2005 Management Studio Express. I'm going to change that also to separate them.

Thanx for your valuable comment!

 
New Post
9/24/2007 7:09 PM
 

Hi psiegers,

My setup isn't all that sophisticated and to be honest, I still consider myself to be a newbie at all this.  My Dev machine is a laptop and as such is not always net connected.  That is the reason that keeping the two sites synchronized is a problem.  My version is definitely not  "best practices" at all, but it works fine and keeps me from making really dumb mistakes.

The live site, becomes my default "stable" version, and all versions I tinker around with on Dev are a version of the most recent live backup.  That way, everything I work on is being tested, by default, against a total system, not just an "ideal" static system.  It requires a bit of effort on my part to do it this way, but I believe it's worth it. 

Kill your live system with an improperly removed or deleted skin or module once, and you'll never, ever do it again.  TrUUUUUUUUssst me.  Been there, done that, bought the postcards, the bumper stickers, the T-shirts, sunglasses, coffee cup, and I will never ever, ever, ever visit again!  Just the mention of it still sends shudders and chills via special delivery.

OK,,, enough humor for now.  If your host did indeed do a "full restore" from the db you backed up from your Dev, then zipped and emailed or FTP'd to them, then it really should be as simple as gaining access to the db with the Username/ password they assigned it, and running that script.  If you login with SQL Express, that is a direct login and not a login like the site uses with the site's connection strings in web.config, at least as I understand it.

I really hope this all helps.

Clay

 
New Post
10/5/2007 12:14 PM
 

Hi again all,

I'm bumping in once again with the problem of not being able to login in DNN - none of the DNN logins work (see my first post).

My scenario is this:

- we created a new package on the same host

- I made a copy of the local website and DB (after modifying the image paths to the new one)

- I uploaded the zips using FTP and unzipped the website in a folder using Panel admin's unzip facility

- I changed the web.config connectionstrings, left the rest like it was (it can be a machinekey issue, but how to check that if you don't have one and are not able to install another copy of DNN)

- I checked DB access through SQL Server 2005 Management Studio Express, worked fine

- I then changed the http alias in the table PortalAlias

- I changed the ASP.NET from 1.1 to 2.0 and assigned Write permissions in Panel admin

- after that it worked fine but the DNN logins NOT!!!

What can be the cause of this weird issue? Sorry but I just don't get it.

Many TIA for any help, Pieter

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN logins donDNN logins don't work after moving DB to new host


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