Edit

Share via

Troubleshoot a virtual network data gateway

  • Article

Troubleshoot a virtual network data gateway connecting to a SQL endpoint

If you're using a virtual network data gateway and a private endpoint to connect to a data source like SQL, you might experience sporadic broken TCP connections to the data source. The queries might fail with error messages like invalid operation, the connection is closed, an existing connection was forcibly closed by the remote host, or a transport-level error has occurred. This experience is a known issue and will be fixed for our GA release.

Troubleshoot a virtual network data gateway network

You can troubleshoot your virtual network data gateway network if you're experiencing network connectivity issues between the gateway and the data sources it needs to connect to.

What is virtual network data gateway network troubleshooting?

The troubleshooting information includes the following data:

  • Ethernet adaptor information: Provides information about the network settings of the gateway. You can use this information to check if the Internet Protocol (IP) is expected in the correct subnet. You can also check if the Domain Name System (DNS) setting is correct.

  • Name resolution and test network connection: Provides the capability to troubleshoot connectivity between the container and the endpoint using either the IP or domain name and port. If this test fails, it's likely that the container doesn't respond well. This issue can occur when the DNS doesn't respond with an address or when the network is unavailable. If the network test fails, there's likely an issue with the assignment of the IP configuration of the data source.

How to troubleshoot the network of the gateway

  1. Navigate to Power Platform admin center.

  2. Select Virtual network data gateways.

  3. Select the gateway you want to troubleshoot and then select Troubleshoot network in the ribbon at the top of the page.

    Image of the Power Query admin center with Data (preview) menu item open, a gateway selected, and the Troubleshoot network selection emphasized.

    The gateway needs to be active. If the gateway is auto paused, it will be started, and it can take up to 2 minutes for the gateway to become active.

    Image of the Troubleshoot network panel while the network connection is being tested.

    Note

    The troubleshooting panel automatically triggers a status check. If the status fails, then the troubleshooting button is disabled because the gateway isn't connected. Refreshing the status will clear the troubleshooting result state.

  4. If the status check succeeded, you can view your ethernet adapter information, including the DNS servers, IPv4 address, subnet mask, and the default gateway.

    Image of the Troubleshoot network panel after the status check succeeded, with IP values displayed for DN servers, IPv4 address, Subnet mask, and Default gateway.

  5. To test the IP configuration, fill in the IP or Fully Qualified Domain Name (FQDN) and the port number, and then select the troubleshoot button. The input of the port must be a whole number—decimals and strings aren't allowed.

    Image of Name resolution panel with values for DNS servers, Addresses, Aliases, Name of computer contacted, Network alias interface, Remote address, and Ping source address.

Note

If you get an Unable to retrieve <IPConfig/TestNetConnectinon/Host Network> information. message, retry troubleshooting and ensure you've set the right IP/FQDN and port number.