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

Power BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.

Reply
Ynr225
Helper II
Helper II

Semantic model refresh failed with adotimeout

Hello All, 

 

I have created a report using Oracle database in power bi desktop in import mode and I refreshed the report in desktop with in 10 minutes refresh is completed. Later i published the report in Power BI service and i did manual but the report is failig to refresh.

 

Ynr225_0-1742568733800.png

 

Can anyone please help on this.

 

1 ACCEPTED SOLUTION

Hi @Ynr225,

As you are experiencing this issue frequently, please submit a support ticket with Microsoft.So that one of the engineers can assist you further, ensuring a thorough investigation and a timely resolution of the Gateway Timeout Error.

Below is the link to raise the support ticket:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

 

Thank you.

View solution in original post

10 REPLIES 10
v-saisrao-msft
Community Support
Community Support

Hi @Ynr225,

Could you please confirm if the issue was resolved after raising a support case? If so, we’d appreciate it if you could share the solution to help others in the community. As we haven’t heard back, we’re closing this thread. For any further issues, please raise a new thread in the Microsoft Fabric Community Forum — we’ll be happy to assist.

Thank you for being part of the Microsoft Fabric Community.

Ynr225
Helper II
Helper II

Thanks for responding @Deku, here the thing is we are getting the above error if user uses import mode where as direct query mode connected report is refreshing in both desktop and service. Don't know why it is happening for import mode.

Deku
Community Champion
Community Champion

Other similar posts suggest increaseing the timeout period in the connector settings

Deku_0-1742631654335.png

 

 


Did I answer your question?
Please help by clicking the thumbs up button and mark my post as a solution!

Hello @Deku ,

 

Even I tried the above method in Power BI desktop but no use, still receiving the same error in service.

Hi @Ynr225,
Thank you for reaching out to the Microsoft Fabric community forum. Also, thanks @Deku for your valuable insights.

Since you have already increased the timeout in Power BI Desktop but are still encountering the issue in Power BI Service, here are a few options you can consider:

  • Limit the dataset size by applying filters in Power Query. Consider splitting the dataset into smaller chunks. If possible, switch to Direct Query mode instead of Import Mode.
  • Rather than importing all data at once, use Incremental Refresh to load only new data.


If this information is helpful, please “Accept it as a solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.


Thank you.

Thanks for responding @v-saisrao-msft ,

 

While connecting oracle database in Power BI desktop,
I used query in Adanced editor to filter the data. Even i splitted the dataset into smaller chunks but getting same error.

Note: When i run query in SQL developer it is taking just 9 seconds to complete the query
Coming to second point I don't have date column to make use of incremental refresh.

 

Don't know the reason why its faiing in service? 

Hi @Ynr225,

Thank you for the follow-up and for sharing the details! Since your query runs in 9 seconds in SQL Developer but still fails in Power BI Service with the "adotimeout" error — even after filtering and splitting the data the issue is likely due to the Service’s handling of the refresh, not the query itself.

First, check Refresh History (Settings > Datasets) to see if the detailed error indicates a timeout, memory, or gateway issue. If you’re using an On-premises Data Gateway for Oracle, ensure it’s updated to the latest version and increase the Connection Timeout under Gateway Cluster Settings.

Next, verify query folding right-click each step in Power Query and select "View Native Query". If the SQL query isn’t shown, folding has broken, which can cause Power BI to pull more data than needed. To resolve this, move as many transformations as possible directly into the SQL query in Advanced Editor.

If none of this works, sharing the exact error details from Refresh History would help narrow things down further.

 

If this information is helpful, please “Accept it as a solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.


Thank you.

Hello @v-saisrao-msft,

 

Here is the full error message screenshot you are looking for

Ynr225_0-1742816744221.png

Yes I am using on-premises data gateway february 2025 version

Hi @Ynr225,

As you are experiencing this issue frequently, please submit a support ticket with Microsoft.So that one of the engineers can assist you further, ensuring a thorough investigation and a timely resolution of the Gateway Timeout Error.

Below is the link to raise the support ticket:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

 

Thank you.

Deku
Community Champion
Community Champion

Sounds like networking between service and oracle. Make sure appropriate IP addresses are whitelisted


Did I answer your question?
Please help by clicking the thumbs up button and mark my post as a solution!

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.