Member Avatar for kalit

Hi,

We upgraded from 4.6.2 to 4.9 recently. All is working well, it seems, except for the login / authentication module. When attempting to login, no username/password box appears and instead we are greeted with a module load warning:

Module Load Warning
One or more of the modules on this page did not load. This may be temporary. Please refresh the page (click F5 in most browsers). If the problem persists, please let the Site Administrator know.

Please suggest on this.

  • 3 Contributors
  • 2 Replies
  • 115 Views
  • 6 Hours Discussion Span
  • Latest Post Latest Post by prashantchalise

Dani AI

Generated

The upgrade path from DNN 4.6.2 -> 4.9 frequently leaves a visible symptom like the one describes: the login control is replaced by a generic "Module Load Warning" because the login control failed to instantiate. is right that vendor docs/support can help, and was on the right track about checking the real error — the useful next step is to surface that error and then follow a short triage checklist.

First, capture the exception. If a host/superuser session is available, open Host -> Event Viewer. If not, read the EventLog table directly from SQL (make a backup first):

-- SQL Server: show recent DNN error rows
SELECT TOP 50 *
FROM EventLog
ORDER BY LogCreateDate DESC;

Open the newest entry and inspect the text/stack trace there — it usually tells you whether the problem is a missing ASCX/file, an assembly version mismatch, a third‑party auth module throwing, or a permissions problem.

Common fixes tied to the error:

  • Missing control file: search the site for the login ASCX and restore the DesktopModules files from a clean 4.9 package.
    Get-ChildItem -Path 'C:\inetpub\wwwroot\yoursite' -Recurse -Filter '*Login*.ascx' | Select FullName
  • TypeLoad / MissingMethod exceptions: check for stray or old DLLs in /bin and replace with the 4.9 assemblies.
  • Third‑party auth modules: temporarily remove their folder(s) from DesktopModules and any DLLs they add to /bin; recycle the app pool and re-check EventLog.
  • Permissions: ensure the app‑pool identity has read access to site files and the /bin folder.

After any change, recycle the app pool (or touch web.config) and re-check the EventLog. Always back up DB/files before making DB edits or replacing DLLs. If the exception message is unclear, paste the exact stack trace into a staging install of 4.9 to reproduce; that makes it much easier to identify which file or assembly to restore or update.

Recommended Answers

All 2 Replies

Member Avatar for Lusiphur

Well... what I might suggest is that you ask the friendly folks at DotNetNuke since it is their application package and you've provided no code for anyone to work with in your post.

Generally speaking if you're having a problem with a pre-packaged software solution the best people to ask would be the people who pre-packaged it :)

Just my opinion though.

Member Avatar for prashantchalise

Many reasons can lead you to this condition such as module not found, Usercontrol not compatible or contains error etc. You need to login as super user and view the exact reason for this.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.