Hi,
The Telerik reporting designer keeps crashing when I made a change to a report and execute a preview action.
Also, when it doesn't crash it jumps back to the designer after it generated the report. I don't know why. Clicking the preview tab again then finally shows the report.
Regarding the crash I have the following information:
Exception: {"Cannot access a disposed object.\r\nObject name: 'AdornerWindowCtrl'."}
Stacktrace: at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at Telerik.Reporting.Design.Behavior.SelectionManager.Refresh()
at Telerik.Reporting.Design.GraphDesigner.OnProcessItemCompleted()
at Telerik.Reporting.Design.GraphDesigner.ProcessItem()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
What am I doing wrong?
The Telerik reporting designer keeps crashing when I made a change to a report and execute a preview action.
Also, when it doesn't crash it jumps back to the designer after it generated the report. I don't know why. Clicking the preview tab again then finally shows the report.
Regarding the crash I have the following information:
Exception: {"Cannot access a disposed object.\r\nObject name: 'AdornerWindowCtrl'."}
Stacktrace: at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at Telerik.Reporting.Design.Behavior.SelectionManager.Refresh()
at Telerik.Reporting.Design.GraphDesigner.OnProcessItemCompleted()
at Telerik.Reporting.Design.GraphDesigner.ProcessItem()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
What am I doing wrong?
4 Answers, 1 is accepted
0
Patrick
Top achievements
Rank 1
Rank 1
answered on 10 Jul 2013, 08:40 AM
Anyone?
The report uses an ObjectDataSource, contains a table and a pie graph.
The HTML preview works fine as in that is doesn't crash. But both previews jump back to the designer after the report project is build. Clicking the preview again makes it work. I'm using the Telerik Reporting 2013 Q2 with Visual Studio 2012.
The report uses an ObjectDataSource, contains a table and a pie graph.
The HTML preview works fine as in that is doesn't crash. But both previews jump back to the designer after the report project is build. Clicking the preview again makes it work. I'm using the Telerik Reporting 2013 Q2 with Visual Studio 2012.
0
Glen
Top achievements
Rank 1
Rank 1
answered on 10 Jul 2013, 07:17 PM
Yep, same here.
I build the solution, click on the Preview tab, "Generating Report" is displayed, then immediately kicks back to Designer Tab.
Works the second time you click Preview.
Using Telerik.Reporting version 7.0.13.220
I build the solution, click on the Preview tab, "Generating Report" is displayed, then immediately kicks back to Designer Tab.
Works the second time you click Preview.
Using Telerik.Reporting version 7.0.13.220
0
Hello Patrick,
Peter
Telerik
Getting back to the report designer surface after invoking the preview is a known behavior when previewing a modified report and having your data layer in the same project as the report definitions. This is caused by the required project rebuild and the initiated automatic VS designer reload. Generally our recommendation is to move your data access layers in a separate project.
About the error please try our suggestion and if you still experience the unexpected behavior we will appreciate if you send us a runnable sample that exhibits the error to debug on our end.
Peter
Telerik
Have you tried the new visualization options in Telerik Reporting Q2 2013? You can get them from your account.
0
Patrick
Top achievements
Rank 1
Rank 1
answered on 24 Jul 2013, 07:53 AM
I have to finish the project but when I have time I will look into this a bit more. However, I seperated the datasources into and reports into different projects now. That doesn't improve the situation.