- 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
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)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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. .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
Subject | Author | Posted | |
---|---|---|---|
Anonymous
| 09-16-2024 09:27 AM | ||
02-03-2025 11:47 PM | |||
12-07-2023 03:24 AM | |||
02-27-2024 11:53 AM | |||
11-28-2024 03:10 AM |
User | Count |
---|---|
5 | |
2 | |
1 | |
1 | |
1 |