Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
Arez2017
Helper I
Helper I

Kerberos with Report Server

Hello Community, 

I have created 3 servers on wich I have installed : PowerBI Report Server, SSAS and SQL Server. 

I have configured Kerberos. 

However, it is not working  

We couldn't run the report because we couldn't connect to its data source. The report or data source might not be configured correctly.
Please try again later or contact support. If you contact support, please provide these details. 

We couldn't connect to the Analysis Services server. The server forcibly closed the connection. To connect as the user viewing the report, your organization must have configured Kerberos constrained delegation. 

Request ID9115842d-13ca-19f4-da04-93a824f9e0b8 

TimeWed Feb 21 2018 17:12:06 GMT+0100 (Romance Standard Time) 

Version14.0.600.442 

 

in log files : 

2018-02-21 17:12:06.1462|ERROR|10|PBI.Win.ReportingServicesHostTrace|type:Error;message:processing:Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'EntityDataSource'. ---> 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 

at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) 

at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) 

--- End of inner exception stack trace --- 

at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) 

at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count) 

at Microsoft.AnalysisServices.AdomdClient.DimeRecord.ForceRead(Stream stream, Byte[] buffer, Int32 length) 

at Microsoft.AnalysisServices.AdomdClient.DimeRecord.ReadHeader() 

at Microsoft.AnalysisServices.AdomdClient.DimeReader.ReadRecord() 

at Microsoft.AnalysisServices.AdomdClient.TcpStream.GetResponseDataType() 

--- End of inner exception stack trace --- 

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.EndRequest(Boolean useBinaryXml) 

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.SendMessage(Boolean endReceivalIfException, Boolean readSession, Boolean readNamespaceCompatibility) 

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.SupportsProperty(String propName) 

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession) 

at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Connect(Boolean toIXMLA) 

at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP) 

at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open() 

at Microsoft.ReportingServices.DataExtensions.AdomdExceptionHandler.Execute(String connectionString, Action action) 

at Microsoft.ReportingServices.Diagnostics.DataExtensionConnectionBase.<>c__DisplayClass6_0.<OpenConnection>b__0() 

--- End of inner exception stack trace ---;;| RequestID = 9115842d-13ca-19f4-da04-93a824f9e0b8 ClientSessionID = 3a233905-497b-a82c-314a-77608064f6ae  

2018-02-21 17:12:06.1618|ERROR|10|PBI.Win.ProcessingError|ExceptionType:Microsoft.ReportingServices.ReportProcessing.ReportProcessingException;stackTrace: at Microsoft.ReportingServices.Diagnostics.DataExtensionConnectionBase.<>c__DisplayClass6_0.<OpenConnection>b__0() 

at Microsoft.ReportingServices.Diagnostics.Utilities.DefaultActivitiesFactory.CreateSyncActivityAndReportResult(RSActivityType activityType, Action action) 

at Microsoft.ReportingServices.Diagnostics.DataExtensionConnectionBase.<>c__DisplayClass5_0.<OpenDataSourceExtensionConnection>b__0() 

at Microsoft.ReportingServices.Diagnostics.DataExtensionConnectionBase.HandleImpersonation(IProcessingDataSource dataSource, DataSourceInfo dataSourceInfo, String datasetName, IDbConnection connection, Action afterImpersonationAction) 

at Microsoft.ReportingServices.Diagnostics.DataExtensionConnectionBase.OpenDataSourceExtensionConnection(IProcessingDataSource dataSourceObj, String connectString, DataSourceInfo dataSourceInfo, String datasetName) 

at Microsoft.PowerBI.ReportingServicesHost.LocalDataExtensionConnectionWrapper..ctor(DataSourceInfo dataSourceInfo, CreateDataExtensionInstance createExtensionCallback, UserContext threadUser, ExecutionType execType, IAdditionalToken additionalToken, IDbConnectionPool connectionPool, IDataProtection dataProtection) 

at Microsoft.PowerBI.ReportingServicesHost.LocalDataExtensionConnectionWrapper.<>c__DisplayClass7_0.<Open>b__0() 

at Microsoft.PowerBI.ReportServer.ExploreHost.WindowsUserIdentityConnectionImpersonator.ExecuteInContext[T](Func`1 func) 

at Microsoft.PowerBI.ReportingServicesHost.LocalReportProcessingHost.GetModelMetadata(DataSourceInfo dataSourceInfo, IDbConnectionPool connectionPool, String modelMetadataVersion, IConnectionUserImpersonator connectionUserImpersonator, ITelemetryService telemetryService) 

at Microsoft.PowerBI.ReportingServicesHost.DataShapingHelper.GetModelMetadata(IPowerViewEngine powerViewEngine, IDbConnectionPool connectionPool, DataSourceInfo dataSourceInfo, IASConnectionInfo asConnectionInfo, Boolean useMsolapForCsdl, IConnectionUserImpersonator connectionUserImpersonator, ITelemetryService telemetryService, String maxModelMetadataVersion);message:GetModelAsStream;| RequestID = 9115842d-13ca-19f4-da04-93a824f9e0b8 ClientSessionID = 3a233905-497b-a82c-314a-77608064f6ae  

2018-02-21 17:12:06.1774|ERROR|4|Failure in conceptualschema| RequestID = 9115842d-13ca-19f4-da04-93a824f9e0b8 ClientSessionID = 3a233905-497b-a82c-314a-77608064f6ae Microsoft.PowerBI.ReportServer.ExploreHost.Error.RSExploreHostException: Cannot create a connection to data source 'EntityDataSource'. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'EntityDataSource'. ---> 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 

at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) 

at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) 

--- End of inner exception stack trace --- 

at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) 

at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count) 

at Microsoft.AnalysisServices.AdomdClient.DimeRecord.ForceRead(Stream stream, Byte[] buffer, Int32 length) 

at Microsoft.AnalysisServices.AdomdClient.DimeRecord.ReadHeader() 

at Microsoft.AnalysisServices.AdomdClient.DimeReader.ReadRecord() 

at Microsoft.AnalysisServices.AdomdClient.TcpStream.GetResponseDataType() 

--- End of inner exception stack trace --- 

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.EndRequest(Boolean useBinaryXml) 

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.SendMessage(Boolean endReceivalIfException, Boolean readSession, Boolean readNamespaceCompatibility) 

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.SupportsProperty(String propName) 

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession) 

at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Connect(Boolean toIXMLA) 

at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP) 

at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open() 

at Microsoft.ReportingServices.DataExtensions.AdomdExceptionHandler.Execute(String connectionString, Action action) 

at Microsoft.ReportingServices.Diagnostics.DataExtensionConnectionBase.<>c__DisplayClass6_0.<OpenConnection>b__0() 

Any idea please? 

Regards, 

5 REPLIES 5
dhawal16
Advocate I
Advocate I

Did anybody able to resolve this issue, we are having the same issue on our environment. We are using Aug-18 release and our keberos and SPNs are set following the documentation by Guy In a Cube. Our report is with import so no question of connecting to SSAS but still getting the same error.

 

Thanks,

Dhawal

pbx
Helper V
Helper V

These errors seem more of a network connectivity problem than Kerberos. Could you please confirm connectivity first?

I have the same error, but mine only happens when I set the authentication type to windows authentication as the user viewing the report and I use a PROD domain user to access the TEST domain Power BI Report Server, I believe it's a double hop issue.

 

Otherwise if I test with the TEST domain user, this same report works fine, I managed to configure SPN delegation following the instructions given here: https://docs.microsoft.com/en-us/power-bi/report-server/configure-kerberos-powerbi-reports

 

Trust between my domain is configured, my PROD domain user can access the PBIRS and view reports that have a forced credetial on the datasource as well as access the SSAS cube, both these servers are on the TEST domain.

 

If anyone has any idea for my double hop issue, I'm open for suggestions 🙂

 

Thanks in advance.

 

Mego

Anonymous
Not applicable
Anonymous
Not applicable

Hi

 

Don't know if it will help but there is a "Guy In A Cube" video on Youtube about exactly this problem, might be worth a view.

 

Rob

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors