Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Dear all
we want to write data to a Fabric Warehouse via dataflow gen 2 to an existing Fabric Warehouse, but get the error message below.
The dataflow reads from an on-premise MS SQL database via a gateway. The reading works with no issue and the dataflow runs fine as long we do not try to write the results to our Warehouse in the cloud.
The strange thing is that it worked a few times, but now it stopped working with the mentioned error.
Anyone any ideas what this could be?
Thanks!
Solved! Go to Solution.
Hi @v-huijiey-msft @FabianSchut
thanks for your feedback - I asked my colleagues who administer our cloud to check.
Probably you are right that it is related to firewall / network settings.
For the moment I was able to solve it via the workaround described in at the end of the link below (splitting in two dataflows: one just reading the on-prem source and the other taking the first dataflow as input and then writing to the data warehouse):
https://learn.microsoft.com/en-us/fabric/data-factory/gateway-considerations-output-destinations
Hi @nigi1978 ,
Thanks for the reply from FabianSchut .
The error message indicates that a network problem or instance-specific error was encountered while connecting to SQL Server.
Here are some of my suggestions:
1. Make sure the SQL Server instance is running.
2. Check that SQL Server is configured to allow remote connections. In SQL Server Configuration Manager, ensure that the “TCP/IP” and “Named Pipes” sections of the “SQL Server Network Configuration” are configured to allow remote connections. Named Pipes” of ‘SQL Server Network Configuration’ are enabled.
3. Ensure that the firewall is not blocking the SQL Server port (the default instance is usually 1433). You may need to add a new inbound rule to the firewall to allow this port.
4. Make sure the SQL Server Browser service is running.
After checking the above factors, remember to restart your current SQL Server instance before reconnecting in Dataflow Gen2 to see if it works.
If you have any other questions please feel free to contact me.
Best Regards,
Yang
Community Support Team
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
Hi @v-huijiey-msft @FabianSchut
thanks for your feedback - I asked my colleagues who administer our cloud to check.
Probably you are right that it is related to firewall / network settings.
For the moment I was able to solve it via the workaround described in at the end of the link below (splitting in two dataflows: one just reading the on-prem source and the other taking the first dataflow as input and then writing to the data warehouse):
https://learn.microsoft.com/en-us/fabric/data-factory/gateway-considerations-output-destinations
Hi @nigi1978 ,
It looks like you have found a solution. Could you please mark this helpful post as “Answered”?
This will help others in the community to easily find a solution if they are experiencing the same problem as you.
Thank you for your cooperation!
Best Regards,
Yang
Community Support Team
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
Hi @nigi1978 ,
Thanks for the reply from FabianSchut .
The error message indicates that a network problem or instance-specific error was encountered while connecting to SQL Server.
Here are some of my suggestions:
1. Make sure the SQL Server instance is running.
2. Check that SQL Server is configured to allow remote connections. In SQL Server Configuration Manager, ensure that the “TCP/IP” and “Named Pipes” sections of the “SQL Server Network Configuration” are configured to allow remote connections. Named Pipes” of ‘SQL Server Network Configuration’ are enabled.
3. Ensure that the firewall is not blocking the SQL Server port (the default instance is usually 1433). You may need to add a new inbound rule to the firewall to allow this port.
4. Make sure the SQL Server Browser service is running.
After checking the above factors, remember to restart your current SQL Server instance before reconnecting in Dataflow Gen2 to see if it works.
If you have any other questions please feel free to contact me.
Best Regards,
Yang
Community Support Team
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
Is it possible that someone added some security rules for Fabric like Entra Conditional Access? And who is the owner of the Warehouse? Is something changed there?
User | Count |
---|---|
8 | |
1 | |
1 | |
1 | |
1 |
User | Count |
---|---|
11 | |
2 | |
2 | |
1 | |
1 |