I looked at the requirements for Reports and it stated a minimum of DNN 4.3.5.  We're running on DNN 4.6.2, so I assumed it would be fine to upgrade by reinstalling the module with version 5.  There were no report modules active.  When I added the reports module (after upgrade to 5.0) to a page, I got this error message stating that it actually requires DNN 4.7.0 or higher to work properly:

Error: Reports is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\beta\1532476c\9f4cd6ea\App_Web_viewreports.ascx.4c7e8800.strfukdg.0.vb(53): error BC32206: Indirect reference is being made to assembly DotNetNuke version 4.7.0.0, which contains 'DotNetNuke.Modules.Reports.ViewReports'. This Project references a prior version of DotNetNuke version 4.6.2.0. To use 'DotNetNuke.Modules.Reports.ViewReports', you must replace the reference to DotNetNuke with version 4.7.0.0 or higher. ---> System.Web.HttpCompileException: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\beta\1532476c\9f4cd6ea\App_Web_viewreports.ascx.4c7e8800.strfukdg.0.vb(53): error BC32206: Indirect reference is being made to assembly DotNetNuke version 4.7.0.0, which contains 'DotNetNuke.Modules.Reports.ViewReports'. This Project references a prior version of DotNetNuke version 4.6.2.0. To use 'DotNetNuke.Modules.Reports.ViewReports', you must replace the reference to DotNetNuke with version 4.7.0.0 or higher. at System.Web.Compilation.AssemblyBuilder.Compile() 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.Compilation.BuildManager.GetVPathBuildResultWithAssert(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 ---

Soooo, what is the minimum requirements for DNN version for installing the Reports module?  Should I uninstall Reports 5.0 and go back to Reports 4.5?  We can't upgrade, we are using Catalook which is DNN version specific for 4.6.2.

Confused,

Rick

JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

I experienced the same problem and I fixed it by moving my DNN to 4.8.0  ( from 4.6.2). Now it works except for the chart and report extensions which have been lost.

The download page appears to be in error. The module does require DotNetNuke 4.7 or higher in order to use the new Package Installer for installing Visualizers and Data Sources. I apologize for any issues those of you who upgraded have encountered and I'll make sure this gets fixed.

If you have specific reasons for staying on a pre-4.7 version of the core but really want to use the new version of the module, please let me know. I am prepared to release a version without the Package Installer features if there is enough demand. You can email me at: andrew DOT nurse AT dotnetnuke DOT com or just post in this thread.

Glad to hear the downgrade worked! Sorry about the inconvenience.

Andrew Nurse
DotNetNuke Core Team Member and Reports Module Project Lead
Microsoft Certified Professional Developer