Can't run report when connected to report server

Question

0.00/5 (No votes)

See more:

Hi all, I've created a report using Report Builder 3 which runs fine until I connect to the reporting server ( SSRS ) I've gone to the servers home page in IE clicked on Folder Options and added myself as a user with all the checkboxes selected but to no avail - any ideas what can be wrong ? - the error I get is, "the permissions granted to pjk(which is me ) are insufficient for performing the current operation", if I then disconnect from the server the report runs fine

What I have tried:

I've gone to the servers home page in IE clicked on Folder Options and added myself as a user with all the checkboxes selected

Posted 29-May-16 3:26am

pkfox

Add a Solution

Comments

Homero Rivera 29-May-16 21:01pm

I've seen that, in order to check a report in SSRS, your user needs to be registered in SQL Server and granted permission.

This is, not just SSRS permission, but also SQL Server permission to read the target tables.

Why not try that approach?

pkfox 30-May-16 1:11am

Hi and thanks for your reply, if it was SQL server permissions problem why does the report run OK when I'm not connected to the report server ?

pkfox 30-May-16 7:19am

Just to update - if I run report builder as administrator I can connect to the report server and run the report without issue - but I notice if I browse to the report server using Firefox and try to create a shared data source I get the same error about permissions for pjk

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)