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