May 21, 2013 at 12:48 pm
I'm not sure if this is the right place to post this one, but maybe someone can help.
I have a report that I built in Report Builder and it works perfect. I have uploaded it to the Report Server, but when I try to view it, I get an error with the query:
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset 'DataSet1'.
For more information about this error navigate to the report server on the local server machine, or enable remote errors
Here is the query that the report is running:
select
HourOfTheDay,
sum(case when TimeReceived between @startdate and @enddate then NumberOfOrdersInBatch else 0 end) as NumberOfOrders,
AVG(case when TimeReceived between @startdate and @enddate then TimeToProcess else 0 end) as AverageTime,
sum(case when TimeReceived between @startdate2 and @enddate2 then NumberOfOrdersInBatch else 0 end) as PrvWkNumberOfOrders,
AVG(case when TimeReceived between @startdate2 and @enddate2 then TimeToProcess else 0 end) as PrvWkAverageTime
from
info.batchstats with (nolock)
where
TimeReceived between @startdate and @enddate or
TimeReceived between @startdate2 and @enddate2
group by
HourOfTheDay
order by
houroftheday
Any help is appreciated.
May 21, 2013 at 1:53 pm
Does your Report Server have access to the database in the data connection of DataSet1?
--------
For SQL Tips, check out my blog: http://lantztechknowledge.blogspot.com/[/url]
You can also follow my twitter account to get daily updates: @BLantz2455
May 21, 2013 at 1:55 pm
Yes it does. It is using a shared data source that works with other reports. I have tried changing it, just to test, and it gives an error that the data source could not be reached. It seems to me like a problem with the query, but I can't figure out what that would be.
May 21, 2013 at 2:15 pm
Run a profiler trace against the target box and see what the query is sending down explicitly. It might be a simple difference in the dateformat defaults on the two boxes.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
May 22, 2013 at 3:33 pm
It is very easy enable report errors as well. Not sure if you have to start and stop the service, though.
http://msdn.microsoft.com/en-us/library/aa337165(v=sql.105).aspx
May 28, 2013 at 3:38 am
Personally, I like to write report SQL within a Stored Procedure, and just call the SP within the report.
This allows me to test that the correct data is being retrieved, independantly of the report. It also helps me realise that any problems with rendering that data are due to the report design. Both things tend to keep me on the right path when dealing with SSRS.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
May 29, 2013 at 7:27 am
Have you checked permissions on the table? I ran into this error yesterday and it was due to the fact that the SQL user we use to connect to the database for reports didn't have permissions to the view the new report was based on. Once I added the permissions, everything worked fine.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply