Sharepoint Authentication failed because the remote party has closed the transport stream

[tivo]

Hi,

since last week we are suddenly facing issues when trying to load data from Excel files in a Sharepoint folder using Data Flows. The error message we get is the following:

Authentication failed because the remote party has closed the transport stream.

I read that this issue often occurs when TLS is not set to version 1.2, but within the connection of Power BI to Sharepoint (which I would assume is handled by Microsoft) I don't see a way to change the TLS version.

Any ideas how to solve this? We are using this feature in quite a few reports so the impact is quite huge. 

Thanks in advance.

Kind regards,

Tim

[Anonymous]

Hi  @tivo ,

Based on the error message you provided, it seems like there may be an issue with the TLS version being used in the connection between Power BI and SharePoint. However, as you mentioned, it may not be possible to change the TLS version within the connection settings. One possible solution could be to try using a different authentication method for the connection. For example, if you are currently using Windows authentication, you could try using OAuth authentication instead. This may help to resolve the issue with the TLS version.

Best regards.
Community Support Team_Caitlyn

[tivo]

Hi @Anonymous,

thanks for your reply.

It seems like part of the reason for our error was just that we were accessing different sources within the same dataflow. The others were connecting to a database via a gateway connection. Apparently if a gateway connection is used it will automatically be used for all sources in the dataflow and this cannot be changed. You don't happen to know some workaround for this case?

Still though, we were trying to access some sharepoint files within single dataflows which resulted in the same error. This seems to have been a temporary issue only, because now we are able to use those sources again. 

Thanks again and best regards,

Tim

[Anonymous]

Glad to hear you've got some temporary mitigation of the problem, as far as I know there's no other workaround at the moment.

I'll give some feedback if I get a follow up on the investigation results.

Best Regards,
Community Support Team _ Caitlyn