OLE DB or ODBC error: [DataSource.Error] An error happened while reading data from the provider:

[Anonymous]

Hi Team,

I'm getting bellow shown error while fetching one table from Power Query Editor to Power BI Desktop.

OLE DB or ODBC error: [DataSource.Error] An error happened while reading data from the provider: 'Invalid operation. The connection is closed.'.

I could see no error in that particular table in power query editor but when I'm fetching it to desktop this popup is coming after few minutes of loading.

@amitchandak  @Greg_Deckler  @lbendlin @Jihwan_Kim  @Ahmedx @Padycosmos @Arul @DataInsights @ppm1 @Sahir_Maharaj @MFelix @AllisonKennedy 

 

[Poojara_D12]

Hi @robinhood276 

You're encountering an error where Power Query loads the table fine in the editor, but when you actually apply and load it into Power BI Desktop, it fails with: "Invalid operation. The connection is closed." This usually means the data source connection is timing out or dropping during the final data load phase, even though preview works. Often, this happens with large tables, slow network/data gateway connections, or providers that close idle sessions. In short, the issue isn't with your query logic but with the connection not staying open long enough when loading to the model.

[robinhood276]

Thanks @Poojara_D12 , how do I overcome this? The internet connection is stable. How do I check which is the source of the issue?

[AllisonKennedy]

@robinhood276 are you able to filter the data first? Do  you need to pull through all the data? Please let us know if you've solved this!

[robinhood276]

HI I'm facing the same issue. Do you have a solution to this? I'm using sql server database as the data source. Gateway has been updated. No merging tables in Power Queries. Data loads for a few minutes and gives the error above.

@AllisonKennedy 

@GilbertQ 

@ibarrau 

[AllisonKennedy]

@Anonymous  Power Query Editor only loads a preview of the data, so errors sometimes don't appear until you 'close and apply'. What's your data source? If you're still experiencing an issue have you tried raising a support ticket?