Forum Discussion
DFGen2 Unable to create Destination table in Lakehouse
Hi,
trying to create a Destination table in a Lakehouse while using DFGen2 to import data. But I am unable to create tables, both when using Data Destination - Choose destination target dialog, or when running the DFGen2 dataflow. Source is onprem SQL Server using gateway. I've tried one table is single column allowing Null, the other table with 3 columns Not Null. Please see attached error screenshots.
20 Replies
- pqian_MSFT
Microsoft Employee
It seems like your gateway is rejecting the TLS connection to the lakehouse server (while having line of sight). Check the following things:
- You have TLS 1.2+ enabled on the GW
- You can validate server certificate chains (I've seen cases where the GW has no access to certain certificate authorities and thus cannot validate the chain)
- MarcusANew Member
Using TSL 1.2
- Element115
Memorable Member
Out of curiosity, (1) is this the first time you try to do this? Or (2) has it worked before and then suddenly it won't work?
- MarcusANew Member
1: First time trying this out
- Element115
Memorable Member
MarcusA btw, and I should have mentioned this before, since you are trying to extract from an on-prem DB, have you tried the 2 dataflow chained workaround? Here, Microsoft briefly explains:
This workaround solved the 'Something went wrong' error in the data destination dialog for me, as well as the other errors that would pop up at refresh time (after you publish).
- Element115
Memorable Member
MarcusA Regarding connectivity issues between DF and on-prem DB, here is a new post in which I explain the resolution of my misadventure in this regard: DATAFLOW and ON-PREM DB connectivity solution - Microsoft Fabric Community
The long and short of it, what solved it was to ignore what is stated in the documentation here: On-premises data gateway considerations for data destinations in Dataflow Gen2 - Microsoft Fabric | Microsoft Learn
After removing the endpoints from the firewall rules and replacing these rules with only one rule for the MS-SQL Server service, opening port TCP/1433, everyting started to work as it should.
- v-cboorla-msft
Microsoft Employee
Hi MarcusA
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.- v-cboorla-msft
Microsoft Employee
Hi MarcusA
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.
If you have any question relating to the current thread, please do let us know and we will try out best to help you.
In case if you have any other question on a different issue, we request you to open a new thread.
Thanks.