I have a site that has been up for a while on wh4l, today I've been getting alot of log messages for different module but basically the same type of error.  I noticed that the forum is starting to have these message actually on the page where other errors I'm only reading in the log.  I noticed this just today.  I will be upgrading this as it is 04.05.01.  What I am wondering is if it could be something with the host provider since this just started happening.  Here is the error log for one error that seems to be about file manager.  The container I'm using is the standard DNN Gray.  If anyone has an idea of what I've done or if it is just something might be going on with WH4L I'd sure apprieciate any help you might have.  Thanks, Janet

 04.05.01
PortalID: 0
PortalName: Savannah Estates Home Owners Association
UserID: 1
UserName: host
ActiveTabID: 19
ActiveTabName: File Manager
RawURL: /savannah-estates/Host/File Manager/tabid/19/ctl/Edit/mid/323/ftype/Module/rtab/18/portalid/0/Default.aspx
AbsoluteURL: /Savannah-Estates/Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; (R1 1.5); .NET CLR 1.1.4322; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 7cd11ad1-86cc-4895-b663-0a37603816b3
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.UI.Containers.ActionBase.set_PortalModule
StackTrace:
Message: System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.UI.Containers.ActionBase.set_PortalModule(PortalModuleBase Value) at DotNetNuke.UI.Skins.Skin.ProcessActionControls(PortalModuleBase objPortalModuleBase, Control objContainer) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings)
Source:
Server Name: DEDI514

This is interesting...  I was getting this error all day yesterday and it appeared to be caused by the login module (it was the only one not showing up).  I had planned to troubleshoot it last night, but I didn't get the chance.  However, I checked again this morning and everything is working again like nothing happened.

You should note that although I am using the same web host, I am running a slightly different configuration.  I have a single DNN instance upgraded to 4.05.03 since version 4 was released.  Also, this DNN instance is currently handling 3 different URL instances, each in a separate Application Pool (I requested it).

What I found particularly odd about this was that this problem was only experienced by one of my 3 portals, even though they are all running from the same instance.  Weird...  I hate problems like this that don't make sense.

Thanks, vitkoz!  That is a really good post and catch.  Which leads me to have narrowed down the other common denominator... 

I would imagine that Janettx would likely have the same condition in her portal.  The one portal where this happened had the login page specified in PortalSettings.  The other portals that did not experience this issue do not.