We are running a PowerShell script using this cmdlet on a Windows 2012R2 server on PowerShell Desktop v5.1 and Core v.7.0.2 and consistently getting the following errors.
v.5.1System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> 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
v.7.0.2{System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
We tried using this workaround in this post but no luck. Also, checked the machine TLS settings via IISCrypto and in the registry. This appears to recently start happening and after the June Windows update.
We are running a PowerShell script using this cmdlet on a Windows 2012R2 server on PowerShell Desktop v5.1 and Core v.7.0.2 and consistently getting the following errors.
v.5.1
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> 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
v.7.0.2
{System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
We tried using this workaround in this post but no luck. Also, checked the machine TLS settings via IISCrypto and in the registry. This appears to recently start happening and after the June Windows update.
Any assistance is appreciated.