Last post Feb 28, 2006 11:18 AM by pauldes
Feb 26, 2006 03:39 AM|pauldes|LINK
I have a DNN site, 4.0.2, and sql database that I developed locally. Add some modules, tables, etc. All is working fine. So I go to my host, copy all my files, backup my local DB and restore it on the remote SQL server.
So I bring up the site remotely, it comes up fine. When I go to login in as Admin or Host on the remote server, I get the "Login Failed, remember that Passwords are case sensitive" error.
What could be happening?
Feb 26, 2006 12:24 PM|Shadowpdx|LINK
Did you remember to add a portal alias for the new site? A bit more info would help.......I am guessing here.
Feb 27, 2006 11:09 AM|pauldes|LINK
Yes, all the portal aliases are set up right. There is NO information to provide unfortunately. No logs, etc. as I couldn't log in. I've found a work around and here is what I did.
Manually creating a super user or host account.
You must at least be able to register on the site and have access to the DNN database for this to work.
1. Regiister a new user on your site
2. select * from users table where username = (new registered username), record the userid value. Set IsSuperUser = 1 where userid = (userid value)
3. delete from userroles where userid is the userid value in step 2.
4. select applicationid from aspnet_applications where applicationname = (-1). Record the applicationid value.
5. select userid from aspnet_Users where username = users.username. Record the userid value.
6. set IsApproved = 1 , set applicationid = aspnet_applications.applicationid found in step 4 from aspnet_membership where userid = aspnet_users.userid recorded in step 5
7. Log in to your portal with the new super user account.
Feb 28, 2006 12:02 AM|smehaffie|LINK
Feb 28, 2006 12:33 AMemail@example.com|LINK
Another workaround if you have simple SQL server access is to just create a new user and T-SQL update your old admin password and salt with the encrypted strings produced by the new user creation and the password will be exactly the same as the new users.
Feb 28, 2006 01:08 AM|kat_attack|LINK
I experienced the exact same problem and it was not a host/local install issue.
These are the steps that triggered my lockout problem:
1] Clean install DNN 3.1
2] Login as Host
3] Set Host user account properties (email address, country etc)
4] Changed Password (yes I wrote it down so it isn't me forgetting it)
5] Logged out
..... tried to get back in.... NO GO... ahhhh
Feb 28, 2006 11:18 AM|pauldes|LINK
Did you copy the DNN files from the direcotry the original install was done from, or from a clean install directory. The reason I am asking is that it sounds like the following keys got changed.
I don't think it was this issue. I copied the web config directly from my local to my host, then just edited the SQL connection string. Am I missing something?