SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSRS Report Security -


SSRS Report Security -

Author
Message
lnpurdie
lnpurdie
SSC Veteran
SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)

Group: General Forum Members
Points: 234 Visits: 89

SSRS 2012 -we have aset of report all using the same data source: XXXXX

They were developed years ago, but I think when theymigrated from 2008 to 2012 something changed. There are a set of “click through” reports and the report ID clickedthrough to depends on the special failure severity and RFP.(Contract rule). Sowhen the team tested these they may not have ran across the few in the set thatuse embedded SQL Text. Each of these reportsfail

Why? They use the samedata source. It is definitely thesesmall subset that have trouble, none of the rest.

Any clues?

An error has occurredduring report processing. (rsProcessingAborted)

Query execution failedfor dataset 'ServiceName'. (rsErrorExecutingCommand)

The SELECT permissionwas denied on the object 'ServiceRequired', database 'XXXXX', schema 'dbo'.


Thom A
Thom A
SSC-Forever
SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)

Group: General Forum Members
Points: 45636 Visits: 15487
The error message is telling you the problem here, the user/login the report is running under is being denied permission to select from the object "ServiceRequired" on the database "XXXXX".

Give the login/user access to select from the object.


Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does :-P

Please always remember to encapsulate your code in IFCode Markup. For example [code=sql] [/code].
Click here to read Jeffs Guide on how to post SQL questions, and get swift and helpful answers from the community
FridayNightGiant
FridayNightGiant
SSCarpal Tunnel
SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)

Group: General Forum Members
Points: 4149 Visits: 3198
Have you checked that the user for the data source has select permission on the ServiceRequired object in the referenced database?
lnpurdie
lnpurdie
SSC Veteran
SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)

Group: General Forum Members
Points: 234 Visits: 89
Well I cannot check - the DBAs will have to. I was surprises as the SAME Data Source used by the other data sets which would be accessing the same schema - using procedures. The obvious was permissions, yes. Thought maybe somehow the SQL Text vs Procedure was part of the problem but I suspect its is as obvious as it appears. The DBA(s) maybe only have granted Exec on report procedures - and not granted SELECT on dbo. Its an inherited solution from 2009. I'll shift it upstream and not waste my time on it.


Thanks guys. Sometimes the obvious is the best answer
Thom A
Thom A
SSC-Forever
SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)

Group: General Forum Members
Points: 45636 Visits: 15487
lnpurdie - Tuesday, August 1, 2017 9:34 AM
Well I cannot check - the DBAs will have to. I was surprises as the SAME Data Source used by the other data sets which would be accessing the same schema - using procedures. The obvious was permissions, yes. Thought maybe somehow the SQL Text vs Procedure was part of the problem but I suspect its is as obvious as it appears. The DBA(s) maybe only have granted Exec on report procedures - and not granted SELECT on dbo. Its an inherited solution from 2009. I'll shift it upstream and not waste my time on it.


Thanks guys. Sometimes the obvious is the best answer

Provided that the owner of the objects is the same and the objects are in the same database, then the permissions would be inherited. If, however, this is not the case, then permission will need to be granted on not only the SP, but any objects which have different owners, or are in a different database. I would suggest that this is the case here.

Note, cross database ownership does exist, but comes with its own security risks, so is often not switched on, and is not enabled by default.



Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does :-P

Please always remember to encapsulate your code in IFCode Markup. For example [code=sql] [/code].
Click here to read Jeffs Guide on how to post SQL questions, and get swift and helpful answers from the community
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search