May 30, 2006 at 1:54 am
I have been working on a report for a while now and just when I go to deploy it, the bloody thing stops working.
I have been testing it mainly under my account (Admin + Domain Admin) and peridocally under another admins account. I have also been testing it under a dummy normal account (domain user only) and up until now it has worked fine.
Originally it did not work although I found that if I Rebuilt & Redeployed the project to the server and then started Reporting services and selected the datasource1 and supplied my credentials and checked Use as Windows Credentials and also the Impersonate check, it all worked perfectly.
However now this does not appear to be the case
The exact error I get is
'An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DashboardSQL-2K5'. (rsErrorOpeningConnection)
For more information about this error navigate to the report server on the local server machine, or enable remote errors'
The connection string under the properties of datasource1 are
INTEGRATED SECURITY=SSPI;INITIAL CATALOG=DashboardSQL-2K5;DATA SOURCE=XXXXXXXX;
XXXXXXXXX is obviously the name of my server blanked out
Please help as I wish to deploy this report and it is just sods law that it stops working today.
Regards
May 30, 2006 at 5:47 am
Further poking around etc showed me that there were a couple of setting adrift in the various places.
I am now at the point where I have got it to work, the only problem I now have is that unless I grant DomainName\Domain Users as sysadmin in the permissions for the database, I get an error similar to below when I try to go to
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for data set 'srcqry_weeklydatadate'. (rsErrorExecutingCommand)
For more information about this error navigate to the report server on the local server machine, or enable remote errors
Now that query it is trying to run is a select query in the report that populates the first parameter box on the report selection criteria. What do I need to change in the report to prevent this from happening. I can't very well allow all and sundrey in as sysadmin for obvious reasons.
Regards
May 31, 2006 at 4:38 am
Have you tried giving the user DataReader access to the database (or if you're using a stored procedure, Execute permission) rather than SysAdmin?
May 31, 2006 at 8:35 am
I found that setting security and privilege levels for Reporting Services to be a difficult exercise unless you wear both the DBA and Network Administrator hats at your organization. Reporting Services consist of five or six separate applications and services that each require it own rights and privileges, Ouch!
In the case of your specific problem I've found that creating a Sql User and then using it's credentials to access the database was the best way to get around the privilege problems in that one specific instance.
Hope this helps.
May 31, 2006 at 3:45 pm
I agree with Dan. We use a generic SQL account with db_reader access to our warehouse. The developers develop locally with their windows account and the datasources on the Report Server have the generic SQL account entered.
This approach has worked well for us to date. Our security model for the data warehouse is fairly simple at this stage however.
Martin
November 17, 2016 at 11:08 am
Been struggling with this for a couple of days. The post to add a generic user for access from SSRS solved the problem!. Wasn't an issue with connecting to the datasource, there was a security issue when accessing the data.
Thanks!
Bill
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply