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 ...After Upgrade to 4.6 - Account Login Module failsAfter Upgrade to 4.6 - Account Login Module fails
Previous
 
Next
New Post
10/17/2007 3:31 AM
 

Hi

Yesterday we've updated a DNN Site to DotNetNuke 4.6.0. The Installation Assistent didn't report any Errors or Warnings.

After the Update, the Login Module didn't load anymore. After clicking "Login" I got an Exception "Object reference not set to an instance of an object."

I checked the EventLog in the Database and noted that this was caused in the Method "DotNetNuke.Services.Authentication.AuthenticationConfigBase.get_AuthenticationModuleID". I found some Posts in the DNN Forum of some People who got the same Problem but have no solution yet.

Cause:

Missing/wrong Records some of this DB Tables related to the Table ModuleDefinitions:

  1. ModuleDefinitions (FriendlyName = Authentication)
  2. Modules
  3. ModuleControls
  4. DesktopModules
  5. TabModules

 

I compared these Tables with those of the Database shipped with DNN 4.6.0 and adapted/added some Records.

Maybe someone would Research that more exactly and write a SQL Script which fixes this Issue.

Regards,
Beni

 

Related Posts:

 
New Post
10/25/2007 1:24 PM
 
Hey Beni, I had the same issue after upgrading from 4.5.5 to 4.6.2. After digging into the code, I found that I did not have a module for ModuleDefID = 91. I installed a clean version of DNN 4.6.2 to a new database and found the record I was missing. I ran this SQL statement which fixed my login woes: INSERT INTO Modules (ModuleDefID, ModuleTitle, AllTabs, IsDeleted, InheritViewPermissions, Header, Footer, StartDate, EndDate, PortalID) VALUES (91, 'Windows Authentication', 0, 0, 1, NULL, NULL, NULL, NULL, 0) Good luck to you. Mike
 
New Post
10/25/2007 3:45 PM
 

Michael Martin wrote
Hey Beni, I had the same issue after upgrading from 4.5.5 to 4.6.2. After digging into the code, I found that I did not have a module for ModuleDefID = 91. I installed a clean version of DNN 4.6.2 to a new database and found the record I was missing. I ran this SQL statement which fixed my login woes: INSERT INTO Modules (ModuleDefID, ModuleTitle, AllTabs, IsDeleted, InheritViewPermissions, Header, Footer, StartDate, EndDate, PortalID) VALUES (91, 'Windows Authentication', 0, 0, 1, NULL, NULL, NULL, NULL, 0) Good luck to you. Mike

 

Please excuse my ignorance, but I just installed DNN for the first time today and also ran into the issue of not being able to login after making some edits to one of the sections on my default page.  Where/when would I run your SQL statement to try and correct this problem?

Thanks.

 
New Post
10/30/2007 5:02 PM
 

You would run the sql statement on your DotNetNuke database using a tool like Query Analyzer.  Before doing this, you probably want to query the database to see if you already have this module defined.  You can use this statement to only insert the record in question if it does not already exist:

IF NOT EXISTS (SELECT * FROM Modules WHERE ModuleDefID = 91) INSERT INTO Modules (ModuleDefID, ModuleTitle, AllTabs, IsDeleted, InheritViewPermissions, Header, Footer, StartDate, EndDate, PortalID) VALUES (91, 'Windows Authentication', 0, 0, 1, NULL, NULL, NULL, NULL, 0)

If you already have this record in your Modules table, you have some other issue.  Many times, people will set their portal's login page to be the home page.  If there is no account login module on the home page, you are out of luck because you are directing people to a page without a login module.  If you think that's the case, search around these forums.  There are MANY solutions to this issue.  I hope that helps.

 
New Post
10/30/2007 9:41 PM
 

I have just spent 3 days dealing with this issue myself.  However, I wasn't installing the newer versions of dnn 4.x.  I'm currently on dnn 3.x and when I updated my IIS server to 2.0 (so I could accomodate some newer modules I wanted to install - like the new forum module) I found I was unable to login.  However, it seemed only to happen with IE.  Attempting to log in with another browser (Firefox) was successful.  Changing the IIS server back seemed to help the IE issue.

Maybe my experience can shed some light on the newer installs, or not.

Cheers,

 

Lisa

 

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...After Upgrade to 4.6 - Account Login Module failsAfter Upgrade to 4.6 - Account Login Module fails


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