error: The underlying connection was closed: An unexpected error occurred on a send

Francesco Giorgio 11

I am experiencing the following error, when doing translations:
The underlying connection was closed: An unexpected error occurred on a send

This has happened suddenly without any change by my side of the script configuration.

I also can read in Resource Integrity: Not possible to determine the status of integrity of the resource Cognitive Services at the moment.

I am wondering if this relates to a known Microsoft Azure issue or if I should do any fix on my side.

Thank you

Dan Granger 6 Reputation points

2021-04-19T15:28:23.84+00:00

We're getting the same issue on calls to an O365 Sharepoint site.
GiftA-MSFT 11,151 Reputation points

2021-04-19T18:21:14.097+00:00

Hi, thanks for reaching out. Are you using a global, regional, or multi-service resource to authenticate? If using a regional resource, can you please share the region?
Prasath, Siva 1 Reputation point

2021-09-22T14:50:28.517+00:00

I I have tried adding the below ones but still I'm getting the same error. I have tried adding at the beginning / Just the line before ExecuteQuery() but no luck. I'm invoking the SharePoint Online using the ClientContext. I'm using .NET framework 4.7.2. Let me know if I'm missing something?

System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;

System.Net.ServicePointManager.SecurityProtocol |= System.Net.SecurityProtocolType.Tls12;

3 answers

Stephen 11 Reputation points

2021-04-19T20:28:03.687+00:00
After MS support pointed us in the direction of TLS, adding the following line fixed the error for us:

System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;

Still don't understand why after years of working fine today was the day it needed to be changed.

Edit: While the above definitely fixed the error, the line we ended up using was:
System.Net.ServicePointManager.SecurityProtocol |= System.Net.SecurityProtocolType.Tls12;
Please sign in to rate this answer.

2 people found this answer helpful.
Francesco Giorgio 11 Reputation points

2021-04-19T20:23:27.957+00:00

The resource to authenticate is Global.

The error happens when calling the following API:
https://api.cognitive.microsofttranslator.com/translate?api-version=3.0&from=it&to=DE&to=EN&to=FR&to=ES&to=NL

and precisely when calling this method: System.Net.HttpWebRequest.GetResponse()

“Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host”

Stack Trace: in System.Net.HttpWebRequest.GetResponse()

Inner exception:
in System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
in System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)

Error code: 10054
SocketErrorCode: ConnectionReset {10054} System.Net.Sockets.SocketError

Francesco Giorgio 11 Reputation points

2021-04-20T05:53:34.67+00:00

Thank you Stephen, I had to adapt this fix to .net framework, but it worked also!
Thank you very much for sharing.

I agree I can't believe they suddenly have deprecated previous TLS versions, without any warning...

Keith Lubell 1 Reputation point

2021-05-20T17:41:31.193+00:00

Same problem. Same solution. Thanks!

thomas 6 Reputation points

2021-06-09T13:03:51.84+00:00

hey stephen.
i think i am missing a small piece of the puzzle :) so if this is a stupid question bear with me
where did you add this line.
in the application or in the api call.

Stephen 11 Reputation points

2021-06-09T15:08:24.68+00:00

Since this was a production hotfix for us, we added the line right before creating the request object that was failing.

If this was something we had time to fix, we would've applied it at application/service start up instead.

Ian Micir 1 Reputation point

2021-08-26T14:28:06.55+00:00

Same problem. Same solution. Thank you!!

ananpeculiar 181 Reputation points

2022-11-05T13:47:24.307+00:00

I have SharePoint on-prem Windows Server 2019, I am getting the Error on the Search Service Application, and this stops the SP Full Backup. does this applicable For SP On-prem, and kindly help me with the file name where to add this line.

DG001 346 Reputation points Microsoft Employee

2023-07-28T22:41:55.09+00:00

I have a customer that is experiencing this error. Where do you add this line too?

Joe F Matthew 0 Reputation points

2024-03-22T20:36:58.7333333+00:00

Was the TLS value already set to 1.2 in the Registry on the machine this code ran?
Sign in to comment
Anindya Chakraborty (IN) 6 Reputation points

2022-06-06T10:50:04.74+00:00

Facing this issue to connect from PBI ? anyone can help me
Please sign in to rate this answer.

1 person found this answer helpful.
Siva Prasath 1 Reputation point

2022-06-06T12:58:00.393+00:00

Anindya,

After lots of back and forth, I was not able to fix it. Finally what fixed for us is, When we deployed to Windows 2016 R2, it started working. If in case, you are deploying on old windows version try it in latest windows server.

LV_Skopea 6 Reputation points

2022-12-19T13:38:45.317+00:00

Hi !

Did you find a way to solve this ? I have the same problem in Power BI and Power Query in Excel, I can't connect to any data source that requires an authentification to my professional account, I get the error "The underlying connection was closed". It also occurs when I try to update datas in my older files that used to work perfectly ...
Sign in to comment
Jeffery Decker 6 Reputation points

2022-12-27T20:31:46.627+00:00

I, too, am having this problem via PBI service through SharePoint online. Any updates?
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment