How to debug Report Server connections
Hi All,
Server1 : Analysis Server with cube.
Server2 : Report Server, Report builder.
Server3 : SQLServer db with reportServerDB
On Server2 using report builder I am able to connect to server1 (with cube), create a report and run it without deploying it on the server3. It pulls the data as expected.
After deploying it on Server2 (report server) I tried to run it and it failed with following error: -------------------------------
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'Server1'. (rsErrorOpeningConnection)
For more information about this error navigate to the report server on the local server machine, or enable remote errors
In report server (Server2) error log I see following: -----------------------------------------------------------------
processing!ReportServer_0-1!dc0!11/11/2010-11:26:02::
e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: ,
Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing.
---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'Server1'.
---> Microsoft.AnalysisServices.AdomdClient.AdomdConnectionException: The connection either timed out or was lost.
---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
I had timeout 60 seconds, I raised it to 240 and still same error.
I don't know what to do next.
Please help.
-DP.
November 11th, 2010 11:40am
Could be kerberos not being setup to relay authentication from the client between the servers.My Blog "Karl Beran's BI Mumble"
Free Windows Admin Tool Kit Click here and download it now
November 11th, 2010 11:54am
Hi,
It is double hop issue. Just as proposed by Karl, enable kerberos to solve it fully, see
http://msdn.microsoft.com/en-us/library/aa378747(VS.85).aspx for more details about Microsoft Kerberos. Or to get it around, you can log on report manager and switch to Report datasource
page, use "Credentials stored securely in the report server".
thanks,
Jerry
November 14th, 2010 10:26pm