Hi,

I have a development server running DNN 4.9.0 (Win2k3, SQL 2k5). It has run perfectly for the last 10 - 11 months. I use it to develop skins for clients and the installation has 8 parent portals running on it. Yesterday when trying to log into one of the portals (in fact any of the portals) I was presented with the message below and am unable to access the Login or Register forms.

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.

I trawled this forum and worked through many of the suggested fixes but nothing has been successful. I restored the file system from a backup but that too changed nothing. To my professional shame and annoyance I am unable to restore the database. However the fact the restoring the file system made no difference suggests that the problem lies with the database.

The last change made on the DNN install was to create a new parent portal. That was created successfully and I was able to login.

Has anybody had a similar problem and found a solution to this?

Thanks in advance

RENAME DNN.ASPX OR DOTNETNUKE.ASPX TO DNN.X or DNN.blah or whatever (Im sorry I do not have an instal to look at right now, that is why I am not sure if it is dnn.aspx or dotnetnuke.aspx - it is which ever one is there.

HIT THE SITE

CHANGE THE NAME BACK TO ORGINAL

HIT THE SITE

.... THIS USED TO FIX ALL SORTS OF STRANGE PROBLEMS LIKE THE ONE YOU DESCRIBE - NOT TOO SURE IF IT STILL WORKS. Sorry for the caps.

My site www.mardigrasunmasked.com was throwing the following error:

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.

I could not login to the portal and this error was being thrown on the login page a few other pages.

After some time consuming and frustrating troubleshooting, I found a very simple solution for my issue.   For some reason, some folder WRITE permissions  had been re-set to READ ONLY.  Setting the correct Read/Write permissions for the portal resolved this for me.

It was REAL aggravating that I went through so much trouble digging into this problem when the solution was so simple.  Ain't that always the way. ; )

Just a heads up for those folks who might have the same issue. 

Mark Sottek

www.MardiGrasUnmasked.com