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 ...Unable to login (Not a skinning problem)Unable to login (Not a skinning problem)
Previous
 
Next
New Post
4/18/2007 1:09 PM
 

I recently made a new installation of dotnetnuke that started without a problem.  I logged in succesfully and added some pages, etc. and everything functioned as usual (this is my sixth installation).  Eventually after a period of inactivity, my session timed out and I attempted to login again as host.  At this point I received an error that my password was incorrect.  I know this is not the case because the password was cut and pasted from its original source.  The same was the case for the admin password.  I attempted to have the password emailed because that seemed to be the next logical step and I received an error that the password could not be emailed.  Does anyone have any next steps for troubleshooting this problem?

 
New Post
4/18/2007 1:54 PM
 

Did you happen to copy any files over after you went inactive? Perhaps the web.config?

I have not seen any reports of this behavior unless the machine keys are different, thus giving different encryption values.

 
New Post
4/18/2007 2:01 PM
 

I have seen this happen if for some reason the InstallationDate node is not in the web.config and you get an app restart, which cause it to change your machine keys.

What happens is people will upgrade and move over their custom information to the new web.config, but miss the InstallationDate node (which is easy to do).

So long story short, check your machine key against a backup, and make sure the InstallationDate node is in your web.config.

 


DotNetNuke Modules from Snapsis.com
 
New Post
4/18/2007 4:16 PM
 

Oddly, this is a fresh install from the 4.5.1 Install package and the only change I made to the web.config file was the connection string.  I'm not really sure what happened except that I know that I did not make any (perhaps I should have) additional changes to the web.config file.

I was able to create a new user name and assign it superuser status using SQL.  If I were to copy the password and the password salt from the new user to the respective applicationIDs in the dbo.aspnet_Membership table, would that correct the password problem?

 
New Post
4/18/2007 5:47 PM
 

Yes, that would correct the problem for host, and since it is a fresh install I am assuming you do not have other users with passwords stored using different machine keys.


DotNetNuke Modules from Snapsis.com
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Unable to login (Not a skinning problem)Unable to login (Not a skinning problem)


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