Cindyfiller
45 pts. | Oct 19 2009 9:37PM GMT
Under site settings / system role assignments I’ve added this user as a system user. That role has the following rights: execute report definitions, view report server properties, view shared schedules. All of the other options have to do with Managing and I didn’t feel she needed those rights.
Cindyfiller
45 pts. | Nov 2 2009 8:08PM GMT
Sorry for the delay in answering this. I was out of town. I did find the spot that I had missed. In management studio I hadn’t give users the dbreader role. That seemed to take care of this issue. But I have one report that I’m still having problems with. There is a data set created within that report and now users can’t run this because of a security issue with the dataset. They can run other reports, but not this one.
mrdenny
46765 pts. | Nov 10 2009 12:48AM GMT
Log into the SQL Server using one of the users accounts and run the query manually. This should tell you where the problem is coming from. Or turn on remote errors in the web.config for the report server.
Cindyfiller
45 pts. | Nov 16 2009 2:21PM GMT
Sorry for the delay in responding. I did find the issue on this. I have give them public access, but needed to give the users dbread access against the data warehouse. Users can run all reports except for one. That one has a stored procedure and users are getting an error message that they don’t have access to the dataset created from the stored procedure. I’ve gone through and given them the same rights as the data warehouse on the stored procedure, but so far that hasn’t worked.
Mrdenny
46765 pts. | Nov 17 2009 8:57PM GMT
You will need to give the users the right to run the stored procedure.
GRANT EXEC ON YourStoredProcedure TO YourUserOrRole
Cindyfiller
45 pts. | Nov 18 2009 10:41PM GMT
I use the GUI interface in management studio. I did give execute access to this user and it still didn’t work. I opened up the stored procedure and noticed that it was creating another view in the procedure. While the view was in the data warehouse that the user had access to, I did go in and give specific rights to that view also. But the user still gets the same error. I have no clue what to try now.






