Could not create SSL/TLS secure channel

adimira — Thu, 06 Jun 2024 14:29:15 GMT

Hi ,

I just upgraded to Power BI Desktop RS to latest version May 2024 and a web data soruce is now failing with

DataMashup.Trace Information: 24579 : {"Start":"2024-06-06T13:46:38.8821650Z","Action":"BackgroundThread/RollingTraceWriter/Flush","ProductVersion":"2.129.255.0 (24.05)","ActivityId":"00000000-0000-0000-0000-000000000000","Process":"Microsoft.Mashup.Container.NetFX45","Pid":12800,"Tid":4,"Duration":"00:00:00.0000800"}
DataMashup.Trace Error: 24579 : {"Start":"2024-06-06T13:46:39.3682101Z","Action":"Engine/IO/Web/Request/RunWithRetry/Failure","ResourceKind":"Web","ResourcePath":"https://test","HostProcessId":"25972","Attempt":"1","MaxAttempt":"3","IsRetryable":"True","ManualStatusHandling":"False","Exception":"Exception:\r\nExceptionType: System.Net.WebException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089\r\nMessage: The request was aborted: Could not create SSL/TLS secure channel.\r\nStackTrace:\n at

System.Net.HttpWebRequest.GetResponse()\r\n at Microsoft.Mashup.Engine1.Library.Http.WrappingHttpWebRequest.<>c__DisplayClass119_0.<WrapResponse>b__0()\r\n at Microsoft.Mashup.Engine1.Library.Http.WrappingHttpWebRequest.WrapExceptionResponse[T](Func`1 getValue)\r\n at Microsoft.Mashup.Engine1.Library.Http.Request.CreateResponse(ResourceCredentialCollection credentials)\r\n at Microsoft.Mashup.Engine1.Library.Http.Request.GetResponseCore(ResourceCredentialCollection credentials)\r\n at Microsoft.Mashup.Engine1.Library.Http.RetryPolicy.Execute[TResult](IEngineHost host, IResource resource, Func`1 func, Tracer tracer)\r\n\r\n\r\n","ProductVersion":"2.129.255.0 (24.05)","ActivityId":"a4fe17f8-9a12-4e97-977a-c7667c3dc536","Process":"Microsoft.Mashup.Container.NetFX45","Pid":12800,"Tid":1,"Duration":"00:00:00.0047320"}

It seems that the new version of Power BI Desktop uses an old TLS version that it's not supported by our network policy.

Where would Power BI Desktop choose what version of TLS to use?

Thanks

Re: Could not create SSL/TLS secure channel

Anonymous — Fri, 07 Jun 2024 05:12:59 GMT

Hi adimira ,

If TLS 1.2 or higher is not enabled, you may need to update your registry settings to enforce the use of these TLS versions. This process is outlined in the Manage SSL/TLS protocols and cipher suites for AD FS | Microsoft Learn

Ensure that your system supports TLS 1.2 or higher. You can do this by checking the registry settings on your Windows machine. For detailed instructions on how to check and enable TLS 1.2:

Transport Layer Security (TLS) registry settings | Microsoft Learn

Best Regards,

Xianda Tang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

topic Could not create SSL/TLS secure channel in Report Server

Could not create SSL/TLS secure channel

Re: Could not create SSL/TLS secure channel