Error "Data Engine Error: 8" on Computers with Multiple Network Adapters

Published: 24 May 2013
Last Modified Date: 21 Jul 2016


When running Tableau Server with high availability configured on computers with multiple network adapters, you may see the following error messages:
DataSourceException: Tableau Data Engine Error: 8: An existing connection was forcibly closed by the remote host

DataSourceException: Tableau Data Engine Error: 8: An established connection was aborted by the software in your host machine

The IP address shown in the error messages is the IP address of the secondary network. In addition, the status of the Data Engine may show as "Down."


  • Tableau Server
  • High availability configured
  • Computers hosting Tableau Server have several network adapters


Option 1

Make sure you have only one IP address per network interface card (NIC).

Option 2

Use the following workaround.

Step 1: On all computers hosting Tableau Server, set the network adapter priority to the highest

  1. In the Command Prompt, run the following command: ncpa.cpl
  2. When the Network Connection window opens, press the Alt key.
  3. Select Advanced > Advanced Settings.
  4. Select the correct network adapter and press the "up" arrow button to move it to the top of the list.

Step 2: Restart Tableau Server

  1. Open the Command Prompt as an administrator run one of the following commands:
    • On a 32-bit machine: cd "C:\Program Files\Tableau\Tableau Server\[version]\bin"
    • On a 64-bit machine: cd "C:\Program Files (x86)\Tableau\Tableau Server\[version]\bin"
  2. ​Type the following command to restart Tableau Server: tabadmin restart


The Data Engine configured itself to use the network interface with the highest priority during a previous restart.

Additional Information

Disabling additional network adapters during installation and when starting Tableau Server will also resolve this issue. However, it would become necessary to disable the additional network cards every time Tableau Server is restarted.
Did this article resolve the issue?