- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
104203 Couldn't refresh the entity because of an internal error
My Dataflowgen2 is failing with below error message. This error messages is coming from past 3 days only. All the scheduled flows are failing. Please give suggestions
error messaage: 104203 Couldn't refresh the entity because of an internal error
gateway version installed in my machine: 3000.190.17
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @dinesh01
Just wanted to check whether you have gone throught the above mentioned document for additional information. If not I request you to kindly go through the document once.
As the document says, when using Microsoft Fabric Dataflow Gen2 with an on-premises data gateway, you might encounter issues with the dataflow refresh process. The underlying problem occurs when the gateway is unable to connect to the dataflow staging Lakehouse in order to read the data before copying it to the desired data destination. This issue can occur regardless of the type of data destination being used.
If the issue still persists. I request you to open up a support ticket as it requires a deeper investigation from our engineering team about your workspace and the logic behind it to properly understand what might be happening.
Please go ahead and raise a support ticket to reach our support team: support-ticket
Please provide the ticket number here as we can keep an eye on it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @dinesh01
Thanks for using Microsoft Fabric Community.
Apologies for the issue that you are facing here.
I see that you are using older version of gateway on your machine. Try to upgrade the gateway version to the latest, this might help you in resolving the error issue. If the issue still persist please do let us know. Glad to help.
Please refer to the document for the latest version of gateway. Please refer to this documentation for additional information.
I hope this information helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @dinesh01
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tonight we are upgrading gateway. I will let you know the results. When I am splitting the dataflows into 2 pieces it is working (source -> stagelakehouse with staging enabled) and ( stagelakehouse -> destination lakehouse without staging enabled ) but this is quiet tiedy process as I have more than hundred tables to bring into lakehouse.
One more thing is dataflowgen2 is not always failing. Sometimes it fails and sometimes it doesn't.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After upgrading gateway 104203 error message disappeared and new error message is appearing and the dataflow is not always failing. Sometime it fails and sometime it doesn't.
New error message: 104100 Couldn't refresh the entity because of an internal error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @dinesh01
Just wanted to check whether you have gone throught the above mentioned document for additional information. If not I request you to kindly go through the document once.
As the document says, when using Microsoft Fabric Dataflow Gen2 with an on-premises data gateway, you might encounter issues with the dataflow refresh process. The underlying problem occurs when the gateway is unable to connect to the dataflow staging Lakehouse in order to read the data before copying it to the desired data destination. This issue can occur regardless of the type of data destination being used.
If the issue still persists. I request you to open up a support ticket as it requires a deeper investigation from our engineering team about your workspace and the logic behind it to properly understand what might be happening.
Please go ahead and raise a support ticket to reach our support team: support-ticket
Please provide the ticket number here as we can keep an eye on it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @dinesh01
Glad that your query got resolved.
Please continue using Fabric Community for any help regarding your queries.

Helpful resources
Subject | Author | Posted | |
---|---|---|---|
01-22-2024 01:07 PM | |||
02-07-2024 03:14 PM | |||
10-31-2023 03:23 AM | |||
11-10-2023 11:39 AM | |||
02-21-2024 04:56 AM |