Forum Discussion
OnPremise Gateway, cannot write to lakehouse
We have now managed to get the data in to the lakehouse. Greate success!
The information that I got from our hosting partner was that traffic going to pbipneu5-northeurope.pbidedicated.windows.net. was blocked. When this blockade was lifted, it started working.
New rule in firewall:
Protocol: TCP
Endpoint: pbipneu5-northeurope.pbidedicated.windows.net
Port: 1433pbipneu5-northeurope depends on what region you have chosen.
Hope this helps.
//Mikael
Super UserHi MikaelDavidsson ,
I did exactly same thing few weeks back and I can confirm that the approach I followed on getting on-premises SQL Server data to Lakehouse using Dataflow Gen 2 works. I tried it again few minutes back by bringing and writing a new table to Lakehouse.
I am not sure where things are gone wrong for you.
I wrote a blog about the whole process and configurations I followed to set this process up at my end.
Worth checking this one once. May be you can identify some difference:
https://datavibe.co.uk/getting-on-premises-sql-server-data-to-fabric-lakehouse/
Memorable MemberI read your blog page and you wrote that using Organizatinal for authentication does not work. However, that's what I used, and the UI picked up the already existing connection to the on-prem DB just fine, populated the DF Power Query UI fine. It's just when it comes to publishing that sometimes the table is created and the data persisted to the lakehouse and sometimes not. When it is, the columns are always lost and replaced by generic names such as Column1, Column2, etc...
I really don't understand why this is not working and even showing inconsistent behavior in failure.