May 9, 2011 at 2:21 pm
Hello:
Last week, SQL Reporting Services 2008 (32-bit) reports were working just fine on client machines. End users could go to the URL (i.e. the Report Manager), click on a report, enter parameters, and run reports.
Now, the only successful way to run these reports from that URL is to run them directly from the server.
Again, these reports were working last week. I have no clue what changed between then and now.
Anyway, below is the error that end users get when they try to run any of the reports.
I did not have to configure any firewall or port settings. I don't know if a firewall or port issue is causing this. But....
And, what's strange is that the end users on these Windows 7 machines can pull up the Report Manager URL just fine. They just can't render reports like they used to.
Like I said, this does work on the server.
Any ideas?
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset ‘DocDate’
For more information about this error navigate to the local report server on the local machine, or enable remote errors.
John
May 9, 2011 at 5:06 pm
Here's the solution.
After looking at the log, it was discovered that the end user did not have db_datareader rights to the database. This was necessary since the reports required access to custom views that the report data was based on.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply