OLE DB or ODBC error: [DataSource.Error] Unable to read data from the transport connection: An exist

[abhishekrws01]

Hello,

Looking for some help, please.

I get the below error when importing the data through the M query. I Googled the issue, and many workarounds were suggested, but none of them worked for me. When I open the Excel data source, I don't see any issue in the data. Does anyone has any idea what is driving it, please? 

Here is what I have tried already (based on suggestions from different people on different forum) 

1. Clear permissions from data source settings

2. Clear caches

3. Reduce parallel loading of Tables from 8 to 2

4. Uncheck 'Internet information services' from  "Control panel"  -> "Programs and features" -> "Turn windows features on or off" -

Thank you

[v-hashadapu]

Hi @abhishekrws01 , Please let us know if your issue is solved. If it is, consider marking the answer that helped 'Accept as Solution', so others with similar queries can find it easily. If not, please share the details.
Thank you.

[v-hashadapu]

Hi @abhishekrws01 , Please let us know if your issue is solved. If it is, consider marking the answer that helped 'Accept as Solution', so others with similar queries can find it easily. If not, please share the details.
Thank you.

[v-hashadapu]

Hi @abhishekrws01 , Please let us know if your issue is solved. If it is, consider marking the answer that helped 'Accept as Solution', so others with similar queries can find it easily. If not, please share the details.
Thank you.

[Greg_Deckler]

@abhishekrws01 So are you using the Excel connector to connect to the Excel data or ?? Make absolutely certain that the Excel file is not open.

[abhishekrws01]

Hi -

No, I am fetching data through API. API works perfectly on Postman, and it worked in Power BI last month.

Thanks

[v-hashadapu · Accepted solution]

Hi @abhishekrws01 , Thank you for reaching out to the Microsoft Community Forum.

Since it works in Postman and used to work in Power BI, this points to a change in how the connection is being handled either on your end or the API’s. It's likely the API now enforces stricter security protocols like TLS 1.2. Power BI might be defaulting to an older version, which gets rejected.

To fix that, make sure your system is set to use TLS 1.2 by adding the SchUseStrongCrypto registry key, this tells Power BI’s underlying .NET framework to use stronger encryption. Also, make sure your API call in Power BI is structured correctly. A solid Web.Contents setup, with headers, timeout, and status handling avoids silent failures. Postman might be more forgiving, but APIs often expect specific headers and timeout behavior. Double-check your authentication. If you’re using an access token, make sure it hasn’t expired, Power BI might be holding onto a stale one. Re-authenticating from the data source settings can refresh this. It’s also worth checking if the API has changed, maybe they’ve added rate limits, tightened TLS rules, or started filtering by IP. Postman could still work if it uses a different IP or fresh token.

Lastly, if you’re using Power BI Service with a gateway, make sure it’s up to date and able to connect over HTTPS. Also try running the same query in a clean Power BI file, if that works, something in the original file might be cached or corrupted.

Also, Please refer to the below documentation:

Install an on-premises data gateway

Overview of TLS termination and end to end TLS with Application Gateway

Web.Contents

Transport Layer Security (TLS) best practices with .NET Framework

If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.