February 7, 2013 at 6:40 am
I have an install of SQL Server 2008 R2 Reporting Services running on a virtual machine. My problem is that I have a person in the Content Manager SSRS role and he cannot create a new data source using Report Manager. He gets the following error: The permissions granted to user 'xxxx' are insufficient for performing this operation. (rsAccessDenied) The same person has no problems deploying a data source from BIDS and he can upload reports and do all the other functions of Content Manager using Report Manager. I confirmed that the Content Manager role has ‘manage data sources’ task enabled and that the person was not in any other roles that would stop him from creating a data source. Everything works fine and as expected in SQL Server 2008 Reporting Services. In fact, the permissions/roles, etc. all came over from SQL Server 2008. Does anyone have any thoughts on this? Thanks…
February 21, 2013 at 2:41 pm
Sounds like a rights issue. Do they have folder navigation to the home folder? I found that this sometimes restricts the ability to view other folders below it.
March 5, 2013 at 7:07 pm
By default, BIDS doesn't overwrite datasources on the report manager website so unless your user has created new datasources and deployed them then I suspect they might not actually have deployed datasources before. Easy to test by creating the datasource with a new name in BIDS and testing both the connection and the deployment (does the new datasource appear in report manager).
But in your question you say the user has problems "creating" the datasource in report builder yet they've had no problems "deploying" from BIDS, which might be a second issue.
Creating a datasource in report builder involves both permission to connect to the datasource using whatever credentials are supplied (does this part work? does it work for that exact same datasource in BIDS?) as well as saving the object in the datasource folder on the server. If the user (on their same machine with the same windows login using BIDS) is able to deploy a new datasource to the server, then there is no reason that report builder would deny them access - both processes use the current windows login for permissions.
I would go back to the user and double check those things.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply