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 ...Cannot authenticate after upgradeCannot authenticate after upgrade
Previous
 
Next
New Post
12/11/2006 10:50 AM
 
 

btw, this site really needs a "Fix It!" forum.  :(

I installed 4.3.5 a month or two ago.  This was my first DNN installation.  I've had some struggles, but all in all things were going OK.

I don't want to get too far behind the current version.  This is mainly because I don't want to have difficult upgrades.  Well, so much for that idea.  I just upgraded to 4.3.7.  Now, I can't authenticate.  More on that below.  Here's what I did:

  • I made a backup copy of my entire website folder.
  • Then I made a backup copy of my web.config file.
  • I unzipped the DotNetNume_4.3.7_Upgrade.zip file over my current website.
  • I copied release.config to web.config and adjusted the SQL connections strings in the new web.config.
  • Then I went to http://localhost/
  • Nothing seemed to happen in terms of the upgrade, I just got my regular home page.

So I tried to log in.  I have two accounts, one "normal" user and one "super user".  Neither would log in.  I tried the default host and admin accounts, and they would not log in either.

Out of desparation, I renamed the current website folder and the backup website folder, to get back to 4.3.5.  This time, when I went to http://localhost/, I got an upgrade page stating that the assemblies were 4.3.5 and the database was 4.3.7.  That was hopeful, so I switched the folders back around.  But I still can't log in.  Here's what I get from Event Viewer's Application log:

Event Type: Information
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1315
Date:  12/11/2006
Time:  9:23:37 AM
User:  N/A
Computer: SUPWEBSVR
Description:
Event code: 4006
Event message: Membership credential verification failed.
Event time: 12/11/2006 9:23:37 AM
Event time (UTC): 12/11/2006 3:23:37 PM
Event ID: 5f399ef58c584a088241f1e958515e89
Event sequence: 5
Event occurrence: 1
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/1/ROOT-1-128103241805036111
    Trust level: Full
    Application Virtual Path: /
    Application Path: D:\Inetpub\wwwroot\website\
    Machine name: SUPWEBSVR
 
Process information:
    Process ID: 1820
    Process name: aspnet_wp.exe
    Account name: SUPWEBSVR\ASPNET
 
Request information:
    Request URL: http://localhost/Default.aspx?TabId=36&ctl=Login
    Request path: /Default.aspx
    User host address: 127.0.0.1
    User: 
    Is authenticated: False
    Authentication Type: 
    Thread account name: SUPWEBSVR\ASPNET
 
Name to authenticate: JonRobertson

 
New Post
12/11/2006 11:01 AM
 
Looking at the aspnet_membership table, FailedPasswordAttemptCount and FailedPasswordAttemptWindowStart are updating as my logins fail.  For some reason, the passwords that I KNOW are valid aren't being authenticated against the membership table.
 
New Post
12/11/2006 11:08 AM
 
Ok, I fixed one of my personal accounts.  I created a new dummy account using the same password that my personal account used.  Then I copied the values of aspnet_membership.password and aspnet_membership.passwordsalt from the new dummy account to my personal account.  Afterwards, I was able to log into my personal account with the expected password.

So, what about all of my users?

What is going on here?
 
New Post
12/11/2006 11:08 AM
 
Check to make sure the MachineValidation and MachineEncryption keys are transferred over to your new web.config.

DotNetNuke Modules from Snapsis.com
 
New Post
12/11/2006 11:16 AM
 
John Mitchell wrote
Check to make sure the MachineValidation and MachineEncryption keys are transferred over to your new web.config.


THANK YOU   THANK YOU   THANK YOU.

Yes, that was the problem. 

Dang!  That was even in the Documentation\Readme.txt file!  My apologies for not being more diligent.  And thanks again!
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Cannot authenticate after upgradeCannot authenticate after upgrade


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