Cannot read the next data row for the dataset DataSet1. (rsErrorReadingNextDataRow) - sql

I am working in Microsoft Visual Studio to create my RDL's. I have a sub report which refuses to run when we put it up on SSRS. This report runs fine inside of Visual studio in preview mode even when pointed at a copy of the prod database (still takes 30 min to run but it completes). The report only returns 1 row with counts of a large amount of data for a summary.
The full error text is:
An error has occurred during report processing. (rsProcessingAborted)
o Cannot read the next data row for the dataset DataSet1. (rsErrorReadingNextDataRow)
A severe error occurred on the current command. The results, if any, should be discarded. Operation cancelled by user.
This report used to work but the query was not correctly pulling the information. I had to change the query and expand what it was pulling from the database. Is there any way this could be caused by not enough memory being given to SSRS? We are using SSRS 2008 r2.

Turns out my problem was solved by putting in the recommended indexes provided by SQL Query Analyzer. After the indexes were created the query ran in ~4 min no problems.

Related

OLE DB or ODBC error. The current operation was cancelled because another operation in the transaction failed

OLE DB or ODBC error.
An error occurred while processing table 'Query 1'.
The current operation was cancelled because another operation in the transaction failed.
Out of line object 'DataSourceView', referring to ID(s) 'Temp_DSV', has been specified but has not been used.
I got the above error when i ran a query in Power Pivot for excel. Can somebody tell me , what might be the reason?
i got this message error too in mylast 7 days.
My solution is running first in example select top 10 * in sql server management studio, then go to excel, running query in power pivot again.
I dont know why this is solve, but it save me, in many times.
Maybe your query exceeds the memory limitations of 32bit Excel. Try to limit your query with a WHERE clause.
Also see this related question:
How to debug OLE DB or ODBC error (import data from MySql to Excel)

SSRS Parameter issue (SQL Server 2008 R2)

Having an issue where I have created a report with a shared data source and several shared data sets. The report has 2 parameters one dependent on the other. This was working fine until just recently. Now any report I create with a parameter does not work. I've tried creating a simple empty report that has an embedded DataSet:
SELECT ClientId, Name From Client
Then have the parameter use this query to populate available values (Value = ClientId and Label = Name).
When I preview in BIDS (VS-2008) it works just fine.
When I deploy and run the report I get the following error:
An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError)
Arithmetic overflow error converting expression to data type int. The statement has been terminated.
There are no expressions and I've deleted all old datasets that used to have an expression. Seems like SSRS has something cached though I have deleted Internet Cache and deleted the datasets from SSRS and went into the DB and deleted everything I could. Anyone else out there experience this issue?
Thanks

Crystal Report Duplicating in details?

so I have a template in Crystal reports using vb.net, I changed my data source location and that source still contains the needed tables for my report, the problem is this... My original template displays the exact report but when I changed its data source it duplicates the data in the details section(e.g I made a query that will show 1 item only,but instead I get 4).
Here is a screenshot of my problem:
(original at http://tinypic.com/r/5by6ih/5)
I want to alter the template rather than to make another one
This is normally down to an issue with the underlying SQL query. If you open the the report in Crystal (or visual studio) you should be able to "Show SQL Query". Run the query in Query Analyser or SQL Server Management Studio and look at the result.
If the underlying reason isn't then immediately apparent please paste the resulting output.

SQL Server 2005 Report Builder 2.0 - TFS Reporting : DATEDIFF between Start and Finish dates of a workitem

First of all thank you on advance for taking the time to access my question here.
I'm using Report Builder 2.0 for TFS Reporting with the TFS OLAP Cube as the main datasource.
I need to calculate the time taken between the start and end (completion) of a workitem as filled in in the appopriate TFS form.
When I use the following formula:
DATEDIFF(DAY; Microsoft_VSTS_Scheduling_StartDate_Date_(Date); Microsoft_VSTS_Scheduling_EndDate_Date_(Date))
I get the following error when running the report in the browser:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for data set 'dataSet'. (rsErrorExecutingCommand)
Semantic query execution failed. (rsSemanticQueryEngineError)
A grouping expression must be either a scalar field or an entity.
I have been around this for days and haven't found an answer anywhere.
Any ideas?
Thanks in advance!

SSRS - Severe error message when running stored procedure

I have a report that runs a stored procedure that takes about an hour to run.
After about 30 minutes I get this error message on the report body:
An error has occurred during report processing.
Query execution failed for data set 'DEV'.
A severe error occurred on the current command. The results, if any, should be discarded. Operation cancelled by user.
The same stored procedure runs fine when I run it from SQL Server management studio (with the same login credentials the report runs under).
Any ideas what could be causing this? I tried increasing the timeout value on the report but that didn't help.
This just sounds like a timeout. May I suggest you don't base a SSRS report on a stored proc that takes so long to run. You could schedule a daily job to populate a table (or tables) containing this report data and point the report at this table. That way it doesn't have to recalculate the data every time.
You can find the logs in your SQL Server installation directory. example: C:\Program Files\Microsoft SQL Server\MSRS10.REPORTING\Reporting Services\LogFiles
This might help.
http://blogs.msdn.com/b/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx
Check your connection string for the report. I got this error when I had used a malformed connection string. i.e. I had "Server=" when I should have had "Data Source=".