Forum Discussion

smpa01's avatar
smpa01
Community Champion
2 years ago

On-prem Gateway issue

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.           ...
data engineering
v-cboorla-msft's avatar
v-cboorla-msft
Microsoft Employee
2 years ago

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's avatar
v-cboorla-msft
Microsoft Employee
2 years ago

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's avatar
    Element115
    Memorable Member
    2 years ago

    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?????