Resolving "Failed to query instance" and "Login timeout expired" Errors during SQL Server dSource and VDB Operations (KBA1751)

Applicable Delphix Versions 

Click here to view the versions of the Delphix engine to which this article applies

Major Release	All Sub Releases
6.0	6.0.0.0, 6.0.1.0, 6.0.1.1, 6.0.2.0, 6.0.2.1, 6.0.3.0, 6.0.3.1, 6.0.4.0, 6.0.4.1, 6.0.4.2, 6.0.5.0, 6.0.6.0, 6.0.6.1, 6.0.7.0
5.3	5.3.0.0, 5.3.0.1, 5.3.0.2, 5.3.0.3, 5.3.1.0, 5.3.1.1, 5.3.1.2, 5.3.2.0, 5.3.3.0, 5.3.3.1, 5.3.4.0, 5.3.5.0, 5.3.6.0, 5.3.7.0, 5.3.7.1, 5.3.8.0, 5.3.8.1, 5.3.9.0
5.2	5.2.2.0, 5.2.2.1, 5.2.3.0, 5.2.4.0, 5.2.5.0, 5.2.5.1, 5.2.6.0, 5.2.6.1
5.1	5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0, 5.1.10.0
5.0	5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1, 5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4

Issue

When attempting to add an Environment, or when performing operations on a dSource or VDB, the Delphix Engine may report warnings or errors that indicate that it is unable to connect to the SQL Server instance.

These errors may be reported as:

WARNING: Failed to query instance "<INSTANCE NAME>" on host "<HOSTNAME>".

Make sure that the SQL Server instance is listening to local TCP connections on port "<PORT>". If the port has changed, refresh environment "<HOSTNAME>". Also make sure that the Delphix Connector service is running on host "<IP ADDRESS>", and the OS user "<DOMAIN\USER>" has the required privileges on the instance.

or:

Sqlcmd: Error: Microsoft ODBC Driver 11 for SQL Server : TCP Provider: No connection could be made because the target machine actively refused it.
.
Sqlcmd: Error: Microsoft ODBC Driver 11 for SQL Server : Login timeout expired.
Sqlcmd: Error: Microsoft ODBC Driver 11 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..
die : Error: attach_vdb failed
At C:\Program Files\Delphix\DelphixConnector\4206020e-3896-b844-e150-5a61861b4c
45-vdb-306\SCRIPT\AttachVDB.ps1:23 char:12
+         die <<<<  "$($args[0])"
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorExcep
   tion
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
   n,die

While they may occur during any operation, the errors are most likely to occur when an Environment is initially added.

Troubleshooting Errors

There are several possible reasons for these errors to occur. Common causes include:

• The SQL Server Instance is not running
• The SQL Server Instance is not configured to allow TCP/IP connections
• There are firewalls in place, preventing connections to SQL Server
• The SQL Server configuration is causing execution of sqlcmd to fail

The Resolution section describes each of these issues, and provides recommended steps to resolve them.

The warning or error provided by the Delphix Engine may provide more information on which SQL Server Instance is involved in the failure. If the affected Environment has been added as a Cluster, the warning or error may also provide detail on which node of the cluster was being accessed when the failure occurred.

Before proceeding with troubleshooting, try connecting to the affected SQL Server instance using your normal SQL Server tools (e.g. SQL Server Management Studio). The success or failure of this connection may help you rule out some possible causes.

Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.

PS C:\> sqlcmd
Failed to load resource file SQLCMD.rll.