We have an Intranet site with 1 portal (portal 0). Last weekend I upgraded it to DNN 5.3.1 (was at 4.9.5) and I also upgraded most of the modules. I am having trouble with the Reports module since then. When I am in the Setup screen and I click "test data source" the browser freezes (ie7) for about 15 seconds then I see the error box "stop running this script?" Whether I click yes or no, it remains stuck for about 10 seconds then releases. I also see this happen when I click to select an HTML template at the bottom. There are page exeptions in the event viewer. Does anyone know why this is happening?

- Windows Server 2003, Dotnet Framework 3.5 sp1

----Execption---
5/21/2010 10:35:31 AM  Page Load Exception  sk460admin    AssemblyVersion: 5.3.1; PortalID: 0; PortalName< ... 
AssemblyVersion: 5.3.1
PortalID: 0
PortalName: Connection
UserID: 242
UserName: sk460admin
ActiveTabID: 428
ActiveTabName: Report1
RawURL: /dotnet/Dept/Technology/Test/Report1/tabid/428/ctl/Module/ModuleId/1158/Default.aspx
AbsoluteURL: /DotNet/Default.aspx
AbsoluteURLReferrer: http://cornerstoneconnection/dotnet/D...
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 8a4be6e1-7c9f-4793-a71c-ff5b36d8e2af
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Modules.Reports.Settings.Page_Load
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.Modules.Reports.Settings.Page_Load(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.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 ---
Source:
Server Name: SK82-460AS002

Yes, I should have mentioned that I did upgrade the Reports module to version 5.1.0 (latest).
I have an almost duplicate test site on another server which is at DNN 5.02.03 with Reports 5.0.0 and it has no problems at all (it has most of the same modules, same skin, same setup). I have been looking at settings on both sites to find any glaring configuration differences, but I am coming up empty.

Now I wish I had only taken the production site to version 5.02.03. It's been a rough week!

FYI. I figured out the solution for us and posted it here: http://local.dotnetnuke.com/Community...

---

-something clever or funny.