Forum Discussion
Dataflows always fail to refresh due to "internal error"
Hi Davolsen,
I've just looked into the logs base on the request Id you provided us. We saw the same problem from other customers and engineering team is working on a fix. We will update you as soon as the fix will be in place.
Thanks,
Galia
Microsoft EmployeeHi Davolsen,
I've just looked into the logs base on the request Id you provided us. We saw the same problem from other customers and engineering team is working on a fix. We will update you as soon as the fix will be in place.
Thanks,
Galia
Is there an update to this issue? I'm seeing the same error.
Hi AdamWidi,
The problem related to MFA issues. We are still working on a fix.
There might be a workaround, please asked the owner of the dataflow to re-login to PBI. After the re-login try to refresh the dataflow again.
Thanks
Batchen
Thank you for the quick response!
I logged out and back into Power BI, and tried refreshing the dataflow again. The spinner spun for longer this time, but I eventually got the same error. Note, I was able to successfully refresh a PowerBI dataset using the same gateway connection. It's the dataflow that is failing.
Thanks, Adam
I just tested my data flows and they are now refreshing.
Looks like the issue is fixed for the moment!
Unfortunately I'm still experiencing this issue.
I suggest you post separately with a Request ID and Activity ID. There might be a different cause for your problem, and you don't want my problem mixed up with yours.
I am getting the same error on dataflows. The data was working and then it started failing to refresh. I tried deleting the table and re-adding it, as well as logging on and off.
This is the error I am getting when I download the excel file:
Error: Internal error Request ID: bc8283d5-d44d-406e-f803-e3e94f06b986 Activity ID: 2672c6b9-184a-45c7-aaf6-4ad7be05693c
Hi verballi.
The root cause of your problem is not the same as this thread problem. I am investigating your problem, will update once I will have more information.
Batchen
dotanMarcusHi verballi2,
We are aware and a fix should be available by the end of week.
If you wish to overcome it immediately you can rename your entities so they include only letters, numbers and spaces (no special characters) and also verify they don't start with a number.
Thanks
Dotan Marcus
Hi there, I am getting the same issue. Is there a fix for it yet?
Cluster URI: WABI-SOUTH-CENTRAL-US-redirect.analysis.windows.net
Activity ID: 90587c35-4f7f-46c3-b6fb-d1d75f179b90
Request ID: 81f222fa-2260-3f65-8a6e-7f86bfa1893a
Time: 2019-06-14 14:59:20ZThanks!
Karina
UstinovdlHelper I
Nope. There is no fix for this issue. I continue to use old datasets with my personal gateway. It's disaster!
- marclelijveld
Resolver I
It seems to be that you're refering to a different case than mine was. For me the issues are all fixed and where related to a temporary bug with the entity and dataflow names. All fixed as mentioned by Batchen_Haviv in earlier posts.
So, if it is not the same, you probably can better open a new topic.
Regards,
Marc
I now seem to have the same error
Error: Internal error
Request ID: ceb6af97-8ebb-49e9-8f21-0293be46a68d
Activity ID: f3bc5d3d-1db0-4734-83e3-14f712133676
HELP!!!
korpek wrote:Hi there, I am getting the same issue. Is there a fix for it yet?
Cluster URI: WABI-SOUTH-CENTRAL-US-redirect.analysis.windows.net
Activity ID: 90587c35-4f7f-46c3-b6fb-d1d75f179b90
Request ID: 81f222fa-2260-3f65-8a6e-7f86bfa1893a
Time: 2019-06-14 14:59:20ZThanks!
Karina
Hi there,
I am also having problems refreshing my dataflows. Please find the error I'm getting below.
Error: Request ID: b475c7bd-c55e-236b-b3c3-6fc611836641 Activity ID: d8521c30-a0af-4c6c-930c-ac26f6d18793
Galia Pramod2699 BI-Geniuz
