Cannot read the next data row for the data set
Hi, My report runs fine when Iview in VS, data shows fine when I run the query in the data window, but when I publish it to the server, I get the above error. I am running SQL server 2005 RTM and I have re-deployed the entire solution. Any ideas?
March 22nd, 2006 9:39am

Found the problem. This is a problem that is down to a bug in reporting services, and I sincerely hope that "they" fix it in the first sp! Occasionally, reporting services will change your parameter types to string. This is sooooo annoying, and normally fails when you view, but in this case, it took my parameters (date/time) that were already in the parameter boxes (I am altering an existing report) and ran the report happily. I just happened to see that there were no calendar boxes next to the parameters on my web server. ^%$"$%^&*&%$%^&(*&^%$ is all I can say - this has wasted 2 hours of my time. Please please Microsoft, fix this bug! A hot fix would be good.....beg beg
Free Windows Admin Tool Kit Click here and download it now
March 22nd, 2006 10:54am

Hi, Iexperienced similar problems with some of my RS reports and finda solution for my case I tried to explain the problem and solution at the article http://www.kodyaz.com/articles/article.aspx?articleid=53 For my situation, it seemed that the NULL values within aggregate functions were causing the problem. Actually although the sql code runs successsfully the warning message "Warning: Null value is eliminated by an aggregate or other SET operation." returned from the sql server was causing the Reporting Services to fire the below error: An error occured during report processing.Cannot read the next data row for the data set Dataset1.A sever error occured on the current command. The results, if any, should be discarded. A simple way to get rid of the problem is running the t-sql codes between "SET ANSI_WARNINGS OFF" and "SET ANSI_WARNINGS ON" commands. Eralper http://www.kodyaz.com
November 30th, 2006 7:18am

I had a similar problem. I also read the article at http://www.kodyaz.com/articles/article.aspx?articleid=53. I discovered that my problem was withstored procedures andaccount permissions. I had left GRANT statements in the stored procedures. When I ran the procs individually the I did not get an error. I also didnot get an error when I switched from design view to the preview view for the reports. When I ran the report from the report manger, I got the error. After I removed the GRANT statements from the procedures the report ran as expected. I now realize that while I was running the reports and procs from my development box , therewere running under my user account. That account had local machine admin and database admin rights. When I accessed the reports from report manager, the report were using the account that I had setup in the share data source. That account had limited permissions in the database. A permission error was occuring in the background, but it as not report that way in the report.
Free Windows Admin Tool Kit Click here and download it now
October 2nd, 2007 10:30am

What do you mean 'you left grant statements in the stored procedures' ?Scripting of permissions is an option in mgmt studioTools - Options - SQL Server Object ExplorerObject Scripting Options Script permissions TRUE/FALSE
August 8th, 2008 5:08am

I tried setting the warnings off but that didn't work for me. My report is fed by a stored procedure, I added the lines to manipulate ANSI_WARNINGS and the report still choked. I ran the proc again to see if it returned a warning and it did so setting the warning on and off and it didn't help. I fixed the condition in the proc that produced the warning and the report now runs every time. So it looks to me like you must have a stored procedure that runs clean or Reporting Services chokes.
Free Windows Admin Tool Kit Click here and download it now
August 18th, 2008 10:08am

I had the same issue and by changing the report execution property Report Execution Timeout Use default setting Do not timeout report executionfrom the Usedefault setting to the do not time outallowed the report to work
September 3rd, 2008 1:39pm

I had a the same problem with my report. I run it on Visual Studio 2005 with preview mode and it runs succesfully, but when I deploy it to the server it gives me the error "Cannot read the next data row for the data set xxx". I looked into my sql code and noticed that I tried to drop some temporary tables within the code. I removed those lines. And I put set ansi_warnings off at the very beginning. Finally I built and deployed the code, and it worked. I was really happy
Free Windows Admin Tool Kit Click here and download it now
September 5th, 2008 5:51am

Hi; I received a similar error in one of my SQL server reporting services reports. I found that connection to a specific table in the database was not possible. After re-indexing the table, the problem was solved. To re-index a table you can use this code: dbcc dbreindex (TableName)
July 5th, 2009 4:03pm

I had the same issue and by changing the report execution property Report Execution Timeout Use default setting Do not timeout report execution from the Usedefault setting to the do not time outallowed the report to work This fix worked for me as well running ssrs 2000 version. I also tried the 'isnulls' suggestion, but had no luck...thanks for posting guys...this was a huge help and a great discussion...!
Free Windows Admin Tool Kit Click here and download it now
July 18th, 2009 10:31am

I had the same issue. Worked fine on my pc in Dev mode but not on the server. I changed the proc for the report to SET NOCOUNT ON at the beginning and that fixed it. When this is off, it may send 2 recordsets to SSRS which it cannot handle.
November 12th, 2009 2:02am

Hi; I received a similar error in one of my SQL server reporting services reports. I found that connection to a specific table in the database was not possible. After re-indexing the table, the problem was solved. To re-index a table you can use this code: dbcc dbreindex (TableName) My Stored Proc was using a lookup table, which we had just truncated and repopulated and the dataset went from a few hundred records to only six...and then we started seeing this error on the deployed report (but not in BIDS). Re-indexing the table fixed the error. Thanks to Mehmet for posting that fix. Richard
Free Windows Admin Tool Kit Click here and download it now
March 24th, 2010 2:41pm

Changing the rreport execution property worked for me. Thanks, Uncle-Bob.
June 21st, 2010 4:15pm

Hi, I experienced the same problem and I fixed it by changing parameters back to Data/Time from Text (string) data type. I hope this bug wont be in SSRS 2008 R2.. Thanks
Free Windows Admin Tool Kit Click here and download it now
August 31st, 2010 5:34am

I tried all suggestions, the only one that worked was changing the parameter back to datetime from text. Thanks jirkaj
April 5th, 2011 1:17pm

I'm having the same issue but a little different. I'm not getting the error but other people are. Any suggestions?
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2011 12:07pm

I was able to correct this error by removing the maxRequestLength="20000" in the the 'web.config' : ...\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportManager\web.config You may be able to increase the value to resolve also.
March 3rd, 2012 5:43pm

After changes I have to reboot the server or not?
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2012 4:14am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics