Re: ThreadAbortException on AR Report with large amounts of data.
ActiveReports for .NET 2.0 Support
ThreadAbortException on AR Report with large amounts of data.
01-28-2010, 2:36 PM
This happens with large amounts of data - but works fine with smaller amounts of data.
This report has one main report withg 2 subreports. One subreport is for the details and the other is for the high level summary section.
Using: ActiveReports3 5.3.1436.2
When I am in the debugger, or run this locally from my PC, the report completes as expected. However when ran from the Report Server this error occurs.
This particular report is written to the local drive on the report server when it is generated. When there is an internal report error, an errorpage is generated in the catch() block and saved before the report exits.
ActiveReports3.dll ,252,Report failed to generate due to unknown error:
System.Threading.ThreadAbortException: Thread was being aborted.
at #mb.#vqb.#vEb()
at #mb.#vqb.#qEb(Page newPage, Single left, Single top, Single right, Single bottom, UInt32 flags, UInt32& status)
at DataDynamics.ActiveReports.Section.#yBb(ActiveReport3 parentReport, #tqb rData)
at #mb.#mqb.#NDb(Int32 pieceIndex)
at #mb.#mqb.#LDb()
at #mb.#vqb.#vEb()
at #mb.#vqb.#qEb(Page newPage, Single left, Single top, Single right, Single bottom, UInt32 flags, UInt32& status)
at DataDynamics.ActiveReports.ActiveReport3.#4yb()
at DataDynamics.ActiveReports.ActiveReport3.Run(Boolean syncDocument)
at rptStatement.ReportServer.RunReport()
Thanks
Re: ThreadAbortException on AR Report with large amounts of data.
01-29-2010, 8:25 AM
Hello,
Could you please share the code with us where the exception is thrown. It would be helpful if you share the .cs or .vb report's code file with us as well.
Regards,
Aashish
Re: ThreadAbortException on AR Report with large amounts of data.
01-29-2010, 2:36 PM
I have found the problem.
Because of the large size of data being
returned, the report was loosing its connection with the database - thus the ThreadAbortedException.
After tuning the stored procedure - all is working as expected.
Thank you for your reply.