Hi Guys, 


I am new to DNN and have the following problem. I installed DNN with no problems and set up the site yet again with no problems. However I now get the following error on my site sporadically. I can see no reason for it. When the error happens I am unable open the site at all then roughly 40-60 minutes later it comes back up and works for another hour or so. I got the following from the logfile in admin but it does not mean anything to me can you please help?!

9/27/2011 1:34:05 PM Page Load Exception  PDC - Designs  AssemblyVersion 6.0.1 PortalID 0 PortalName PDC - Designs UserID -1 UserNa 
AssemblyVersion: 6.0.1
PortalID: 0
PortalName: PDC - Designs
UserID: -1
UserName:
ActiveTabID: 81
ActiveTabName: Pandas & People
RawURL: /Default.aspx?tabid=81&error=An%20unexpected%20error%20has%20occurred&content=0
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: d53e20eb-e248-4797-b883-98c691d48b59
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.UI.Skins.Skin.GetSkin
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.UI.Skins.Skin.GetSkin(PageBase page) at DotNetNuke.Framework.DefaultPage.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:
Server Name: WFWEB10B 

Hello, that's odd , i searched and can find a few references to this error from 2010 (about 5.2.x timeframe) but none recently. Could you install the symbol files from http://dotnetnuke.codeplex.com/releases/view/71896 -this should alter the stacktrace to show what the line number is and might help us track it down. As for the application pool starting up, thats strange but not unexpected, when an application pool is shutting down/being recycled a new one get's started whilst the old one finishes any queued requests - the question is why this error in particular is causing the app pool to rarely shut down.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US