Forum Discussion
Scheduled refresh fail
Hi,
The scheduled refresh gives below error message. I find it too general to troubleshoot. Anyone got same issue before and was able to solve? Thanks!
Last refresh failed: Tue Jan 09 2018 16:05:55 GMT+0100 (Romance Standard Time)
Cancellation occurred when sending or receiving a request.Hide details
| Cluster URI: | WABI-NORTH-EUROPE-redirect.analysis.windows.net |
| Activity ID: | 361789e9-57df-47e0-9646-6eafbad15e7c |
| Request ID: | c1a7711e-0fe2-49dc-aabe-051810c6bd8c |
| Time: | 2018-01-09 15:05:55Z |
Our scheduled refresh seemed to fix itself on 1/12. Successful daily schedule refreshes completed 1/12, 1/13, 1/4, 1/15, and 1/16. Any ideas on the root cause?
10 Replies
Hi timclaeys,
Can you please provide more detail informations to help us clarify your issue? (e.g. datasource type, connect mode, using proxy? screenshots...etc)
Regards,
Xiaoxin Sheng
Hi Anonymous,
I'm using an on-premises data gateway (personal mode), and data source types are several .xlsx files and 1 SQL server (data source credentials are all ok, no errors).
Anonymous,
Where those .xlsx's file are located, Is it in your local or share point.Those files are should be share point with no down time, if those files are in your local Scheduled refresh will not work.
Regards,
Bajee.
I also have this error occurring.
My last successful Gateway Refresh was 1/10 at 6 AM. After this time, using scheduled refresh or the on-demand refresh from PBIS is giving the error of "Cancellation occurred when sending or receiving a request.".
I also tried a test using another data model and I have the same error occurring.
Any help is appreciated. I believe I can work around by downloading the .pbix, doing a refresh in PBID, then publish back to PBIS. I have not tried that yet.
Our scheduled refresh seemed to fix itself on 1/12. Successful completion daily 1/12, 1/13, 1/14, 1/15, and 1/16. Any ideas on the root cause?
Our scheduled refresh seemed to fix itself on 1/12. Successful daily schedule refreshes completed 1/12, 1/13, 1/4, 1/15, and 1/16. Any ideas on the root cause?
Hi kdyess1,
>>Our scheduled refresh seemed to fix itself on 1/12. Successful daily schedule refreshes completed 1/12, 1/13, 1/4, 1/15, and 1/16. Any ideas on the root cause?
I think this may related to recently service feature release.(power bi team seems finished resolve compatibility issues with new features)
Regards,
Xiaoxin Sheng
HI timclaeys,
You provide a common error message, can you share more detail info to help us clarify this issue?
For e.g. gateway local logs, operation trace log...
Troubleshooting the on-premises data gateway
Collecting logs from the gateway configurator
There are several logs you can collect for the gateway, and you should always start with the logs. The simplest way to collect logs after installing the gateway is through the user interface. In the On-premises data gateway user interface, select Diagnostics and then select the Export logslink near the bottom of the page, as shown in the following image.
Installer logs
%localappdata%\Temp\On-premises_data_gateway_*.logConfiguration logs
%localappdata%\Microsoft\On-premises Data Gateway\GatewayConfigurator*.logOn-premises data gateway service logs
C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises Data Gateway\Gateway*.logEvent Logs
The On-premises data gateway service event logs are present under Application and Services Logs.
Fiddler Trace
Fiddler is a free tool from Telerik that monitors HTTP traffic. You can see the back and forth with the Power BI service from the client machine. This may show errors and other related information.
Regards,
Xiaoxin Sheng
