- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Problem running a gen2 dataflow from a non azure sql server via a gateway to a Lakehouse
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the latest version installed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @miguel !
I updated the gateway today to version number 3000.178.3. And still got the same problem.
Regards
Fredrik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have exactly the same error than you after I have updated the Gateway.
Did you find any solution yet ?
Thanks,
David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
It works ! Thanks a lot for the quick fix
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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).
Helpful resources
Join us at the Microsoft Fabric Community Conference
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Microsoft Fabric Community Conference 2025
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
Subject | Author | Posted | |
---|---|---|---|
Anonymous
| 09-16-2024 09:27 AM | ||
09-06-2024 11:59 AM | |||
02-07-2024 07:50 AM | |||
12-07-2023 03:24 AM | |||
03-11-2024 12:20 AM |
User | Count |
---|---|
3 | |
2 | |
2 | |
1 | |
1 |