I am testing an upgrade of my site from DNN 5.6.3 to 6.0.2 and I am getting the error below on one page. It looks like it is related to the Netism Satellite module. I have tried to contact Netism using Snowcovered support but no response yet. Was something changed in the way the GetHostSettings() is used in DNN 6? The funny thing is that I moved the only module that uses Netism Satellite to another page and I still get this error.

On the page it just says... A critical error has occurred. An unexpected error has occurred

But in the Event Log I see this.

DotNetNuke.Services.Exceptions.PageLoadException: Method not found:
'System.Collections.Hashtable
DotNetNuke.Entities.Host.HostSettings.GetHostSettings()'. --->
System.MissingMethodException: Method not found:
'System.Collections.Hashtable
DotNetNuke.Entities.Host.HostSettings.GetHostSettings()'.
at Netism.SatelliteExtreme.TemplateEngine.Render(String TemplatePath,
String TemplateName, PortalModuleBase module, Page page, String datasource,
String Query)
at Netism.SatelliteExtreme.Display.ExecuteText()
at Netism.SatelliteExtreme.Display.Page_Load(Object sender, EventArgs
e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object
o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object
sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
--- End of inner exception stack trace

---

Forerunner Communications, LLC
DotNetNuke Integration Specialists

I doubt this is much help, but in our case we fixed it by improving one of the lines in our Skin files. This is what works now.

<dnn:STYLES runat="server" ID="StylesIE7" Name="IE7Minus" StyleSheet="ie7.css" Condition="LT IE 8" UseSkinPath="true"/>

I apologize, but I do not have a copy of the wrong version that was throwing the error. We might have added the Name and/or the UseSkinPath attribute. Thanks - Jeremy
 
I would eventually like to know what actually caused the error. It might make identifying the problem and fixing it easier.

---

- Accuraty / Jeremy

I see that there is a patch on the support site. I looked at the code in the file. Is this something that can be added in to an operating site or does the codebase have to be updated and the site files recompiled? Is there anyone who has done this who can supply only the necessary files that I could drop into my site?

I really cannot wait for a month or so for DNN 6.1 so is there any work around for this? I can pay whomever to help me fix this. It shows that this was reported in the 6.0.1 release. So is there a reason why it wasn't targeted for 6.0.2 instead of waiting for 6.1? Will there be a 6.0.3 where it can be fixed?

---

Forerunner Communications, LLC
DotNetNuke Integration Specialists