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 ...Module Load WarningModule Load Warning
Previous
 
Next
New Post
10/24/2007 8:36 PM
 

Mark Tutt wrote

Figured the first two out.  As I said before, now the login module won't load, but nothing is logged as an error

BTW, you can't get to event viewer if you can't log in so you have to look at the DB. 

The login control simply won't load now, looking at the code I've added try/catches around the page_init and page_load, and that hasn't caught anything yet.  I'm guessing the exception is happening further up the chain.

The part that sucks is that I did pull everything back and test the upgrade locally first, and that worked fine.  Since I can't reproduce it locally, I can't debug it.  I've been scratching my head for about 14 hours now, and I think it's time to sleep on it.

I did upload the folders from the full install after I couldn't get the upgrade working, so that's not applicable to me.  I've scripted the stored procedures, functions and views from a working DB and updated the site DB with those on another suggestion, and that didn't get me anywhere.  I'm thinking there is something seriously hosed in the production DB after the first failed upgrade, but reviewing all of the obvious tables hasn't led me to what it is... 

Hi,

Any solution found for this?  I get the Module Load Warning after the upgrade of 4.6.2 and now even after reverting it back to 4.5.5 version I get the same error.  When I point the DB connection to my old database (2 months back db) it works fine and it fails only in the current database.  As I dont have the latest backup of the current database I'm forced to rectify the problem in the current database.  Anyone knows what is written into the db and in which table when it failed for the first time.  This is an urgent issue.  I hope someone shed light on this problem.  Thanks.

 
New Post
10/24/2007 11:05 PM
 

Hi,

I finally managed to spot out the problem.

  • In the new upgrade 4.6.2 Admin folder has additional sub folders.  They are <root>/Admin/Authentication and <root>/Admin/Packages
  • During the upgrade these new subfolder files path information is written in to the db into the table ModuleControls in the column ControlSrc for the keys like LOGIN,Logoff,Signin etc
  • when doing a downgrade, the admin folder is from the 4.5.5 version and the additional subfolders Authentication and packages are not available
  • during the downgrade the DB is not updated with the module path information and that causes the problem.  The login module could not find the path mentioned, so results in the error.

Solution:

In the ControlSrc I tried to look for %Authentication% and updated those values with the old values.  They were pointed to the security folder files in the 4.5.5 version. When the paths were pointed to the correct files, it started to work normally.  Now no more dreadful 'Module Load Warning' error.  Hurray!!!

 

I will try with the fresh upgrade of 4.6.2 in a few weeks time.

 
New Post
6/18/2008 1:27 PM
 

I experienced the same thing to my localhost DNN without any reason. It displayed that error and I could not login. I solve it by doing the followings. See it would help someone.

1) Make a copy of my whole DNN folder.

2) Unzip the original DNN installation ZIP to that DNN folder which has the problem . Let the original installation files overwirte any exisiting file.

3) Copy the web.config file from the very-first duplicated DNN folder back to this problem DNN folder in order to overwite the just re-installed web.config.

4) Browse my localhost DNN portal in web browser, DNN will install/update again.

5) At this point my login is back without any error message. BUT the style css and skins and containers were gone. Don't worry! Copy those stuffs from the very-first duplicated DNN folder back to this freshly re-installed DNN folder accordingly.

6) OK now the looks and feels are back.

7) Another BIG unknown problem!!! I login as host (the most powerful host!) but the DNN didn't allow me to use Edit mode. That meaned I cannot see the module settings and page settings.

8) Then I logout , then login as portal admin (the second-most powerful user!), luckily the I can use those settings with this portal admin.

9) To save my host login to be able to use those settings and edit mode, login as port admin, go to [Role Security], add HOST to the administrator group.

10) To test the HOST account, logout your portal admin and then login your HOST account. Bravo! It works.

11) Now logout your HOST and login as portal admin again. Go to the [Role Security] page, delete HOST from the Administrator group. This will not take away the HOST's greatest authority. It's admin authority will stay even it's removed from the Administartor group in the [Role Security] page. To test it, login as HOST and the eidt mode and all settings options are there. I don't know why but somehow it refresh/fool the DNN database.

Good luck.

 
New Post
12/7/2009 9:32 AM
 

that didn't work, neither looking at the eventlogs in the database, because it's empty.

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Module Load WarningModule Load Warning


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