Post reply

SSRS - Cannot Create Connection

  • October 1, 2013 at 8:53 am

    #283342

    Hi There,

    I am new to SSRS and have basically created a bunch of reports (sysadmin) through visual studio, deployed them and setup the necessary rights, permissions and roles needed per folder on the localhost URL. Now the fun part, the domain user can access the URL get to the required folder but when trying to execute the report the following error is thrown out.

    An error has occurred during report processing. (rsProcessingAborted)

    Cannot create a connection to data source 'RI_TEST_TEXTILES'. (rsErrorOpeningConnection)

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

    I logged in using the domain users credentials that is not part of system admin and i can execute the reports successfully but as soon as the users try they get the above error.

    I have been at this now for two days but with no luck, i have literally tried everything.

    Thanks

    Max

  • October 1, 2013 at 10:55 am

    #1654984

    Hi Max,

    How is your connection defined? SQL authentication or Intergrated authentication?

    How do you test it? On the same server or from a laptop for example? Sinc eyou mentioned a domain account, my guess it is Integrated Authentication

    Please note that if you report server is on a different server from a data source database where (hopefully) all your user domain accounts have been given access to the database, and you test from the report server (the second comouter in the chain) but your users test from their laptops 9the third computers in the chain) , then the delegation errors may happen.

    One of my developers has had it recently in another context.

    Please google on how to eneble security accound delegation or if you are notuing Windows authentication in data source, let us know more how your data source connects.

    Yelena

    Regards,Yelena Varsha

  • October 1, 2013 at 11:07 am

    #1654988

    Hi

    Thanks for the reply

    The report server and database reside on the same server. And we using integrated authentication just checked.

    My test method is to run the report connected to the guest which is a public network in a sense so from outside the network.Then enter the url and the users credentials and go to a folder where the user has access click on a report and it works. Then I logout and the user logins again from his work station which is on the network then he gets the error.

    And yes all the other users are across Europe but do have accounts on our domains.

  • October 1, 2013 at 11:21 am

    #1654993

    Check a few things;

    - If your SQL Server is set up to audit failed logins, check SQL Server logs what was the error message. If not, run profiler to capture Audit -login, logout and login failed events

    - Can you use that person's computer, login as yourself and see if the report works from his computer and you as a user. it can happen that this person will need to add you as a user to his computer.

    - Check if this person is added as a user of the report in SSRS. You have to add the users to appropriate SSRS roles and / or report permissions

    - Stupid thing: sometimes we have to add a person to the permissions on the root folder HOME is SSRS, permissions to the actual report folder and reports is not sufficient.

    - Another stupid thing: check public role permissions and Guest user permissions. Your Windows users may come as a role that does not have permissions to the database but your Guest account have been give permissions. Check both.

    Regards,Yelena Varsha

Viewing 4 posts - 1 through 3 (of 3 total)

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