On-prem Gateway issue

[smpa01]

I am trying to utilize DFGen2 to query a sql table accessible via on-prem Gateway and publish the result to a LakeHouse Table.

I am running into following errors.

I can use a dataflow in power bi using same gateway without having any issues whatsoever.

How can I resolve this?

[v-cboorla-msft]

Hi @smpa01 

Thanks for using Microsoft Fabric Community.

Apologies for the issue that you are facing.

As I understand that you are trying to utilize DFGen2 to query a sql table accessible via on-prem Gateway and publish the result to a LakeHouse Table.

The below procedure might help you to resolve your ask.

In order to connect from on-prem SQL server to Fabric, you need to install an on-premises gateway. Please find the related documentation - Install and configure an on-premises data gateway 

For server connection from on-prem SQL server to Microsoft Fabric please refer :

On Premise SQL Server 2022 Data into Microsoft Fabric

Getting On-Premises SQL Server Data to Fabric Lakehouse 

I hope this information is helpful. If problem still persists please do let us know.

[smpa01]

@v-cboorla-msft  on-prem gateway is already installed as I am using the same gateway to create dataflow in Power BI ( as opposed to DFG2 in Data Engineering ) without any issue and able to refresh and consume the same dataflow downstream.

[v-cboorla-msft]

Hi @smpa01 

Could you please confirm the present version of your on-Premises gateway? If you are running on the older version try to upgrade to the latest version, this might help me you in resolving the error.

For details please refer Link.

I hope this helps. If you have any further queries please do let us know.

[v-cboorla-msft]

Hi @smpa01 

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]

Hi @smpa01 

Could you please confirm couple of things.

Have you opened up the required 1433 ports for the data gateway?

Did you map the connection to a single gateway? You can't use multiple gateways in a single solution.

For more details on 1433 port please refer Link. 

Thanks.

[v-cboorla-msft]

Hi @smpa01 

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]

Hi @smpa01 

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

[Element115]

The same error message appears for me as well, and yes, we updated the gateway to the latest version and all that.  

I do have a follow-up question though.  I ignore the message and proceed with the dataflow ingestion process.  The data does make into the lakehouse.

HOWEVER!  Why are all column names lost?!?!?  Inside dataflow, the column names appear exactly as they are in the source on-prem DB, but after publishing the dataflow, poof!  they are gone and replaced by generic names such as : Column 1, Column 2 etc...

Why? Oh why??!!  And what is the fix? Is there even a fix?????