My first report works fine. Every thing is same second report gets this error. An error has occurred during report processing.Query execution failed for data set 'DataSet1'.For more information about this error navigate to the report server on the local server machine, or enable remote errors SSRS 2005,DataSource is cube same security info,small aspx apps which has report viewer. based on report selection url changes to different report. a) "For more information about this error navigate to the report server on the local server machine" - don't what this meansb) "enable remote errors" - where do you enable remote errors? I know this is one of those error messages of reporting services - when error is on Left it will let you go Right. Thanks - Ashok

Do One thing if you are using stored Procedure , try to run it in SSRS before you Upload the report to the main server. And Dont forgot to click the refresh Button and then save.Check that in datset properties the parameters are there of what you require

My datasource is cube. My RS and IIS both are in same server. My aspx apps has few lines of code like this Report1 and Report2 both uses same cube (olap) database. when I run my apps in server both reports runs fine. When I run apps from out side Report1 is fine but Repor2 gives this error. Now first thing comes in mind is that Report2 may not have same permissions, which I compared with Repor1 10 times it's same. Inboth reports database connection info are same. so again both reports runs fine in server but out side I get error in report2. don't know what else I can look....... ReportViewer1.ProcessingMode = Microsoft.Reporting.WebForms.ProcessingMode.Remote; Uri u = new Uri("http://servername/ReportServer"); ReportViewer1.ServerReport.ReportServerUrl = u; if (Menu1.SelectedValue == "Report1") ReportViewer1.ServerReport.ReportPath = "/Report1"; if (Menu1.SelectedValue == "Report2") ReportViewer1.ServerReport.ReportPath = "/Report2"; ReportViewer1.ServerReport.Refresh();

Does both the reports resides on same folder level?

yes. still not able to fix the issue. I am sure it's able to access the report but not able to get data if I rename dataset name in report I see new name coming in error message as " Query execution failed for data set 'dataset name' "

Yes thats the reason. The dataset name should be changed everywhere in the report layout, not only in the data tab. All the controls in the report will be pointing to the old dataset name, change these.

You are right but then how I am able to run same report fine when I open report in the report server using same url? so if I open IE in report server and use http://reportserver/apps/default.aspx reports runs fine. same request I make from my machine report fails. -Ashok

Can you quickly check whether its authentication problem? if shared datasource is not used for Report 2 then go to Datasource properties of the report and check the credentials stored securely option is checked and you are passing a valid user account that has access to datasource. If this is the case the report still runs from URL but wont if proper user credentials are not passed from CLient app.

Guys, I experienced the same issue, and discovered that it was a simple matter of a stored procedure not having the appropriate permissions. To see if the same condition applies to you, check to see whether the dataset in question is being generated by a stored procedure. (If you have the .rdl file open in visual studio, look at whether it is being generated by a stored procedure - in the data tab, click on the dataset, and look to its right, to discover the name of the stored procedure) If the dataset is associated with a stored procedure, correct the permissions in your stored procedures as follows 1) Within SQL Server Management Studio, right click on the stored procedure 2) Right Click "Properties" 3) Hit "Permissions" 4) Look at users roles. If the user is not included, add them (you will need to know their object name) 5) After adding them (if necessary) Grant them & permission to execute 6) Hit Ok

Guys, I experienced the same issue, and discovered that it was a simple matter of a stored procedure not having the appropriate permissions. To see if the same condition applies to you, check to see whether the dataset in question is being generated by a stored procedure. (If you have the .rdl file open in visual studio, look at whether it is being generated by a stored procedure - in the data tab, click on the dataset, and look to its right, to discover the name of the stored procedure) If the dataset is associated with a stored procedure, correct the permissions in your stored procedures as follows 1) Within SQL Server Management Studio, right click on the stored procedure 2) Right Click "Properties" 3) Hit "Permissions" 4) Look at users roles. If the user is not included, add them (you will need to know their object name) 5) After adding them (if necessary) Grant them & permission to execute 6) Hit Ok