(originally reported by MatthewHill)
If I use a ReportViewer in a Repeater or DataList inside a UserControl with ToolkitScriptManager in MasterPage I get the following error:
Microsoft JScript runtime error: Sys.ArgumentNullException: Value cannot be null.
Parameter name: panelsCreated[2]
If I use the standard ScriptManager I don't get the error. If I use the ReportViewer control directly on a page I can use either script manager. I've had to create Multi-level masterpages to allow me to choose ScriptManager or ToolkitScriptManager where needed. I know I could put the required script manager on each page instead of the masterpage but it's really yucky programming repeating markup/code on each page.
Another error happens on pages where I use the same user control with other ajax components:
Microsoft JScript runtime error: AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced. If you are using an ASP.NET ScriptManager, switch to the AjaxScriptManager in System.Web.Ajax.dll, or use the ToolkitScriptManager in AjaxControlToolkit.dll.
The page uses the ScriptManager so the ReportViewer will work but the other Ajax components want Ajax 4.0 scripts.
I haven't tried the ReportViewer on its own in a UserControl to determine if the DataList or Repeater is contributing to the problem.
I'm using VisualStudio 2010 RC Ultimate with Nov 09 Ajax Library. ReportViewer v10.
===========================================
Comments most recent at top (show oldest at top)
MatthewHill wrote Mar 6 at 2:32 PM
I've found that if you set the property EnablePartialRendering="false" then the ReportViewer control continues to load. Unfortunately this is not a good solution as it interferes with other functionality.
MatthewHill wrote Mar 6 at 1:57 PM
I did a bit more checking and the error can be recreated by simply having the ToolkitScriptManager and a ReportViewer control pointing to a server report. If you point it to a local report there is no error. I think the javascript in the Server mode is not being handled correctly by ToolkitScriptManager. Attached is a very simple website that shows the error.
MatthewHill wrote Mar 4 at 5:08 PM
I've attached a sample website that works if the report is local. If the report is on a report server it fails.
assads wrote Mar 3 at 3:48 PM
Can you provide a minimal repro of the issue? That would help us narrow down to your issue.
Stephen_Walther wrote Feb 24 at 4:10 PM
We are investigating this issue.
Comments: Has anyone managed to work around this issue?
If I use a ReportViewer in a Repeater or DataList inside a UserControl with ToolkitScriptManager in MasterPage I get the following error:
Microsoft JScript runtime error: Sys.ArgumentNullException: Value cannot be null.
Parameter name: panelsCreated[2]
If I use the standard ScriptManager I don't get the error. If I use the ReportViewer control directly on a page I can use either script manager. I've had to create Multi-level masterpages to allow me to choose ScriptManager or ToolkitScriptManager where needed. I know I could put the required script manager on each page instead of the masterpage but it's really yucky programming repeating markup/code on each page.
Another error happens on pages where I use the same user control with other ajax components:
Microsoft JScript runtime error: AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced. If you are using an ASP.NET ScriptManager, switch to the AjaxScriptManager in System.Web.Ajax.dll, or use the ToolkitScriptManager in AjaxControlToolkit.dll.
The page uses the ScriptManager so the ReportViewer will work but the other Ajax components want Ajax 4.0 scripts.
I haven't tried the ReportViewer on its own in a UserControl to determine if the DataList or Repeater is contributing to the problem.
I'm using VisualStudio 2010 RC Ultimate with Nov 09 Ajax Library. ReportViewer v10.
===========================================
Comments most recent at top (show oldest at top)
MatthewHill wrote Mar 6 at 2:32 PM
I've found that if you set the property EnablePartialRendering="false" then the ReportViewer control continues to load. Unfortunately this is not a good solution as it interferes with other functionality.
MatthewHill wrote Mar 6 at 1:57 PM
I did a bit more checking and the error can be recreated by simply having the ToolkitScriptManager and a ReportViewer control pointing to a server report. If you point it to a local report there is no error. I think the javascript in the Server mode is not being handled correctly by ToolkitScriptManager. Attached is a very simple website that shows the error.
MatthewHill wrote Mar 4 at 5:08 PM
I've attached a sample website that works if the report is local. If the report is on a report server it fails.
assads wrote Mar 3 at 3:48 PM
Can you provide a minimal repro of the issue? That would help us narrow down to your issue.
Stephen_Walther wrote Feb 24 at 4:10 PM
We are investigating this issue.
Comments: Has anyone managed to work around this issue?