Ssrs Cannot Read the Next Data Row for the Dataset Dataset1. (Rserrorreadingnextdatarow)

Hi,

I've created a report that works perfectly in Visual Studio when I preview information technology, but in one case deployed I get the error: -

An fault has occurred during report processing. (rsProcessingAborted) Cannot read the next information row for the dataset Claims. (rsErrorReadingNextDataRow)

Having checked my dataset Claims, I noticed this contained a cavalcade Claim_Date that although containing a appointment (UK format east.g. 31/x/16) information technology was actually set to Varchar. I am guessing this may exist my effect?

I tried to apply convert on the column in question, simply when running the study I got the same error. Has anyone had a like effect and how do I get around this?

From some reading, I may need to cast to datetime, simply not entirely certain where to commencement with that 1.

Any advice appreciated.

Thanks

Glenn

---

If y'all created a "New" shared data source you lot also need to deploy it with the written report

10 Replies

Brand Representative for Microsoft

Information technology's not a data type issue. It's an issue with getting the information from the information set up. Are you calling a stored procedure or executing advertisement hoc SQL?

Make sure there isn't a argument existence called that doesn't render a data ready like a grant statement or DDL statement (most probable to happen if calling a stored process).

How-do-you-do Robert,

Many thanks for the response. It'southward adequately elementary SQL that I'thousand executing. I wasn't even sure what GRANT or DDL statements were until about five minutes ago simply no, nothing within my SQL that should be causing an issue.

It'south definitely that dataset though as I created a dummy written report pulling in just that dataset, and deployed it. Same issue.

Also, is at that place a reason why this wouldnt crusade any issues during Previewing / Testing, but not work one time deployed?

Thanks

Glenn

Make Representative for Microsoft

The mistake can also be caused by losing the connection to the SQL Server during data return.

Are you able to open the study in study builder and meet a completed data fix there?

I have never written reports in Visual Studio, so I don't know what the differences there could be.

Once the written report is deployed make certain you are pointing to the correct data source and have the correct credentials. Select written report "Cheque Marking" Drop down carte du jour and select Manage .......data source.

If you lot created a "New" shared data source you also need to deploy it with the report

Thanks for the suggestion, Octavio. I've checked this and all seems consistent with other reports. Additionally, the other reports using the same information source and credentials seem to be fine. For some reason it's this written report that is causing me issues!

exclude the claim date on your report and from the underlying query and deploy it ...See if it gives you the error.

Removing and redeploying the shared datasource was the answer. Thanks And so Much! Saved me a late nighttime going around in circles!

Thanks Octavio and thanks to others who contributed...

Your Welcome, Glad I could help.

Glenn Worth

This topic has been locked by an administrator and is no longer open up for commenting.

To continue this discussion, please ask a new question.

brownyouris1946.blogspot.com

Source: https://community.spiceworks.com/topic/1899941-converting-varchar-to-datetime

Share this post