Solved

SSRS - Users can't run reports

Posted on 2013-06-10
1
806 Views
Last Modified: 2013-06-10
I have set up SSRS. I have written the sp's and SQL functions to build the reports and they run just fine.

However, I'm logging into Windows as an administrator. The standard users cannot run the reports. Initially they couldn't even log into the reports home. I set up the permissions so that the Domain Users group could get access to reports. This didn't fully work until I actually allowed the Domain Users group to access the main folder in SSRS. Now they can see all the reports. All users on the domain are part of the Domain Users group. When they run them they get an error.

"An error has occurred during report processing. (rsProcessingAborted)
    Cannot create a connection to data source "DataSource1". (rsErrorOpeningConnection)
        For more information about this error navigate to the report server on the local server machine or enable remote errors"


Firstly, where do I enable remote errors? I've been through the reports server configuration and there is nothing I can find that enables remote errors. The server itself has no IIS instance running on it.

If I go into each report and check the security settings on it, it is inheriting from the parent folder. The security settings on the site are:

Domain Users - Site User

Under the folder settings:

Domain User: Browser which says the users "May view folders, reports and subscribe to reports"

Each report has security settings which inherit from the folder so what am I missing?

All I want is that anyone that can log onto the URL and is part of the Domain Users group in Windows, I would like them to be able to run the reports. It's really quite simple.

If you need more info, please ask.
0
Comment
Question by:Lee Savidge
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 25

Accepted Solution

by:
Lee Savidge earned 0 total points
ID: 39235270
I fixed this stupid problem myself in the end.

Instead of using Windows Authentication I set up the datasource to use SQL Authentication with a SQL user. All datasources now use this logon and the problem has gone away.
0

Featured Post

Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article I will describe the Copy Database Wizard method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question