After installing the module succesfully (DNN 4.5.x) I get the following error when I add the moduel to a page:

DotNetNuke.Services.Exceptions.ModuleLoadException: Unknown server tag 'asp:UpdatePanel'. ---> System.Web.HttpParseException: Unknown server tag 'asp:UpdatePanel'. ---> System.Exception: Unknown server tag 'asp:UpdatePanel'. ---> System.Web.HttpException: Unknown server tag 'asp:UpdatePanel'. at System.Web.UI.TagPrefixTagNameToTypeMapper.System.Web.UI.ITagNameToTypeMapper.GetControlType(String tagName, IDictionary attribs) at System.Web.UI.MainTagNameToTypeMapper.GetControlType(String tagName, IDictionary attribs, Boolean fAllowHtmlTags) at System.Web.UI.RootBuilder.GetChildControlType(String tagName, IDictionary attribs) at System.Web.UI.ControlBuilder.CreateChildBuilder(String filter, String tagName, IDictionary attribs, TemplateParser parser, ControlBuilder parentBuilder, String id, Int32 line, VirtualPath virtualPath, Type& c! hildType, Boolean defaultProperty) at System.Web.UI.TemplateParser.ProcessBeginTag(Match match, String inputText) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider b! uildProvider) at System.Web.Compilation.BuildProvidersCompiler.Process BuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

Any idea what may be the cause of this?

Marko Mazeland

We are using 04.05.05

We made one step ahead as it came out that Java is required to run the module. The required adaptation of the web.config was made by hand, shouldn't this be done by the installer?

Then we did run in the next error, a reference to /DesktopModules/AdverageousExplorer/AExpSettings.ascx where obviously a reference to something like AdverageousManager was expected.

mazeland wrote We are using 04.05.05 We made one step ahead as it came out that Java is required to run the module. The required adaptation of the web.config was made by hand, shouldn't this be done by the installer? Then we did run in the next error, a reference to /DesktopModules/AdverageousExplorer/AExpSettings.ascx where obviously a reference to something like AdverageousManager was expected.

The settings page is not currently active.  The only settings for the module for 1.0 are via "Manage Folders"

Java is not required, can you please tell me the web.config change you made?

I have only had a partner test this on 4.5.5, but have not done this myself.  I suspect, once again, new DNN version is causing issues.   I will confirm sometime today, and get you an update if needed.