Double Hop Issue in SSRS

-

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

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

An error has occurred during report processing. (rsProcessingAborted)

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

Login failed for user ‘domain\\username’. The user is not associated with a trusted SQL Server connection.

OR

Double Hop Issue



What’s a Double Hop Issue?

To explain it in simple terms, when your SQL Reports make a call to the IIS Server (SQL Reports run on IIS) using the Authentication set for the Reports and then IIS attempts to make a call to SQL Server running on a different machine, using the same Authentication, it gets Authentication error with SQL Server. This is a case of a Double Hop, as it tries to hop around the credentials across different machines.

So in my case, I had set Windows Integrated Security Authentication for my Reports and it worked fine as long as my Report Server and the SQL Server which had my Reports data were on the same machine. But if the SQL Database Server was on a different machine than the SQL Reports Server, the Reports had authentication failure due to Double Hop Issue and threw above errors.

Step 1:

                Create a New User or use an existing User who has required rights on the Reports Database (the database from where you Report will pull the data)

Step 2:

                Access your Report Manager Web UI on the Report Server.  You can do that by going to the following URL on your Report Server

                http://servername/Reports
Step 3:

                Navigate to the Data Source that is used by your Reports.

Step 4: 

Click on the Data Source and then click on the General Tab in the left panel if it is not already selected.

Step 5:

                Select the Credentials stored securely in the report server option and enter the credentials

Step 6:

                Make sure the Use as Windows credentials when connecting to the data source option is checked.

Step 7:

                Click on Apply

Comments

Post a Comment

Hi User,
Thanks for visiting My Blog and please provide your valuable feedback and subscribe for more updates. Please don't post any spam content or comments.
Thank You

Popular Posts

Failed to execute the package or element. Build errors were encountered

-
Error: TITLE: Microsoft Visual Studio ------------------------------ Failed to execute the package or element.   Build errors were encountered. For more information, see the Output window. ------------------------------ BUTTONS: OK ------------------------------   Solution: We tried to close SSDT and run it again but, we still got the same error while running SSIS package. Then, we need to follow bellow solution: Step 1: Go to Task Manager–> Details Tab. Step 2: Locate the process “ DtsDebugHost.exe “. Kill this process. There might be multiple instances of this process. Kill all of them. Step 3: Rerun SSIS package
Read more

Exception deserializing the package "The process cannot access the file because it is being used by another process."

-
TITLE: Microsoft Visual Studio ------------------------------ Failed to start project ------------------------------ ADDITIONAL INFORMATION: Exception deserializing the package "The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process.". (Microsoft.DataTransformationServices.VsIntegration) ------------------------------ The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process. (mscorlib) ------------------------------ BUTTONS: OK ------------------------------ While running SSIS package i got the error “The process cannot access the file ‘*.ispac’ because it is being used by another process”. I tried to close SSDT and run it again but, I still got the same error while compiling. Then, after searching over internet, I got
Read more

Temporary enable and disable SSRS subscriptions

-
--Code Snippet --To Check Subscription Status. USE ReportServer GO SELECT dbo . Subscriptions . Description ,        dbo . [Catalog] . Name ,        dbo . Users . UserName ,        InactiveFlags FROM dbo . Subscriptions      INNER JOIN dbo . [Catalog]      ON dbo . Subscriptions . Report_OID = dbo . [Catalog] . ItemID      INNER JOIN dbo . Users      ON dbo . Subscriptions . OwnerID = dbo . Users . UserID --Temporary disables subscriptions while data warehouse is unavailable UPDATE dbo . Subscriptions SET InactiveFlags = 1 GO --After this you can find, all the subscription where disabled until you again enable it. --Again enable subscriptions. UPDATE dbo . Subscriptions SET InactiveFlags = 0 GO
Read more