Showing posts with label role. Show all posts
Showing posts with label role. Show all posts

Monday, March 26, 2012

rsAccessDenied even for the Content Manager role

I have the Content Manager rights on a folder and on a report for my user.
When I try to edit ther report properties I got the error
the permissions granted to user `domain\user` are insufficient for
performing this operation (rsAccessDenied)
I am able to upload, create folders, create data source, upload file, but
not to view the report properties
--
AlexSounds like someone changed the Security for that Particular report, so you
can't mess with it...
All of the things you can do, have perms at the folder level...Report
properties can be set at the report level, so if someone removed
ContentManager Role from the specific report, you'd get the behaviour you are
seeing..
Hope this helps.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
See you at the PASS Conference!
"Alex" wrote:
> I have the Content Manager rights on a folder and on a report for my user.
> When I try to edit ther report properties I got the error
> the permissions granted to user `domain\user` are insufficient for
> performing this operation (rsAccessDenied)
> I am able to upload, create folders, create data source, upload file, but
> not to view the report properties
> --
> Alex|||I just verified it and It has the Content Manager perms
I even created a new folder with the builtin\Administrators Content
Manager and the Server\user Content Manager too.
I checked the report's security tab, and in all the reports in that folder I
have both, the Builtin\Administrators Content Manager and the Server\user
Content Manager permissions.
But Still having the rsAccessDenied Error
I would appreciate very much any help about it
Thanks
--
Alex
"Wayne Snyder" wrote:
> Sounds like someone changed the Security for that Particular report, so you
> can't mess with it...
> All of the things you can do, have perms at the folder level...Report
> properties can be set at the report level, so if someone removed
> ContentManager Role from the specific report, you'd get the behaviour you are
> seeing..
> Hope this helps.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> I support the Professional Association for SQL Server ( PASS) and it''s
> community of SQL Professionals.
> See you at the PASS Conference!
>
> "Alex" wrote:
> > I have the Content Manager rights on a folder and on a report for my user.
> >
> > When I try to edit ther report properties I got the error
> > the permissions granted to user `domain\user` are insufficient for
> > performing this operation (rsAccessDenied)
> >
> > I am able to upload, create folders, create data source, upload file, but
> > not to view the report properties
> >
> > --
> > Alex|||I had the same problem you described and fixed it by granting the NT group
the 'Content Manager' permissions at the 'Root' of the Report Server site.
After doing this the permissions were applied correctly to the Folders
underneath this.
Hope this helps.
Diran
"Alex" wrote:
> I just verified it and It has the Content Manager perms
> I even created a new folder with the builtin\Administrators Content
> Manager and the Server\user Content Manager too.
> I checked the report's security tab, and in all the reports in that folder I
> have both, the Builtin\Administrators Content Manager and the Server\user
> Content Manager permissions.
> But Still having the rsAccessDenied Error
> I would appreciate very much any help about it
> Thanks
> --
> Alex
>
> "Wayne Snyder" wrote:
> > Sounds like someone changed the Security for that Particular report, so you
> > can't mess with it...
> >
> > All of the things you can do, have perms at the folder level...Report
> > properties can be set at the report level, so if someone removed
> > ContentManager Role from the specific report, you'd get the behaviour you are
> > seeing..
> >
> > Hope this helps.
> > --
> > Wayne Snyder MCDBA, SQL Server MVP
> > Mariner, Charlotte, NC
> >
> > I support the Professional Association for SQL Server ( PASS) and it''s
> > community of SQL Professionals.
> > See you at the PASS Conference!
> >
> >
> > "Alex" wrote:
> >
> > > I have the Content Manager rights on a folder and on a report for my user.
> > >
> > > When I try to edit ther report properties I got the error
> > > the permissions granted to user `domain\user` are insufficient for
> > > performing this operation (rsAccessDenied)
> > >
> > > I am able to upload, create folders, create data source, upload file, but
> > > not to view the report properties
> > >
> > > --
> > > Alex|||Thanks Diran,
It worked, I just granted the "My Reports" permissions.
Thanks again!
--
Alex
"Diran" wrote:
> I had the same problem you described and fixed it by granting the NT group
> the 'Content Manager' permissions at the 'Root' of the Report Server site.
> After doing this the permissions were applied correctly to the Folders
> underneath this.
> Hope this helps.
> Diran
>
> "Alex" wrote:
> > I just verified it and It has the Content Manager perms
> >
> > I even created a new folder with the builtin\Administrators Content
> > Manager and the Server\user Content Manager too.
> >
> > I checked the report's security tab, and in all the reports in that folder I
> > have both, the Builtin\Administrators Content Manager and the Server\user
> > Content Manager permissions.
> >
> > But Still having the rsAccessDenied Error
> >
> > I would appreciate very much any help about it
> > Thanks
> >
> > --
> > Alex
> >
> >
> > "Wayne Snyder" wrote:
> >
> > > Sounds like someone changed the Security for that Particular report, so you
> > > can't mess with it...
> > >
> > > All of the things you can do, have perms at the folder level...Report
> > > properties can be set at the report level, so if someone removed
> > > ContentManager Role from the specific report, you'd get the behaviour you are
> > > seeing..
> > >
> > > Hope this helps.
> > > --
> > > Wayne Snyder MCDBA, SQL Server MVP
> > > Mariner, Charlotte, NC
> > >
> > > I support the Professional Association for SQL Server ( PASS) and it''s
> > > community of SQL Professionals.
> > > See you at the PASS Conference!
> > >
> > >
> > > "Alex" wrote:
> > >
> > > > I have the Content Manager rights on a folder and on a report for my user.
> > > >
> > > > When I try to edit ther report properties I got the error
> > > > the permissions granted to user `domain\user` are insufficient for
> > > > performing this operation (rsAccessDenied)
> > > >
> > > > I am able to upload, create folders, create data source, upload file, but
> > > > not to view the report properties
> > > >
> > > > --
> > > > Alex

rsAccessDenied

The permissions granted to user '[user]' are insufficient for performing this operation. (rsAccessDenied) Get Online Help

I have given role (literally every possible role just to see) access in SQL Manager without success. And the permissions on the directory were set to Everyone Full Control (just to try to get it to work).

Any ideas?

Hi,

Which folder are you trying to deploy to? Which OS are you using? Try allocating the Report Manager role to the user and also to the folder.

These links may be helpful

http://technet.microsoft.com/en-us/library/aa337491.aspx

http://msdn2.microsoft.com/en-us/library/aa237755(SQL.80).aspx

http://msdn2.microsoft.com/en-us/library/aa337471.aspx

Search for "Setting Permissions in Reporting Services" or "Using Role-based Security" in SQL Server Books Online.

HTH,
Suprotim Agarwal

--
http://www.dotnetcurry.com
--

|||

Thanks. But, I've already been through all of that. And, I've searched this group for answers. I see that some found a solution; but those modifications aren't working, in my case.

Do you know if there is a problem with the port? The port is currently set at 8888.

|||

Another thought..

The Report Server machine that I am using is on a DOMAIN. The users are configured on the DOMAIN - not the local machine. The (2 Report Server) roles that are available from the Computer Management screen are not used with the users. However, they are added in SQL Manager (with their DOMAIN credentials) and given the proper roles (RSExecRole, etc). And the roles (2 filesystem) are assigned and given control over the directory for the Report Server configuration.

NT Authentication is being used. Does each network user need to be configured in "Computer Management -> Users/Groups" for some reason? Even though they are DOMAIN users - not LOCAL.

|||

Never Mind. I added a DOMAIN user to the "Computer Management" Report Server roles and I still get the error.

|||

Hi,

I am sure you must have done a lot of searching before asking this question, but at times the smallest of details can be helpful. So let us revisit this. I always follow these steps i noted sometime back and recommended by a mvp called bruce:

1. I hope you have gone through the link which i gave you earlier. That explains the role based security of reporting services. We have to use that to assign permissions. We will try not to give permissions using IIS.

2. Assuming you belong to the Local Admin group, create a local group on the deployment machine and add the domain users to that local group. Then assign this local group the appropriate role to access reporting services.

3. In IIS there are two sites Report Server and reports. Make sure that IIS has not allowed anonymous access for them.

HTH,
Suprotim Agarwal

--
http://www.dotnetcurry.com
--

|||

1. I hope you have gone through the link which i gave you earlier. That explains the role based security of reporting services. We have to use that to assign permissions. We will try not to give permissions using IIS.

Yep, I had been to that link even before you posted it.

2. Assuming you belong to the Local Admin group, create a local group on the deployment machine and add the domain users to that local group. Then assign this local group the appropriate role to access reporting services.

Yep. I have admin-ability on that machine. I created a group and added users to the group that was then given role access; and I tried giving role access directly to the users. Either way, I get the error.

3. In IIS there are two sites Report Server and reports. Make sure that IIS has not allowed anonymous access for them.

Yep. Using NT Authentication throughout.

Thanks. But, I've already been though all of that.

I have noticed that when going through Localhost (for testing it works), it shows that the Authentication is "NTLM"; but when going through the domain it shows that the Authentication is "Negotiate". I don't know if that makes a difference or not.

BTW.. I tried uninstalling the ReportServer stuff from Add/Remove and got an error (and then more errors) leading to the installer crashing. Now, ReportServer didn't actually uninstall (it is still there - in the GUI anyway); but doesn't work. And installing it again doesn't fix it. I was hoping that a fresh install would fix whatever it was. So, Report Services is completely broken at this point.

sql

rsAccessDenied

The permissions granted to user '[user]' are insufficient for performing this operation. (rsAccessDenied) Get Online Help

I have given role (literally every possible role just to see) access in SQL Manager without success. And the permissions on the directory were set to Everyone Full Control (just to try to get it to work).

Any ideas?

Hi,

Which folder are you trying to deploy to? Which OS are you using? Try allocating the Report Manager role to the user and also to the folder.

These links may be helpful

http://technet.microsoft.com/en-us/library/aa337491.aspx

http://msdn2.microsoft.com/en-us/library/aa237755(SQL.80).aspx

http://msdn2.microsoft.com/en-us/library/aa337471.aspx

Search for "Setting Permissions in Reporting Services" or "Using Role-based Security" in SQL Server Books Online.

HTH,
Suprotim Agarwal

--
http://www.dotnetcurry.com
--

|||

Thanks. But, I've already been through all of that. And, I've searched this group for answers. I see that some found a solution; but those modifications aren't working, in my case.

Do you know if there is a problem with the port? The port is currently set at 8888.

|||

Another thought..

The Report Server machine that I am using is on a DOMAIN. The users are configured on the DOMAIN - not the local machine. The (2 Report Server) roles that are available from the Computer Management screen are not used with the users. However, they are added in SQL Manager (with their DOMAIN credentials) and given the proper roles (RSExecRole, etc). And the roles (2 filesystem) are assigned and given control over the directory for the Report Server configuration.

NT Authentication is being used. Does each network user need to be configured in "Computer Management -> Users/Groups" for some reason? Even though they are DOMAIN users - not LOCAL.

|||

Never Mind. I added a DOMAIN user to the "Computer Management" Report Server roles and I still get the error.

|||

Hi,

I am sure you must have done a lot of searching before asking this question, but at times the smallest of details can be helpful. So let us revisit this. I always follow these steps i noted sometime back and recommended by a mvp called bruce:

1. I hope you have gone through the link which i gave you earlier. That explains the role based security of reporting services. We have to use that to assign permissions. We will try not to give permissions using IIS.

2. Assuming you belong to the Local Admin group, create a local group on the deployment machine and add the domain users to that local group. Then assign this local group the appropriate role to access reporting services.

3. In IIS there are two sites Report Server and reports. Make sure that IIS has not allowed anonymous access for them.

HTH,
Suprotim Agarwal

--
http://www.dotnetcurry.com
--

|||

1. I hope you have gone through the link which i gave you earlier. That explains the role based security of reporting services. We have to use that to assign permissions. We will try not to give permissions using IIS.

Yep, I had been to that link even before you posted it.

2. Assuming you belong to the Local Admin group, create a local group on the deployment machine and add the domain users to that local group. Then assign this local group the appropriate role to access reporting services.

Yep. I have admin-ability on that machine. I created a group and added users to the group that was then given role access; and I tried giving role access directly to the users. Either way, I get the error.

3. In IIS there are two sites Report Server and reports. Make sure that IIS has not allowed anonymous access for them.

Yep. Using NT Authentication throughout.

Thanks. But, I've already been though all of that.

I have noticed that when going through Localhost (for testing it works), it shows that the Authentication is "NTLM"; but when going through the domain it shows that the Authentication is "Negotiate". I don't know if that makes a difference or not.

BTW.. I tried uninstalling the ReportServer stuff from Add/Remove and got an error (and then more errors) leading to the installer crashing. Now, ReportServer didn't actually uninstall (it is still there - in the GUI anyway); but doesn't work. And installing it again doesn't fix it. I was hoping that a fresh install would fix whatever it was. So, Report Services is completely broken at this point.

sql

Tuesday, March 20, 2012

rs.exe scripts

I'm a SQL Server DBA and will be playing the role of a
SQL2000 Reporting Services administrator. To tightly
control the environment and keep track of all the changes,
I'm considering to implement a policy that requires all
changes to Reporting Services and reports be released into
production via VB.NET scripts for rs.exe, and all such
scripts be submitted to me for review first.
I'd like to bounce this off you guys to see (1) whether
I'm going overboard, and (2) whether all changes can be
implemented via RS scripts.
JoeAs far as your first question, about going overboard... it's not clear to me
how this policy can be enforced. Users could just run any script, or write
their own app to talk to the server. If you really want to prevent users
from performing certain actions, I recommend using the built in security to
give users only the permissions they need for the actions you want them to
take.
As far as functionality... rs.exe has complete access to the SOAP API.
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Joe Bourne" <anonymous@.discussions.microsoft.com> wrote in message
news:46ae01c4734b$5b917fa0$a401280a@.phx.gbl...
> I'm a SQL Server DBA and will be playing the role of a
> SQL2000 Reporting Services administrator. To tightly
> control the environment and keep track of all the changes,
> I'm considering to implement a policy that requires all
> changes to Reporting Services and reports be released into
> production via VB.NET scripts for rs.exe, and all such
> scripts be submitted to me for review first.
> I'd like to bounce this off you guys to see (1) whether
> I'm going overboard, and (2) whether all changes can be
> implemented via RS scripts.
> Joe|||Thanks, Brian!
I was thinking in the line of SQL Server's DDL vs DML, if
I can make such a similar distinction in SSRS. So
for 'DDL' type of changes, I'll try to enforce the rs
scripting requirement, whereas for 'DML' type of changes,
the users can make whatever changes however they want.
Just like in SQL Server, the users can
insert/delete/update their data with their permissions,
and I really don't care what they do. But when it comes to
schema changes, I make sure that thye submit scripts to me
first.
Now, can I classify SSRS tasks into 'DDL' and 'DML', and
assign security to allow DML changes only?
Joe
>--Original Message--
>As far as your first question, about going overboard...
it's not clear to me
>how this policy can be enforced. Users could just run
any script, or write
>their own app to talk to the server. If you really want
to prevent users
>from performing certain actions, I recommend using the
built in security to
>give users only the permissions they need for the actions
you want them to
>take.
>As far as functionality... rs.exe has complete access to
the SOAP API.
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights
>"Joe Bourne" <anonymous@.discussions.microsoft.com> wrote
in message
>news:46ae01c4734b$5b917fa0$a401280a@.phx.gbl...
>> I'm a SQL Server DBA and will be playing the role of a
>> SQL2000 Reporting Services administrator. To tightly
>> control the environment and keep track of all the
changes,
>> I'm considering to implement a policy that requires all
>> changes to Reporting Services and reports be released
into
>> production via VB.NET scripts for rs.exe, and all such
>> scripts be submitted to me for review first.
>> I'd like to bounce this off you guys to see (1) whether
>> I'm going overboard, and (2) whether all changes can be
>> implemented via RS scripts.
>> Joe
>
>.
>