Forum Discussion

Element115's avatar
Element115
Memorable Member
2 years ago
Solved

BUG::Data destination can't be set. Vague error msg produced.

In a new data flow, when I try to set the data destination to an existing lakehouse as a new table, this error message shows up.  I tried later again and again, and now it's been 4+ hours this is goi...
Dataflows
  • v-cboorla-msft's avatar
    v-cboorla-msft
    2 years ago

    Hi Element115 

     

    Thanks for using Microsoft Fabric Community.

    Apologies for the inconvenience.

    I tried to repro the scenario and didn't find any difficulty in choosing the data destination as Lakehouse. For reference please find the screenshot.

     

    If you are using an on-premises as data source with Dataflow Gateway might cause connectivity problems. The firewall might be blocking communication between the gateway and the destination (lakehouse or warehouse).

    For more details please refer : Solution: Set new firewall rules on server running the gateway

     

    In case the issue still persists, please do let us know. Glad to help.

    I hope this information helps.

     

    Thanks.

v-cboorla-msft's avatar
v-cboorla-msft
Microsoft Employee
2 years ago

Hi Element115 

 

Thanks for using Microsoft Fabric Community.

Apologies for the inconvenience.

I tried to repro the scenario and didn't find any difficulty in choosing the data destination as Lakehouse. For reference please find the screenshot.

 

If you are using an on-premises as data source with Dataflow Gateway might cause connectivity problems. The firewall might be blocking communication between the gateway and the destination (lakehouse or warehouse).

For more details please refer : Solution: Set new firewall rules on server running the gateway

 

In case the issue still persists, please do let us know. Glad to help.

I hope this information helps.

 

Thanks.

Element115's avatar
Element115
Memorable Member
2 years ago

Goddamn!   I clicked the 'Accept as solution' by mistake.'

 

Just wanted to add to my previous reply:

 

Been a while now I had our sysadmin update the firewall rules and multiple DFs had no issue ingesting from the on-prem DB until last Friday.   Although last Friday, I asked the sysadmin to add this to the FW rules, as per the MS documentation, as this endpoint is new and wasn't mentioned a couple of weeks ago:  *.dfs.fabric.microsoft.com  , and it went downhill from there.

 

Also, should have said this was another test of DF at the behest of the SE, case #2401190040000098.  

 

I notified the SE of the failure of the test he asked me to perform, so I guess, no need to open a new support ticket.  This is what he asked me to do:

 

 

 

We got an update from Product team.
We suspect the issue could be related to missing configuration in the Gateway to allow reaching to the Lakehouse storage.

Please try out the following steps and provide the outcome of two refreshes:
1. Create a new dataflow A with a simple query (blank table) that is using the Lakehouse storage as output destination and then try to refresh the dataflow.
2. Create a new Dataflow B with an entity that uses a data source that utilizes the GW and configure the Lakehouse as the output destination and then refresh the Dataflow.