Post reply

Reporting Services Permission Problem - I Think

  • July 27, 2009 at 2:45 pm

    #212821

    Hello All

    I've setup Reporting Services on a SQL 2005 environment. The issue that I'm having is I have a few users that recieve the following message when they try to view a report (http://server/Reports):

    An error has occurred during report processing.

    Cannot create a connection to data source '{5C6358F2-4BB6-4a1b-A16E-8D96795D8602}'.

    For more information about this error navigate to the report server on the local server machine, or enable remote errors

    I added the Domain Users group to the Browser Role (Properties > New Role Assignment > added the "Domain\Domain Users" group of the domain the user logs onto and selected the Browser role).

    The user has no problem seeing the reports. The error occurs when the user selects a report to generate the report details.

    Has anybody seen this type of error before? Are there other areas where I need to grant that group permissions before they can see report details?

    Thanks in advance for your help!

    Ronnie

  • July 28, 2009 at 9:06 am

    #1031089

    What type of authentication is your data source using? If you are using Window Authentication then you need to make sure the users have access to the database.

    Jack Corbett
    Consultant - Straight Path Solutions
    Check out these links on how to get faster and more accurate answers:
    Forum Etiquette: How to post data/code on a forum to get the best help
    Need an Answer? Actually, No ... You Need a Question

  • July 28, 2009 at 10:07 pm

    #1031451

    I suspect that the report is not associated with a data source (any more). Perhaps the report RDL was updated but the data source reference was not correct.

    Try going to the report properties and updating the data source(s) used by the report.

  • July 28, 2009 at 10:12 pm

    #1031454

    I suspect that the report is not associated with a data source (any more). Perhaps the report RDL was updated but the data source reference was not correct.

    Try going to the report properties and updating the data source(s) used by the report.

  • August 3, 2009 at 11:02 am

    #1033793

    Thanks Guys!!

    This is what I ended up doing:

    • Created a login account on the database side

    • Granted the login the Public role

    • Mapped it back to the database (data source) being used

    • Set the Data Source Authentication under Reporting Services in the

    SMS tool to use the login account credentials

    SMS has a internal feature that uses SQL Reporting Services. Within SMS, you can configure various aspects of SSRS.

    I'm not sure if that was totally correct, but worked for allowing the user to access reports. But it also prevented us from administering SSRS as well. So, it's not totally right, but the users are happy.

    Thanks again for all your suggestions.

    Ronnie

  • August 7, 2009 at 12:58 am

    #1035802

    not sure if this could be of any help . (i know it s already fixed )

    Programs-Sqlserver2005-Configuration Tools- SqlServ Config Manager-SqlServer network Configuration-Protocols for MSSQLSERVER-TCP/IP -Enable

    Programs-Sqlserver2005-Configuration Tools- Surface Area configuration-Surface area configuration for Services and connections-MSSQLSERVER-Database engine-Remote connections-Enable Local and remote connections

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply