Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Error: OLE DB or ODBC error: pbipeus23-eastus2

Hello All, 

 

I am having the following error in many of my reports, I am using a composite model and most of my data is in the service, but for some reason my visuals keep crashing and the only way to fix them is by clicking the refresh Data, it happens again and again if I keep adding more data into my visuals,  I have seen some errors are related to OLE DB or ODBC when wrong Datatypes are present but I have checked all my Datatypes and seems to be in order also this error just randomly started. 

Any suggestions how can I fix this error ?  is delaying my PowerBi development since I have to refresh data constantly.
Thanks Power BI error.png

 

Status: Investigating

Hi  @Ameth ,

 

Please Go to File > Options and Settings > Options. Under Data Load, click Clear cache and then save the file and reload it.
You may aslo make sure you are using the latest version of Power BI Desktop. Go to File > About and check for updates.

 

Best regards.
Community Support Team_Caitlyn

Comments
v-xiaoyan-msft
Community Support
Status changed to: Investigating

Hi  @Ameth ,

 

Please Go to File > Options and Settings > Options. Under Data Load, click Clear cache and then save the file and reload it.
You may aslo make sure you are using the latest version of Power BI Desktop. Go to File > About and check for updates.

 

Best regards.
Community Support Team_Caitlyn

Ameth
Regular Visitor

Hi @v-xiaoyan-msft,

 

I have tried that as well and still does not works for me.

Thank you.

Ameth
Regular Visitor

[Solution]
Hi,


The error that has been solved, I had network connectivity issues, a network security software was creating a restriction when fetching the data from the cloud, the software was reconfigured and the error has been solved.

Thanks.