topic Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse in Dataflow

Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

FredrikJ — Fri, 09 Jun 2023 02:58:44 GMT

Hi!

I have set up a gen2datflow from an oracle database via gateway (version number 3000.178.3) and everything looks fine in the dataflow I can my data. Destinations of the dataflow is to a lake house and it works fine to publish the Dataflow but when refreshing the Dataflow it fails with no error message

Regards

Fredrik

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

Anonymous — Fri, 26 May 2023 12:48:41 GMT

What error message are you getting? If you click on the Table Name (DART) is should give you the error message.

I'm having siliar issues. I'm getting this error;

Error Details: Error: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: We don't support creating directories in Azure Storage unless they are empty. Details: #table({"Content", "Name", "Extension", "Date accessed", "Date modified", "Date created", "Attributes", "Folder Path"}, {}) GatewayObjectId: b4a8b741-aef4-482e-9d30-19d6dea19022. Request ID: 78757b74-d18e-c8c3-6e24-7c16331d838d. (Request ID: 2dfa424a-69ea-41c2-a61a-82484f43eee7).

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

FredrikJ — Fri, 26 May 2023 13:28:26 GMT

Yes, I see now I get the same errormessage:

Error Details: Error: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: We don't support creating directories in Azure Storage unless they are empty. Details: #table({"Content", "Name", "Extension", "Date accessed", "Date modified", "Date created", "Attributes", "Folder Path"}, {}) GatewayObjectId: 89d69b05-cbca-4382-b000-c8c76058d4ed. Request ID: a0a20bcc-958f-09b6-c6bd-bdfab9bf796f. (Request ID: 4a0c7012-c9ec-417a-8029-e2281b52a919).

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

miguel — Fri, 26 May 2023 16:18:07 GMT

Hi FredrikJ Anonymous ,

Would you mind updating to the latest version of the gateway and try again? Let us know if you're still any errors after updating the gateway

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

FredrikJ — Fri, 26 May 2023 16:21:57 GMT

Hi miguel !

I updated the gateway today to version number 3000.178.3. And still got the same problem.

Regards

Fredrik

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

Anonymous — Fri, 26 May 2023 16:28:11 GMT

I have the latest version installed.

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

miguel — Fri, 26 May 2023 16:54:03 GMT

FredrikJ Anonymous Thank you for confirming this! please go ahead and raise a support ticket so an engineer can look deeper into it

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

suidino2 — Sat, 27 May 2023 04:25:30 GMT

Same error here.

Dataflow pulling from on-premise SQL-server by using enterprise gateway (updated to latest version)

Dataflow destination setup to lakehouse. Dataflow itself setup successfully, but when tried to refresh the dataflow, it appears the same error message.

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

miguel — Sat, 27 May 2023 04:29:10 GMT

Hi all!

The product team has been notified of the issue which is in relationship to the Gateway. They're working hard on pushing out a new version of the gateway that will have the fix for it.

Thank you for your patience!

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

RRPowerBiAdmin — Sat, 27 May 2023 21:58:39 GMT

Similar problem with DF Gen 2 with Lake house target. Simple one column hand entered table. For testing. DF runs fine. Target won't keep saved credentials despite being entered repeatedly and seeing the destination in the saving and publishing steps...

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

miguel — Sat, 27 May 2023 22:39:43 GMT

Hey!

As mentioned in the other thread, the problem that you're mentioning seems to be unrelated to the gateway related issue. I'd highly recommend reaching out to the support team to go deeper into this issue and possibly find a solution.

if there's no gateway involved in your dataflow, then the problem will be someplace else in our stack.

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

FilipVDR — Tue, 30 May 2023 07:45:50 GMT

Seems i got a similar error: even when I create a new dataflow and enter data with one column and one row, and I want to write it to the lakehouse i get an error:

It seems that the dataflow can't save my connection using my Organizational Account

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

Anonymous — Tue, 30 May 2023 10:53:43 GMT

Hello,

I have exactly the same error than you after I have updated the Gateway.

Did you find any solution yet ?

Thanks,

David

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

SidJay — Wed, 31 May 2023 05:44:54 GMT

The most recent version of the Gateway (version 3000.174.12 uploaded on May 30th) addresses the "We don't support creating directories in Azure Storage unless they are empty" error.

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

SidJay — Wed, 31 May 2023 05:46:37 GMT

The most recent version of the Gateway (version 3000.174.12 uploaded on May 30th) addresses the "We don't support creating directories in Azure Storage unless they are empty" error.

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

FredrikJ — Wed, 31 May 2023 06:28:34 GMT

SidJay I uploaded the Gateway on May 26th and got a higher version (3000.178.3) then you talking about. Is it possible for us to install a version with lower version number then we already got? And how can i be possible for us to have a higer version when we uploaded our version before u did?

Regards

Fredrik

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

SidJay — Wed, 31 May 2023 06:36:15 GMT

Hi Frederik,

I'm unfortunately not sure how you could have gotten into that state. The most prudent course of action would be to uninstall the prior installation, and then install version 3000.174.12.

Re: Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse

Anonymous — Wed, 31 May 2023 07:28:27 GMT

Hi,

It works ! Thanks a lot for the quick fix