SSRS Remote Connection Problem

  • Hi!

    I have described problem in different parts as following:

    Local Machine = End user Computer

    Remote Machine-A:

    1. It has Cube-A.

    2. Reporting services are also installed on this machine.

    3. DataSources for Cube-A and Cube-B also resides on this computer.

    4. Two reports called Rep1 and Rep2 which are also resides on this machine and connected to Cube-A and Cube-B

    5. And offcourse Report Manager is also working on Machine-A.

    Remote Machine-B = It has only Cube-B

    Problem:

    End user accesses the http://Remote Machine-A/Reports/Rep1. It works perfectly fine.

    But when end user accesses the http://Remote Machine-A/Reports/Rep2. It does not work. The following error is rendered on the explorer:

    Cannot create a connection to data source 'Cube-B'. (rsErrorOpeningConnection)

    A connection cannot be made. Ensure that the server is running.

    Unable to read data from the transport connection:

    An existing connection was forcibly closed by the remote host.

    Network Architecture

    All computers exist under the same domain, MyDomain.

    MyDomain->LocalMachine,

    MyDomain->Remote Machine-A

    MyDomain->Remote Machine-B

    What does I have in my head:

    It may be a double-hop problem. I tried quite many ways buy changing in Report Manager but no positive results. After reading few articles I came up with an idé to create a new PowerUser on the Domain which will communicate between Remote Machine-A and Remote Machine-B. But I am affriad if it will work or not?

    Help Required

    If someone has any solution, to overcome the problem, it will be appriciated.

    Thanks

    /Nave

  • Can Remote Machine-A see Remote Machine-B (i.e. ping Remote Machine-B from Remote Machine-A and does it return the correct ip address for Remote Machine-B)? You could also use something like Wireshark to view what is going on in the network when you make the request for Rep2.

  • You can verify if it is a kerberos issue by connecting to ServerA via rdp or using it's console. If you are able to run the report from a browser on ServerA, you have the double-hop issue.

    To resolve this, you should enable and use kerberos delegation and configure the correct SPN's. This type of configuration is becoming increasingly common and learning how to set it up is important.

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

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