The permissions granted to the user are not enough to complete this operation. (RsAccessDenied) "}

I created a report model using SSRS (2005) and published it on a local server. But when I tried to run the report for a model published using Report Builder, I get the following error.

Report execution error. The permissions granted to the user are not enough to complete this operation. (rsAccessDenied)

+71
reporting-services reporting reportingservices-2005
Sep 25 '08 at 11:52
source share
20 answers

This is due to the lack of privileges for the user who runs Report Builder, just give this user or group the privilege to run Report Builder. Please visit this article.

Or for quick access:

  • Launch Internet Explorer using the Run As Administrator command
  • Open http: // localhost / reports
  • Go to the properties tab (SSRS 2008).
  • Security-> Assign New Roles
  • Add DOMAIN / USERNAME or DOMAIN / USERGROUP
  • Check Report Builder
+70
Jun 20 '11 at 6:23
source share

I know this for a long time, but you (or any other new users) can solve this problem with

  • Add [Domain \ User] to Administrator , IISUser , SQLReportingUser .
  • Delete encryption key in SSRS configuration tools
  • Restart Database Change in SSRS Configuration Tools
  • Open WebServiceUrl from SSRS configuration tools ( http: // localhost / reportserver )
  • manual folder reporting
  • go to "Properties of the created folder" and add these roles to the security system ( built-in \ user, built-in \ administrator, domain \ user )
  • Expand your reports and solve your problem.
+17
Jun 09 '10 at 6:40
source share

Right-click Microsoft BI β†’ Click Run as Administrator β†’ either open an existing SSRS report, or create a new SSRS report, and then expand your report after it is executed, and you will get one web URL to view your report. Copy this URL and paste it into your web browser (Run as administrator) and you will get a presentation of your report. You can use Internet Explorer, which will be necessary for the web service.

If this is wrong, please forgive me, since I made it so that I just wrote.

+15
Jul 06 '12 at 15:40
source share

Verify that you have access to the http: // localhost / reports URL using the SQL Reporting Services configuration. For this:

  • Open the Reporting Services Configuration Manager β†’ then connect to the report server instance β†’, then click the Report Manager URL.
  • On the Report Manager URL page, click the Advanced button β†’, and then click Add in Multiple Identifiers for Report Manager.
  • In the Add Report Manager URL drop-down box, select the host header and enter: localhost
  • Click OK to save the changes.
  • Now start / run Internet Explorer using Run as Administator ... (NOTE: If you do not see the "Site Settings" link in the upper left corner, but http: // localhost / reports , this is probably because you aren " starting IE as an administrator or you did not assign your computers \ username "domain for reporting services roles, see how to do this in the next few steps.)
  • Then go to: http: // localhost / reports (you may have to log in with your username and computer password)
  • Now you should go to the main page of SQL Server Reporting Services: http: //localhost/Reports/Pages/Folder.aspx
  • On the home page, open the Properties tab and click Assign New Role
  • In the "Group or username" text box, add "domain \ username" that was in the error message (in my case, I added: DOUGDELL3-PC \ DOUGDELL3 for "domain \ username", in your case you can find the domain \ name user for his computer in the rsAccessDenied error message).
  • Now check all the boxes; Browser, Content Manager, My Reports, Publisher, Report Builder and click OK.
  • Now the domain name \ username should be assigned to Roles, which will give you access to report deployment on the report server. If you are using Visual Studio or SQL Server Business Intelligence Development Studio to deploy reports on a local report server, you should now be able to.
  • Hope this helps you resolve the rsAccessDenied report server error message ...

Just to let you know that this guide was done on a Windows 7 computer with SQL Server Reporting Services 2008.

Link: http://techasp.blogspot.co.uk/2013/06/how-to-fix-reporting-services.html

+6
Aug 26 '15 at 11:58
source share

in the Site settings section in the report manager> Configure role definitions at the system level> check the ExecuteReport Defination parameter then Create a system user group, provide access to this group in Connect to the report services database in the server properties and add the group and allow access as a system user. .. It should work

+5
Dec 09 '08 at 21:34
source share

I have SQL2008 / Windows 2008 Enterprise, and this is what I had to do to fix rs.accessdenied , 404, 401, and 503 errors:

  • Added NT users for SQL Server and IIS_USR Group report users
  • I changed the SQL Reporting Service to a local account (it was a domain with a local administrator).
  • I deleted the encryption key in the configuration of Reporting Services (last tab in the list)
  • and THEN it worked.
+4
Aug 24 '09 at 23:22
source share

You can also verify that the identifier in the application pool has the correct permissions.

  • Go to IIS Manager

  • Click Application Pools

  • Define the application pool on the site where the reports are deployed,

  • Ensure that the identifier is set to any service account or user account with administrator rights.

  • You can change the identifier by stopping the pool, right-clicking it and selecting "Advanced Settings" ...

In the "Process Model" section, the "Identification" field is indicated.

+4
Mar 31 '11 at 17:03
source share

An old but relevant question. I decided in 2012 by logging into the report server and:

  • go to http: // localhost / reports /
  • Click "Site Settings" in the upper right corner (available only when entering the report server)
  • Go to the "Security" tab and click "Assign New Role"
  • Added by my DOMAIN \ USERNAME as system administrator

I can’t say that I like this solution, but I need something that worked, and it worked. Hope this helps someone else.

+3
May 22 '15 at 18:57
source share

I used the following steps and it works for me.

Open Reporting Services Configuration Manager β†’ then connect to the report server instance β†’, then click the Report Manager URL.

On the Report Manager URL page, click the Advanced button β†’, and then click Add in Multiple Identifiers for Report Manager.

In the Add Report Manager URL drop-down box, select the host header and enter: localhost Click OK to save the changes.

Then:

  • copied report server url
  • Launch Google chrome / Internet Explorer as administrator
  • Paste the URL into the address bar and press enter.

It works great for me in Internet Explorer and Google Chrome, but not for Mozilla Firefox.

In case Firefox asks for a username and password, I provide it, but it does not work. I am an administrator and I have every right.

I made another 1 set of changes to "User Account Management Settings" to never notify.

If you get this type of exception when you deploy this report from Visual Studio, follow these steps:

  • Open Google Chrome / Internet Explorer with administrator privileges.
  • Open the report server URL in it.

3. Click "Assign New Role", then add the username and select Roles enter image description here

  1. Click OK.
  2. Now deploy the report from Visual Studio, it will work and deploy the reports on the specified server.
+3
Jan 31 '16 at 19:00
source share

Problem:

Error rsAccessDenied: To perform this operation, the rights granted to the user "User \ User" are not enough.

Decision:

Click Folder Setup> Assign New Role. Then enter "User \ User" in the "Group or username" text box. Check the "Roles" boxes that you want the user to have.

+2
Feb 23 '14 at 1:31
source share

What worked for me:

 Open localhost/reports Go to properties tab (SSRS 2008) Security->New Role Assignment Add DOMAIN/USERNAME or DOMAIN/USERGROUP Check Report builder 
+1
Mar 12 '14 at 10:20
source share

It worked for me - -go to the report manager, check the site settings-> Security β†’ Assign a new role-> add user

-Also go to the datasets in the report manager β†’ your report dataset β†’ Security β†’ Assign a new role β†’ add a user with the required role.

Thank!

+1
Mar 11 '16 at 22:57
source share

Like Nasser, I know that it was recently, but I wanted to publish my solution for everyone who has this problem in the future.

I had my report set up to use a data connection in a data connection library hosted in SharePoint. My problem was that I did not have an approved data connection, so it could be used by other users.

Another thing to look for is to make sure that permissions on this data connection library also allow selected users to read.

Hope this helps someone sooner or later!

0
Jul 26 '13 at 17:54
source share

For SQL Reporting Services 2012 - SP1 and SharePoint 2013.

I have the same problem: Permissions granted to the user [AppPoolAccount] are not enough to complete this operation.

I went into the settings of the service application, clicked the "Key Management" button, then "Change" and updated the key.

0
Sep 25 '13 at 18:07
source share

Open Internet Explorer as an administrator.

Open the url report http://machinename/reportservername

then in the settings of the "folder" permission is given to the required user groups.

0
Jul 09 '14 at 7:03
source share

Thanks for sharing. After fighting for 1.5 days, I noticed that the report server was configured with the wrong IP address. It was configured with a backup domain IP address, which is disabled. I identified this in the user group configuration where the domain name was not specified. Changed IP and restart report server. The problem is resolved.

0
Jan 05 '16 at 10:05
source share

I know this for a long time, but can be useful for any other new visitors,

I decided to pass the username, password and domain when requesting SSRS reports, so I created one class that implements IReportServerCredentials.

  public class ReportServerCredentials : IReportServerCredentials { #region Class Members private string username; private string password; private string domain; #endregion #region Constructor public ReportServerCredentials() {} public ReportServerCredentials(string username) { this.Username = username; } public ReportServerCredentials(string username, string password) { this.Username = username; this.Password = password; } public ReportServerCredentials(string username, string password, string domain) { this.Username = username; this.Password = password; this.Domain = domain; } #endregion #region Properties public string Username { get { return this.username; } set { this.username = value; } } public string Password { get { return this.password; } set { this.password = value; } } public string Domain { get { return this.domain; } set { this.domain = value; } } public WindowsIdentity ImpersonationUser { get { return null; } } public ICredentials NetworkCredentials { get { return new NetworkCredential(Username, Password, Domain); } } #endregion bool IReportServerCredentials.GetFormsCredentials(out System.Net.Cookie authCookie, out string userName, out string password, out string authority) { authCookie = null; userName = password = authority = null; return false; } } 

when calling SSRS Reprots, put the following code snippet

  ReportViewer rptViewer = new ReportViewer(); string RptUserName = Convert.ToString(ConfigurationManager.AppSettings["SSRSReportUser"]); string RptUserPassword = Convert.ToString(ConfigurationManager.AppSettings["SSRSReportUserPassword"]); string RptUserDomain = Convert.ToString(ConfigurationManager.AppSettings["SSRSReportUserDomain"]); string SSRSReportURL = Convert.ToString(ConfigurationManager.AppSettings["SSRSReportURL"]); string SSRSReportFolder = Convert.ToString(ConfigurationManager.AppSettings["SSRSReportFolder"]); IReportServerCredentials reportCredentials = new ReportServerCredentials(RptUserName, RptUserPassword, RptUserDomain); rptViewer.ServerReport.ReportServerCredentials = reportCredentials; rptViewer.ServerReport.ReportServerUrl = new Uri(SSRSReportURL); 

SSRSReportUser, SSRSReportUserPassword, SSRSReportUserDomain, SSRSReportFolder are defined in web.config files.

0
Oct 24 '16 at 14:29
source share

After setting up SSRS 2016, I RDP'd to the server (Windows Server 2012 R2) went to the reports URL ( https://reports.fakeserver.net/Reports/browse/ ) and created the header of the FakeFolder folder; everything seemed to be working fine. Then I disconnected from the server, looked at it on the same URL, logged in as the same user and found an error below.

The permissions granted to fakeserver \ mitchs are not sufficient for this operation.

Confused, I tried almost all the solutions offered on this page, and could not create the same behavior both locally and externally when navigating the URL and authentication. Then I clicked on the FakeFolder ellipsis, clicked β€œManage”, clicked β€œSecurity” (on the left side of the screen) and added myself as a user with full permissions. After disconnecting from the server, I looked at https://reports.fakeserver.net/Reports/browse/FakeFolder and was able to view the contents of the folder without encountering a permission error. However, when I clicked on the house, I got a permission error.

For my purposes, this was good enough, since no one else would need to go to the root URL, so I just made a note when I needed to make changes to SSRS to connect to the server first and then go to the reporting URL.

0
Apr 25 '17 at 13:51 on
source share

What worked for me:

  • Go to site setup
  • Click Configure Site Security
  • Click the "Assign New Role" button on the top line.
  • Give the new role the following name "Everyone"
  • Of the available roles, provide only the "System User"
  • Click Apply

That should do it

Good luck

-one
04 Sep '09 at 2:23
source share

Launch BIDS as an administrator, despite existing membership in the Administrators group.

-one
May 03 '12 at 7:02 a.m.
source share



All Articles