Power BI Paginated Reports Datasource Timeout Error

[Anonymous]

We have 30 Power BI Paginated reports that retrieve data from an On Premise SQL server database through an on premise data gateway. The reports use SQL stored procedures to access the data they require.

Each report is set up with a subscription to email the report in Excel, on a daily basis. The reports run once a day with their times spread over about 1 hour 15 mins. This menas we have up to 7 reports running at the same time.

Each day we get 1 (sometimes 2) reports erroring  with the below error :

DataSource_Timeout

Data for this report could not be fetched in the allocated time. If you continue to experience this error contact the report author or data source owner to increase the time-out.

All the paginated reports have the dataset timeout values set to 1200 seconds. 

We recieve the error, in an email, 1 or 2 minutes after the report is scheduled to run. 

The report that fails seems to be a different report each day.

Can anyone help please

Thanks

[Anonymous]

Hi,

Can you please give more infomation on what you mean when you say 'Visability Properties'. 

Thanks

[Igna]

Hi,

You can hide items in your report using expressions. That way you can manage what is displayed.

https://learn.microsoft.com/en-us/sql/reporting-services/report-builder/hide-an-item-report-builder-...

Igna

[Igna]

Hello, 

You are mentioning that 7 reports are running at the same time. Do they have the same sources (tables) ? If yes, it could cause some lock on the tables concerned. You should try to put different schedules to your subscriptions.

Hope it helps.

Igna

[Anonymous]

Hi Igna,

Thanks for the reply.

The reports do access the same data tables but they are only reading the data (no updates or inserts) so would you still expect contention issues to occur? 

Also if we have a different schedule for each report, they will need to run from 8am to about 10:30 which isn't ideal.  

Thanks

Paul

[Igna]

Hi,

Each transaction create a lock on ressources. Even if it is just reading.

There is no way to create a unique dataset and to create only on report ? Using visibility properties or that kind of stuff ?

Igna

[Anonymous]

Hi Igna,

I have some further info on this issue. Sometimes the issue occurs even when we are running just 1 paginated report in a subscription. 

I have also noticed that the Request id that we are given in the error email does not appear in any of the On Premise Data Gateway logs. 

Does this extra information help at all? 

Thanks in advance.