Forum Discussion
SQL On-Prem with Enterprise Gateway refresh issue
Hello,
I resolved my original issue. I added a new IBM DB2 table to my dataset, so after publishing and since I didn't have a related source configured in my on-prem data gateway, it would not allow me to schedule a refresh. Once I added the IBM DB2 data source to the on-prem data gateway, I was able to schedule my refresh again.
As far as some of the other issues some of you have reported, we recently experienced some refresh failures that were due to firewall firmware updates, because of the continued need for stronger security. Our security team had to make a firewall change to fix the refresh issue.
Thanks,
The service health page no longer has any information about scheduled data refresh failures. My reports are still failing even though the data gateway is healthy, and I'm not finding anything that stands out in the log files. I'm seeing really generic errors in the service that look like this with 15+ scheduled data refreshes:
| Failed Connections: | Query - Get Award Exceptions |
| Cluster URI: | WABI-US-NORTH-CENTRAL-redirect.analysis.windows.net |
| Activity ID: | e8c3cc55-01e2-4f85-647a-60d8643ac60f |
| Request ID: | a79a6fd5-f59b-61d1-2a16-2bd8c6f098a1 |
| Time: | 2018-05-14 14:25:15Z |
I went as far as reinstalling the data gateway (I only have one machine with the enterprise gateway installed) and republishing several of my reports. The on-demand refreshes would typically complete a refresh successfully the first time, but now they are right back to failing with the generic errors as posted above. This is becoming a very big problem for us as this is now day 4 of all our scheduled processes being down.
Is there a known issue with the service? Any other suggestions for correcting the failed refreshes?
I am experiencing the same issue - I also tried reinstalling the gateway with no success. Will continue to check in on that support page.
Hello,
I resolved my original issue. I added a new IBM DB2 table to my dataset, so after publishing and since I didn't have a related source configured in my on-prem data gateway, it would not allow me to schedule a refresh. Once I added the IBM DB2 data source to the on-prem data gateway, I was able to schedule my refresh again.
As far as some of the other issues some of you have reported, we recently experienced some refresh failures that were due to firewall firmware updates, because of the continued need for stronger security. Our security team had to make a firewall change to fix the refresh issue.
Thanks,
Both Schedule and on demand refreshes for Excel Workbooks are failings since saturday 05/12/2018
Is anyone facing these issues?
Although Power BI refreshes are working fine and the gateway does not log any message either.
Below is the message which I am getting, it is not at all descriptive.
Scheduled 5/14/2018, 9:31:06 AM 5/14/2018, 9:34:21 AM Failed Workbook refresh failed. See details for more information.
Failed Connections: XXXX
Cluster URI: WABI-US-EAST2-redirect.analysis.windows.net
Activity ID: 89899023-b67d-480b-a29c-de10c2e1aacc
Request ID: 518edd66-263a-48dc-802b-6978dc3b0a11
Time: 2018-05-14 13:34:21ZYes, that is exactly the same problem that I'm having. I should have been more clear in my original reply to the first post on this thread. I'm seeing the same generic refresh errors with Excel Workbook refreshes (both on-demand and scheduled). They had been running and refreshing successfully up until Friday morning. I also do not see anything on the BI Service Health page that would suggest this is a known issue or something Microsoft is currently working on.
Both Schedule and on demand refreshes for Excel Workbooks are failings since saturday 05/12/2018
Is anyone facing these issues?
Although Power BI refreshes are working fine and the gateway does not log any message either.Below is the message which I am getting, it is not at all descriptive.
Scheduled 5/14/2018, 9:31:06 AM 5/14/2018, 9:34:21 AM Failed Workbook refresh failed. See details for more information.
Failed Connections: XXXX
Cluster URI: WABI-US-EAST2-redirect.analysis.windows.net
Activity ID: 89899023-b67d-480b-a29c-de10c2e1aacc
