Hello,
I have created a web application that is used for report processing. The way it works is as follows:
The user goes to a page, select the 5 reports they want to run (5 checkboxes) and specifies the cut off date. The reports are made in Crystal Reports RC 2 with ASP.NET using VB.NET 2.0. The page itself is Ajax enabled and shows a progress bar graphic upon click of the button.
I retrieve a dataset and bind it to the crystal report (aka the push method) and then export to PDF format. The dataset is recycled because I filter the report's dataset once per user (approx 15 users). This saves multiple calls to the database.
On my development machine, it works like a charm. BEAUTIFUL!!! On the server, I am getting the "Thread was aborted. Load repot failed." error message. It is being fired in the asyncPostBackError event. The error message is inconsistent as to timing. It occurs seemingly randomly.
I've confirmed that all assembiles, includes and reports are pointing to correct location.
anyone have this issue or know a workaround?
I have created a web application that is used for report processing. The way it works is as follows:
The user goes to a page, select the 5 reports they want to run (5 checkboxes) and specifies the cut off date. The reports are made in Crystal Reports RC 2 with ASP.NET using VB.NET 2.0. The page itself is Ajax enabled and shows a progress bar graphic upon click of the button.
I retrieve a dataset and bind it to the crystal report (aka the push method) and then export to PDF format. The dataset is recycled because I filter the report's dataset once per user (approx 15 users). This saves multiple calls to the database.
On my development machine, it works like a charm. BEAUTIFUL!!! On the server, I am getting the "Thread was aborted. Load repot failed." error message. It is being fired in the asyncPostBackError event. The error message is inconsistent as to timing. It occurs seemingly randomly.
I've confirmed that all assembiles, includes and reports are pointing to correct location.
anyone have this issue or know a workaround?