Before the data import for (Data Source Name) finished, its data source timed out.

[Anonymous]

Scheduled Reports are taking error "Before the data import for (Data Source Name) finished, its data source timed out."  Most reports have 60 min. timeout coded and error occurs after a couple minutes.  Start of last week, a couple reports showed error.  By Fend of week about half the scheduled reports took the error.  Administrator restarted/rebooted Enterprise Gateway.  Reports immediately ran fine.  This week, a similar pattern emerged.  Some reports fail at start of week and by Friday, high percentage of reports failed with this error message.  Data sources are accessing SQL Server & Oracle databases.  We know the restart of the Gateway is the quick fix, but seems like there is a bigger issue.

[Anonymous]

@v-qiuyu-msft 

Hi, I got the same issue with my Customer report (about 16m data rows).

I can refresh it by using schedule refresh. It always show me the error (after took from me 2 waiting-hours) like below:

Yesterday I already updated the On-premises gateway to the lastest version.

Hope to get your response soon. Thanks in advance!

[Anonymous]

If it is due to a MS issue chances are good it would show up here:  https://powerbi.microsoft.com/en-us/support/

What is the timeout parameter set at for the import data source?  Set it high to see if it would finish.

Do you need all columns in the 16M rows of data?  Only pull in the columns needed.  Or select half 16M rows, did it run?  Select a quarter of the data, did it run?

Pulling the 16M from a database?  Aggregate the data on the database server in the SQL.

Is the Gateway server struggling?  Memory issue?  Network throttling? Competition for resources?  With MS only allowing refreshes to be every 30 min, there is a rush for resources from other reports.

Try using aggregation tables:  

https://radacad.com/power-bi-aggregation-step-1-create-the-aggregated-table

Still unable to refresh?  If SQL Server, build a tablular model cube using SSAS and use direct query. 

[JuanPa]

Hi everyone

We have the same issue just from the last 2 days.  This only happens with 3 of our 10 datasets, these ones are the biggest in quantity of tables which comes from excel files, text files and sql server tables.

This error is produced after we manually refresh them or after a schedulled refresh.

We have increased the power of our Gateway server to 8 cores and 12 Gb RAM but this error still open.

Any other idea?

Thanks

[sebnemd]

Hi, we repeatedly got this error message today during each run of schedule.

We also checked the gateway and it was working fine. But we restarted it anyway.

This happens from time to time and we do not know the root cause or the ideal solution. Gateway reset cannot be it, each time. Any suggestions? Thanks!