Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Next up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now

Reply
marcoG
Advocate III
Advocate III

Lakehouse validation of the connection hangs

I have installed the latest version of the gateway(3000.178.9).
The on premise input connection works while the connection to the lakehouse hangs(VERY SLOW) on validation (both with and without gateway)

5 REPLIES 5
miguel
Community Admin
Community Admin

Hey!

I suggest reaching out to the support team by raising a new support ticket.

 

The team would be able to dig deeper to figure out what could be the situation.

marcoG
Advocate III
Advocate III

The data arrives in the staging area but not in the lakehouse I don't understand what the logic is?

 

Error: WriteToDatabaseTableFrom_TransformForOutputToDatabaseTableFrom_

null Error: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) Details: DataSourceKind = Lakehouse;DataSourcePath = Lakehouse;Message = A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server);ErrorCode = -2146232060;Number = 53;Class = 20 GatewayObjectId: 305f0d41-e624-4c13-b947-0f2761403cb7. .

What could be happening is that you may have a firewall rule that prevents data being moved by the Gateway from the staging lakehouse to its final destination.

Please reach out to our support to create a support ticket and have an engineer look at this situation.

Hi @miguel ,
if the data arrived at the cloud (in the staging area) through a gateway,

why should it now return to the premise to then reach the final destination (lakehouse)?

 

Another thing the gateway, by definition, must have only one opening of doors towards the gateway
and not open the doors for each lake house otherwise what is it the gateway for?

The Gateway is effectively the engine doing all the moving and transformation of the data. 

 

I'm not sure I follow the last question. Could you please rephrase it?

 

For this specific scenario, I'd recommend reaching out to our support team so they can do a more thorough investigation.

Helpful resources

Announcements
FabCon and SQLCon Highlights Carousel

FabCon &SQLCon Highlights

Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.

New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Fabric Update Carousel

Fabric Monthly Update - March 2026

Check out the March 2026 Fabric update to learn about new features.

Top Solution Authors
Top Kudoed Authors