Forum Discussion

hammadhassan90's avatar
hammadhassan90
Regular Visitor
3 years ago

Running into refresh issues with Dataflow Gen 2

I am running into refresh failures when using SQL On Prem data as source and Lakehouse as destination. Previously, i was getting the following error: Mashup Exception Error: Couldn't refresh the ent...
Dataflow
Need Help
rubayatyasmin's avatar
rubayatyasmin
Community Champion
3 years ago

Hi, hammadhassan90 

 

It looks like you are facing two different issues here:

  1. A network-related error or instance-specific error that occurred while establishing a connection to SQL Server.
  2. The gateway proxy is unable to connect to SQL.

The first issue usually occurs due to incorrect SQL Server instance name or if the SQL Server does not allow remote connections. If you've already checked these, and your SQL Server instance is running and allows remote connections, the issue could be a firewall blocking the connection or not having the correct client protocols enabled in SQL Server configuration manager.

The second issue suggests a problem with the gateway setup. While you've allowed a URL through your firewall, it's also important to check whether your gateway is properly installed, configured, and up to date.

Here are a few things you can try to resolve these issues:

  1. Check your SQL Server Configuration:

    • In the SQL Server Configuration Manager, check if TCP/IP is enabled under SQL Server Network Configuration > Protocols for [YourInstanceName].
    • Under SQL Server Native Client Configuration > Client Protocols, make sure TCP/IP is enabled.
    • Check if the SQL Server Browser service is running, as this service is used to provide the SQL Server connection to the client.

  2. Check Firewall settings:

    • Ensure that your firewall allows incoming connections for the SQL Server port (default is 1433).
    • Add an exception in the firewall for sqlbrowser.exe.

  3. Check your Data Gateway:

    • Make sure that your gateway is running and is updated to the latest version.
    • Ensure the correct credentials are entered for the data source in the gateway configuration.
    • Try to restart the gateway service and test the connection again.
    • If you're using a standard mode (single-tenant) gateway, check if adding *.servicebus.windows.net to your allowlist helps, as it's the endpoint used by Azure Service Bus, which is the technology the on-premises data gateway uses to facilitate communication between the cloud and on-premises.