Only User with Administrator Role able to run Report

(0) Share

Report

Posted on by Community Member

I have been deploy SSRS Report in CRM 2016. Other user's trying to run the reports from CRM. But they all get error message (rsaccessdenied). All the users are the member of Reporting Group. Also has permission in the security role against report.

I have tried this following article, but no luck:

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

So far, we have found the answer. The user needs to be a Local Administrator in the computer (server) that sql server installed. After adding the users as Administrator on the Computer Server. They can run the reports.

But, i think its strange that only local administator who can run the reports. Is it normal ? or did i make a mistake during setup the reporting server ?

*This post is locked for comments

All responses (6)

Answers (0)

Community Member on at

Like (0)

Report

RE: Only User with Administrator Role able to run Report

@Nithya: Yes, the users have read privilege on that entities
Suggested answer

Nithya Gopinath 17,078 on at

Like (0)

Report

RE: Only User with Administrator Role able to run Report

Hi Fikri,

Do you have Read Privilege of entities that are queried by the report?

See: community.dynamics.com/.../198201
Community Member on at

Like (0)

Report

RE: Only User with Administrator Role able to run Report

@maxxsir: yes i did, i already change from User to Organization during importing the rdl file
Community Member on at

Like (0)

Report

RE: Only User with Administrator Role able to run Report

@David Jennaway: we only tried with SQL-based report
Community Member on at

Like (0)

Report

RE: Only User with Administrator Role able to run Report

Did you check the Administration tab in the report wizard and switch it from User to Organization? Also check actions/sharing, maybe you can do it there too?
David Jennaway 14,065 on at

Like (0)

Report

RE: Only User with Administrator Role able to run Report

This sounds like a problem with your setup. The reporting services log files should give you more information on the issue. Does the issue apply for SQL-based reports, or Fetch-based reports, or both ?