rsErrorExecutingCommand

Question

I am getting the error "... Query execution failed for dataset 'DataSet1'. (rsErrorExecutingCommand)..." when users try to run any report in our SQL 2008 database.  I changed one report and gave it [public] permissions on the stored procedure and then it worked.  However, I don't want to do that for every stored procedure used in every report.  I have the security on the Reporting Server set to windows authentication so I thought valid network user could run the reports...but apparently not.  What can I do to "globally" allow network users to access any report on that server?  Thanks.

Answer 1

Hi David,

If you want to go with Windows Security, each user running the report should have access to the data sources(stored procedures etc) being used by the report. You can setup the security at a higher level(at the database level for example) if you want to avoid setting up granular permissions.

Another option is to create a data source and store credentials in the data source(http://msdn.microsoft.com/en-us/library/ms159736.aspx) and use this data source in your reports. This way, users won't need to have access to the data source, but instead will use the credentials stored in the data source to connect to the database.

Hope this helps!

---

Shahfaisal Muhammed http://shahfaisalmuhammed.blogspot.com

Answer 2

I added BuiltIn\Users to the Security logins of the database and assumed that would give all network users access but it still gives the error when the users try to run the report.

Answer 3

You'll need to map the login to the database which the report is pulling the data from. If the report is using a stored procedure, then you'll need to grant the right to execute the stored procedure as well.

Follow these links -

http://msdn.microsoft.com/en-us/library/ms345484.aspx

http://stackoverflow.com/questions/5428406/grant-execute-permission-for-a-user-on-all-stored-procedures-in-database

---

Shahfaisal Muhammed http://shahfaisalmuhammed.blogspot.com