PBI Error: The client and server cannot communicate, because they do not possess a common algorithm

[rohithkothaneth]

Hello,

I'm encountering the below error when accessing the web portal reports witin the Power BI Report server.  I have August 2018 release of PBI Report server installed and it was working fine until begining of last week and starting this week noticing this error.

An error has occurred.

Something went wrong. Please try again later.

Upon checking the log files, these are the details associated with this error.

2019-01-03 09:43:18.1920|INFO|12|CONFIG : AccessControlAllowCredentials = [false] (env)
2019-01-03 09:43:18.1920|INFO|12|Received request GET /assets/fonts/PowrMDL2.woff| RequestID = s_f3c01750-fcf5-4089-a00d-64eb6144625d
2019-01-03 09:43:18.1920|ERROR|16|OData exception occurred: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.ComponentModel.Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm
at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc)
at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential)
at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint)
at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output)
at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.ReportingServices.Portal.ODataWebApi.Utils.PbixReportHelper.ShouldReShred(PowerBIReport entity, Uri basePortalUrl, ILogger logger, IPrincipal userPrincipal, String reportServerHostName)
at Microsoft.ReportingServices.Portal.ODataWebApi.Common.CatalogItemControllerHelper`1.GetItem(String key)
at Microsoft.ReportingServices.Portal.ODataWebApi.Common.CatalogItemControllerHelper`1.GetAllowedActions(String Id)
at lambda_method(Closure , Object , Object[] )
at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters)
at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken)

We are using windows server 2016 and SQL Server v17.8.1

Had anyone encounetred similar error and what was the resolution taken to fix it.

Thanks,

Rohith Kothaneth

[ambarishkunte]

Hi Rohit,

On which server did you enable the TLS 1.0,1.1,1.2 ? Was it SQL Server or some other server.

We are also facing a similar issue .  With the creds we are able to connect but getting a below error.

A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The client and server cannot communicate, because they do not possess a common algorithm.)

Regards,

Ambarish Kunte

[rohithkothaneth · Accepted solution]

I was able to fix this issue by enabling TLS 1.0, 1.1 & 1.2 on server an dupon rebooting the server fixed the issue.

Thanks,

Rohith