An error has occurred during report processing. (rsProcessingAborted)Cannot read the next data row for the data set PerfAnalysis. (rsErrorReadingNextDataRow)Please Help!Thanks!

Sorry, you need to let us know some more information. Which version / build of Reporting Services are you using?Which data source are you using?If you right click on the error page and select View Source, you should be able to see the stack trace.

Thank you all the same.The problem is solved.It is data source.

Hello Brian, We are also facing the same problem. We are getting following two messages on the error page. We are using reporting services 2000. An error has occurred during report processing. (rsProcessingAborted) Get Online Help http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings.resources.Strings&EvtID=rsProcessingAborted&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=8.00 Cannot read the next data row for the data set DsCheck. (rsErrorReadingNextDataRow) Get Online Help http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings.resources.Strings&EvtID=rsErrorReadingNextDataRow&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=8.00 When we executed the stored procedure from the Query Analyzer we get the proper output without any error. There is no clue as to why next row is not getting read. Thanks for your help. Atul

Hi, I have the same problem now, what is the solution ? Regards. Mario

Did any one find the solution for this?. I have the same problem for one my report. other reports works fine. All uses the same datasource

Even i m facing same problem at client place. Did any one find the solution for this? I guess this error might be related one of the following two things 1 Connection. I am able to reproduce this error only when i disconnected the network during report generation. 2 Permission The stored procedure might not have sufficient permission. Perticularly when one of the dataset depending upon another dataset. For example when we use formula to hide columns in report based on value of another dataset.

Hi, I came across this problem when using reporting services where the report was using a stored procedure. I, as an administrator, was able to run the report without any errors. The users however, who had read permission on the database and execute on the stored procedure kept receiving the error. The problem ended up being caused by a DDL statement (grant execute) that was mistakingly created at the end of the stored procedure (forgot to put a go after the end so it created the grant execute with the stored proc). Once the ddl statement was removed the users who didn't have permission to execute DDL statements were able to run the report. Regards, Patrick Roberts

Patrick, Thank you! I have been chasing thissame bug for two miserable days. My problem was EXACTLY what you described - a grant statement inadvertently stuck on the bottom of the stored procedure because I forgot to put a GO in! Have a great day, Laura Killian Olympia, Washington, USA

hello everyone, Im getting the same message from sayhi1982, but the scenario of my reports is: I run the report on performancepoint in a sharepoint site. When I open de report from the server I created it, it runs fine but when I try to open the report from another computer with the same administrator credential the error appears. Can someone help me with this problem? Thanks Jose