The error message returned when the mscrm 3.0 Reporting Services error processing report is canceled by the user.

Today, I encountered difficulties in developing a SQL Server reporing services 3.0-based report on the mscrm 2000 platform. After multiple parties ruled out the collapse, I finally got it done.

This is the case. First, the report code is very long and the business logic is relatively complicated. Therefore, the running time is relatively long. However, the following message is displayed:

 

Reporting Services error

• An error occurred while processing the report. (Rsprocessingaborted) Get online help
  • Failed to query the dataset "v_sale. (Rserrorexecutingcommand) Get online help
    • The operation has been canceled by the user.

Microsoft Reporting Services

I have not found any clues through the windows event viewer. To eliminate the problem. Therefore, the author has done the following:

First, the author runs the SQL code involved in the report in the SQL query analyzer. It takes about 30 minutes to 40 minutes to run the record set normally. Therefore, the SQL code is excluded.

Second, I doubt why the SQL query analyzer can be executed normally and an error is reported when it runs in mscrm 3.0. Then suddenly, mscrm 3.0 runs reports through the reporting services service components, and my reports run for a long time. Will the reporting services service time out. Therefore, I went to the Internet to check the relevant information:

 

Systemreporttimeout

Default Report Processing timeout value (in seconds) for all reports hosted in the Report Server namespace ). This value can be overwritten at the report level. If this attribute is set, the Report Server stops processing reports after the specified time. Valid value:-1To2,147,483,647. If the value is-1, The report in the namespace does not time out during processing. The default value is1800.

 

Finally, in order to check the problem, I immediately open the SQL Server Enterprise Manager, expand the reportserver database, open the configurationinfo table, and findSystemreporttimeoutThe column value is 1800. 1800 is 30 minutes, and it takes at least 30 minutes for the author to run the SQL query analyzer. I suspect the problem is caused. Then I immediately changed the value to-1. Save and close the table. After restarting the server, run the report again, and the report appears as expected.

Pai_^