I just upgraded to 4.7 from the last release, 4.6.2 or whatever it was. After the upgrade process (which I saw nothing of, no dialog boxes or anything), when loading the page, I get this:

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.

This is for the Login module. I use both the DNN Registration and Login, as well as the AD provider (Windows Login). I never have seen any new registrations even get put into Active Directory, but that is a new thread. I need to figure out why this Login Module is no longer functioning. Any supportive ideas? I have full access to everything, so if there is a tick in the database that will revert to using only the DNN Login Module, I am willing to give that a try to get a functioning portal. The address for viewing it yourself if you like is http://www.hayesportal.com.

If you receive an IIS Windows Login prompt, please hit cancel and retry the page; this is an entirely separate error that has persisted since 4.6.2. Thanks in advance for any help and I appreciate your patience through my longwinded nature.

Shannon Justice

A Google search on "Module Load Warning" includes numerous webpages that have returned this error message to the Google crawler. These webpages are from sites that appear to be production sites and include such sites as .gov's, user groups, etc. I suspect that as people return to work from the holidays, we're going to see many more posts regarding this issue. I too am getting this error and have been unsuccessful in resolving it from the forum posts and on my own. Any help on this is going to be appreciated by many people.

I may have misunderstood your previous comment about the AD provider. The way I understood it was that you were expecting new accounts to be created in your networks Active Directory which isn't the case. What the provider does is read the Active Directory and registers a new account in the DNN database automatically without the user having to enter any information.

As far as your error goes, if you aren't able to get logged in (which sounds like the case here) you may be able to find more detailed information by checking the log files. If you could get logged in it would be under Admin->EventViewer but not logged in it coudl be a couple of places that I can see. One is in your DNN directory under Portals/_default/Logs and the other is in the database under EventLog. In the database EventLog table the messages are stored in the LogProperties field and are very long. It would probably be easiest to copy the contents of that field to notepad. I think those are the two places the logs are normally written and with that information it'll be easier to sort out the problem.