microsoft / microsoft/powerbi-powershell

Connect-PowerBIServiceAccount PowerShell cmdlet throwing SSL/TLS error

Open
#238 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
413
Forks
134
Avg merge
33m
Merged PRs (30d)
1

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing Connect-PowerBIServiceAccount on Windows Server 2012 R2 with PowerShell 5.1 and 7.0.2, comparing the reported TLS errors and the June Windows update context. The issue names no files or tests; done would be a confirmed cause and a documented, reproducible resolution or clear evidence that the problem is external.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.