Forum Discussion
Dataflow gen2 refresh Error
Thanks for this. This table has incremental refresh baked in which might result in a an empty table. i am not sure how that needs to be handled for lakehouse ingestion.
This part should be internally baked in to incemental refresh -
if Table.IsEmpty(Source) then ... else ...miguel can you please provide some insights on to why df gen2 keeps on faikling for some tables from on prem sql db. I keep on getting this, I am trying to ingest a base table without incremental refresh and it is still failing
- miguel1 year agoCommunity Admin
I'm not sure sure that we can help with the information shared on this thread. Do you have a way for us to repro the behavior or could you go into details as to how we could create something similar in our own environments ? Or perhaps a more detailed definition of your mashup document ?
assuming that you're using the latest version of the gateway, please raise a support ticket so our engineering team can take a closer look at this scenario
- smpa011 year agoCommunity Champion
To reproduce
#1. Ingest a data from on prem sql server to a lakehouse with fixed schema and replace using a df gen2. Do not factor in incremental refresh.
There is no issue in this step.
#2. Go back and factor in incremental refresh in the same df gen2 and run the dataflow. It errors out in this stage with 10855.
#3. If you factor in incremental refresh in #1 before doing a base ingestion, it gets error out with tge same error.
What I desire is to be able to ingest from on prem sql server db to lakehouse with incremental baked in without any error.
- smpa011 year agoCommunity Champion
I keep on getting refresh error 104500, do you know what it is for?
There was a problem refreshing the dataflow: 'Something went wrong, please try again later. If the error persists, please contact support.'. Error code: 104500. (Request ID: f356ef9a-2194-46be-8aa2-72483c85d585). dim_activity_WriteToDataDestination: There was a problem refreshing the dataflow: 'Something went wrong, please try again later. If the error persists, please contact support.'. Error code: 999999. (Request ID: f356ef9a-2194-46be-8aa2-72483c85d585).