Forum Discussion
Error when trying to create a dataflow gen 2.
Guys...tnx for the answers.
We added the rule to the firewall... same problem.
I don't see anything in our firewall that blocks.
Moreover, i have removed the staging part from the dataflow... the same problem.
Let me say it again - bthe issue is when i am addding target for the data to be stored (datalake or data warehouse)...it is trying to create a table there... writing "validating data destination target" for like 2-3 minutes and there "Something went wrong when retriveing the lsit of table. try again later"
For me it looks like more a Fabric problem and not something on my side.
You're welcome. I'd tend to agree as I keep bumping into bugs every other day. Last night, I couldn't even create a new Power BI report with the Power BI persona--Fabric couldn't retrieve the model that was in the lakehouse after I ran all my DFg2s. The product is definitely not GA ready. Let's cross fingers it will not take 6 years to fix, like the broken CTRL-Z / Undo in Power App studio that people have been complaining about, I kid you not, for 6 years!
YairCzitrom , let's debug this - can you share the session ID where you are running into this issue.
1. In your dataflow editor, click Options -> diagnositics -> copy the session ID
2. If possible, run a HTTP capture via fiddler or browser dev tools
3. Repro the issue where in the output destination selector, it produces "Something went wrong"
4. If you are running the network capture, save it locally
(Export HAR...)
Keep the file for future references and post the session ID here.
Also, since this is routing to a gateway, make sure you turn on gateway logging (additional logging, see: https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-performance#slow-performing-queries) before the repro.
Once you reproduced the error, flush the logs and zip them up for future reference
Guys.... it is fixed
My bad... after all.
It IS all about the fire wall.
We open it on the on-prem server BUT it is not enough!
AS we are hosting it on some data center, THEY have to open the firewall and it will work.
The biggest problem now is that they are not happy about it as we open another port in thier firewall, and they cannot do the *.domainname roles apperently so they open for all!!!
Microsoft support - is there any way to give them a specific address/s to open?
