Scheduled Refresh Returns "Timeout occurred when sending or receiving a request", Manual Works

[Anonymous]

We have the On-premsis data gateway version 14.16.6792.1 (August 2018):

We've deployed a report using imported data from SSAS to the Power BI service.  It is setup to use the gateway, and the data source is setup in the service:

One of the two scheduled refreshes fails almost daily, sometimes it's the 5am, others it's the 6am.  It's always "Timeout occurred when sending or receiving a request."  However, a manual refresh or the next scheduled refresh will succeed just fine.  It doesn't happen every day.

We have many reports using the same SSAS cubes, and none have this same issue.  It's just this one report.  I've exported the logs from the gateway server but I'm not sure what to look for.

[v-qiuyu-msft]

Hi @Anonymous,

You can find the related log based on RequestID in log files to find if there is any detail information. As you mentioned the manually refresh is working, once the schedule refresh is failed, if you refresh the dataset manually at once, does the same issue occur? 

Best Regards,
Qiuyun Yu 

[Anonymous]

Thank you, Qiuyun.  When the scheduled refresh fails, the manual refresh works.  Of the 5am and 6am scheduled refreshes, if the 5am refresh fails, the 6am will usually succeed.  If the 6am fails, we'll do a manual refresh which will succeed.

I have verified that the cubes are done processing by 3:30am.

I'll check the logs by the RequestID, thank you for the tip!

[Anonymous]

@v-qiuyu-msft I went through the logs this morning, found that the Timeout occurred when sending or receiving a request error that occurred on Friday & Sunday were similar.

For the failure that occurred at 5am on Friday:

There's only one entry in any of the logs for RequestID 58d6f33e-870a-48bd-b2eb-37b30f4efb8f or for ActivityID 97311d5d-23d6-4321-90a2-3bf47b67eef6. 

It's in Gateway20180914.000000001.log:

Line 15146: DM.EnterpriseGateway Information: 0 : 2018-09-14T10:01:14.7060507Z DM.EnterpriseGateway 71179910-de86-4e96-aa5d-6b392e43d4d9 58d6f33e-870a-48bd-b2eb-37b30f4efb8f MGPP 97311d5d-23d6-4321-90a2-3bf47b67eef6 A08BF3B6 [DM.GatewayCore] Deserialized TestGatewayConnectionRequest, executing

For the failure that occurred at 5am on Sunday:

There's only one entry in any of the logs for RequestID 6c0feecd-4467-4de9-9379-5a67cf0e5323 or for ActivityID c566f66a-f964-46af-ae80-791fcd98f6f0. 

It's in Gateway20180916.000000001.log:

Line 13436: DM.EnterpriseGateway Information: 0 : 2018-09-16T10:01:11.5205711Z DM.EnterpriseGateway a71951d1-80ba-45b0-abd2-ee8d9ba0e0eb 6c0feecd-4467-4de9-9379-5a67cf0e5323 MGPP c566f66a-f964-46af-ae80-791fcd98f6f0 A08BF3B6 [DM.GatewayCore] Deserialized TestGatewayConnectionRequest, executing

This morning, neither refresh failed:

[Anonymous]

This issue is still occurring with this specific report.  Has anyone run into this before?

[RadiantToxicBot]

I'm experiencing the same issues ([DM.GatewayCore] Deserialized TestGatewayConnectionRequest, executing).

These never occurred before October and I'm wondering if it's because we are stuck on version 14.16.6780.1 (Aug 2018). We're unable to update the gateway due to installer issues LINK

[Anonymous]

One year later and I am having issues with  [DM.GatewayCore] Deserialized TestGatewayConnectionRequest, executing daily against SQL Servers.

Did you find something out?