RS errors and reports "Operation cancelled by user"

Question

RS errors and reports "Operation cancelled by user"

Cami Reily

SSC Veteran

Points: 226
More actions
June 2, 2005 at 4:27 pm

#110454

Attempting to generate a report using RS. It returns the following error:
"System.Data.SqlClient.SqlException: Operation cancelled by user."
...although the operation was not cancelled by a user. I have reviewed the logfiles and found:
"INFO: RunningJobContext.IsExpired; found expired request
ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'DataSet'.
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'DataSet'. ---> System.Data.SqlClient.SqlException: Operation cancelled by user.
ERROR: An exception has occurred in data source 'DataSet'.
Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'DataSet'. ---> System.Data.SqlClient.SqlException: Operation cancelled by user.
ERROR: An exception has occurred. Trying to abort processing.
Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'DataSet'. ---> System.Data.SqlClient.SqlException: Operation cancelled by user.
INFO: Merge abort handler called. Aborting data sources ...
INFO: Data source 'Production': Abort handler called. CanAbort = True.
INFO: Data set 'DataSet': Cancelling command.
WARN: CommandWrapper.Cancel not called, connection is not valid
INFO: Abort callback successful.
ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing.
Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'DataSet'. ---> System.Data.SqlClient.SqlException: Operation cancelled by user.
...That is the end of the inner exception stack trace. Can anyone shed light on the cause of this issue and possible resolutions?

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

david bartz Valued Member Points: 51 More actions · Answer 1

We ran into the exact same issue. Is your browser connectiing via a proxy server or going through a firewall? if so, check the timeout intervals on these and if your report in not generating in under the timeout of the proxy server / firewall, it's these that are closing your connection. You'll need to update the timeout on the offender accordingly.

An easy test is to run the report several times and time exacty how long it takes to fail. if the time is consistent, this will be a good indication that a network piece is timing you out.

shanker-439606 SSC Enthusiast Points: 155 More actions · Answer 2

hi im facing the same prob as above. and when my report run more than 45 minutes it shows Error as below:

An error has occurred during report processing. (rsProcessingAborted) Get Online Help

Query execution failed for data set 'dsDailyLeaveOt'. (rsErrorExecutingCommand) Get Online Help
- Operation cancelled by user.

when i check my reporting services logfile, i got some info as below.

aspnet_wp!runningjobs!43c!5/14/2007-10:31:39:: i INFO: RunningJobContext.IsExpired; found expired request

aspnet_wp!processing!be8!5/14/2007-10:31:39:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'dsDailyLeaveOt'., ;

Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'dsDailyLeaveOt'. ---> System.Data.SqlClient.SqlException: Operation cancelled by user.

anyone face this prob before and any solution how to overcome this prob?

Thank you

Regards

Shanker

philcart SSC-Forever Points: 47797 More actions · Answer 3

Firstly, I'd be asking what person in their right mind would have a report that takes 45 mins to run. That would indicate that there is probably too much going on in the report in the first place.

Now for SQL Reporting Services 2005 you can modify the config to increase the timeout,

http://msdn2.microsoft.com/en-us/library/ms157273.aspx,

DatabaseQueryTimeout
Specifies the number of seconds after which a connection to the report server database times out. This value is passed to the System.Data.SQLClient.SQLCommand.CommandTimeout property. Valid values range from 0 to maximum integer. The default is 120. Setting the value to 0 is not recommended; it specifies an unlimited wait time.

For the Report Manager you can add a httpRuntime element (http://msdn2.microsoft.com/en-us/library/e1f13641.aspx) to web.config file to increase the timeout

The execution timeout can also be modified via the Site Settings.

--------------------
Colt 45 - the original point and click interface

shanker-439606 SSC Enthusiast Points: 155 More actions · Answer 4

im not really sure but i think its because of all the funtions that been used by the previous programmers and the amount of data generated nearly millions of data. so any where to set timeout for the reporting services 2003 huh dude?

philcart SSC-Forever Points: 47797 More actions · Answer 5

I didn't know there was a Reporting Services 2003 In Reporting Services 2000, I think the config and Site Settings are pretty much the same.

If you're outputting millions of rows of data then maybe you should be using DTS instead of Reporting Services. While it can perform the task, Reporting Services is not a data extraction tool

--------------------
Colt 45 - the original point and click interface

shanker-439606 SSC Enthusiast Points: 155 More actions · Answer 6

iIts not just extract the data and put on screen. all the data in different different tables. i need to join them all, use few cursors and some functions and so on to fulfill the user requirement.

sorry i mean in 2000 reporting services. i had set the config as told but its still the same. i have set them to 0 but it still show the same error 'Operation cancelled by user. '

philcart SSC-Forever Points: 47797 More actions · Answer 7

Ok, how about processing the data and storing the results in a table that the report uses?

I've done this with a couple of reports where data had to come from 4-5 different sources. It was quicker to amalgamating the data in the database than bringing it together in the report.

This would remove the "live" data aspect, but if it takes 45 minutes to run, I'm betting this isn't a live report anyway.

--------------------
Colt 45 - the original point and click interface

jonathan.bloom Valued Member Points: 53 More actions · Answer 8

We received the following error in the log file:

ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset

Turns out the export format was Excel and the output row count exceed 65k rows. Converted to .csv or .pdf should fix the issue we had...

Jon Bloom

http://www.tampabaybi.com