Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dexter.knudson
Constraint Violating Yak Guru
260 Posts |
 Posted - 2008-09-03 : 22:03:01
|
| We have a .Net app that calls RS via a ReportViewer. Reports seem to generally be working fine [apart from the need to delete deployed reports & re-deploy (not just re-deploy) when param details are changed] but I have 2 reports generating an error:"Cannot read the next data row for the data set". From what I have seen on forums a range of issues can cause this from timeout to data type bugs in RS. Does anyone have experience with this? |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-09-04 : 03:01:59
|
| i've had a problem like this one. in the end, the problem was with back end query. it was breaking after a certain number of records where returned which caused this error. |
 |
|
|
dexter.knudson
Constraint Violating Yak Guru
260 Posts |
Posted - 2008-09-04 : 17:10:06
|
| Thanks Visakh. There were 3 reports with the same back-end query. 1 worked & 2 didn't. I ended up coping the one that did & pasting the RS tables from the others into it. In the profiler, something interesting I noticed in the ones that didn't work was that there was a line break in the path/name of the report which was used in the ReportServer commands like "exec ObjectExists", whereas the report that worked did not have this. I don't know whether this was significant or not, but it's the only difference I found. All 3 reports worked fine in the VS & on the report server & there was nothing in the log. It was just in ReportViewer where the problem was. |
|
|
|
|
|
|
ReportViewer: "Cannot read the next data row.."