Home » Uncategories » Sql Server Error (-2147467259) Text: 'login Timeout Expired' Updated FREE

Sql Server Error (-2147467259) Text: 'login Timeout Expired' Updated FREE

Sql Server Error (-2147467259) Text: 'login Timeout Expired'

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

Last updated
Save as PDF

Applicable Delphix Versions

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

Major Release	All Sub Releases
half dozen.0	6.0.0.0, 6.0.1.0, 6.0.1.1, half dozen.0.two.0, 6.0.2.1, half-dozen.0.3.0, 6.0.iii.1, 6.0.4.0, 6.0.4.ane, six.0.4.2, half dozen.0.5.0, 6.0.6.0, half dozen.0.six.one, 6.0.7.0
5.3	5.iii.0.0, v.3.0.1, v.iii.0.two, 5.three.0.three, v.3.1.0, five.three.ane.one, 5.3.1.two, v.3.2.0, v.3.3.0, five.3.3.1, 5.three.four.0, 5.3.5.0, 5.3.6.0, 5.3.7.0, 5.3.7.one, 5.3.8.0, v.3.8.1, 5.3.ix.0
5.2	5.2.2.0, v.2.2.1, 5.two.3.0, 5.2.4.0, 5.ii.5.0, 5.2.5.1, 5.2.6.0, 5.ii.6.1
5.1	5.ane.0.0, 5.1.i.0, 5.1.2.0, 5.ane.three.0, 5.1.4.0, five.ane.5.0, 5.1.v.1, 5.ane.half dozen.0, 5.one.7.0, 5.1.8.0, five.1.viii.1, five.1.nine.0, 5.1.ten.0
5.0	5.0.1.0, 5.0.i.i, v.0.2.0, 5.0.2.1, 5.0.ii.2, five.0.2.3, five.0.3.0, 5.0.3.1, v.0.4.0, 5.0.4.1, 5.0.5.0, 5.0.five.1, 5.0.five.two, 5.0.five.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 information technology is unable to connect to the SQL Server instance.

These errors may be reported equally:

                                  Warning:                                  Failed to query instance "<INSTANCE Proper name>" on host "<HOSTNAME>".  Make sure that the SQL Server case is listening to local TCP connections on port "<PORT>". If the port has changed, refresh environment "<HOSTNAME>". Too make sure that the Delphix Connector service is running on host "<IP Accost>", and the OS user "<DOMAIN\USER>" has the required privileges on the example.

or:

Sqlcmd: Error: Microsoft ODBC Driver 11 for SQL Server : TCP Provider: No connection could be made considering the target automobile 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 mistake has occurred while establishing a connection to SQL Server. Server is not plant or not accessible. Check if instance name is correct and if SQL Server is configured to permit remote connections. For more information run into SQL Server Books Online.. dice : Mistake: attach_vdb failed At C:\Plan 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    due north,die

While they may occur during whatsoever 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. Mutual causes include:

The SQL Server Example is non running
The SQL Server Instance is not configured to let TCP/IP connections
In that location 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 problems, and provides recommended steps to resolve them.

The alert or error provided by the Delphix Engine may provide more data on which SQL Server Instance is involved in the failure. If the affected Environment has been added as a Cluster, the alarm or fault may also provide particular on which node of the cluster was beingness accessed when the failure occurred.

Before proceeding with troubleshooting, attempt connecting to the affected SQL Server instance using your normal SQL Server tools (east.k. SQL Server Management Studio). The success or failure of this connectedness may help y'all rule out some possible causes.

Resolution

The SQL Server Instance is non running

In some cases, SQL Server will not be responding to login attempts considering the SQL Server Instance is non running, perhaps due to failure or scheduled maintenance.

This tin can be verified by opening the Services control panel on the affected Source or Target environment.

In the following example, the SQL Server ExampleSQL2008 is non running.

Resolution

Start the affected SQL Server instance.

The SQL Server Case is not configured to allow TCP/IP connections

Some editions of SQL Server ship with TCP/IP intentionally disabled, or TCP/IP may have been disabled for the SQL Server Case considering it was not previously required.

To confirm whether TCP/IP is correctly configured for a SQL Server Example, connect to the affected Source or Target surroundings and open the Sql Server Configuration Manager . In the tree that appears, expand the SQL Server Network Configuration object and select Protocols for <Your Instance> .

In the following case, TCP/IP has been disabled for theSQL2008 instance.

Resolution

Right-click "TCP/IP', select Properties , and change Enabled to "Yeah". You volition need to restart the SQL Server Example before the changes have upshot.

There are firewalls in place, preventing connections to SQL Server

One time you lot have verified that the service is running and listening for TCP/IP connections, it is important to verify that your Windows Server and your network devices are allowing connections betwixt the Delphix Engine and SQL Server.

Host-based firewalls tin can be checked using the Windows Firewall with Advanced Security awarding.

To ensure that the advisable rules are in place with other network devices, it may be necessary to engage your Network or System assistants teams.

A list of ports that are used by the Delphix Engine is available in our document Network Access Requirements for SQL Server. Please annotation that you may demand to open additional ports for "Named Instances" of SQL Server or if SQL Server has been configured to run on a not-standard port.

Resolution

Piece of work with your System and Network administrators to verify that the appropriate access is in identify.

The SQL Server configuration is causing execution of`sqlcmd` to fail

In some cases, a problem with the server's configuration prevents thesqlcmd application from loading its required libraries. This, in turn, will cause some operations initiated by the Delphix Engine to fail.

To verify whether this is an issue, launch PowerShell from the affected Source or Target host, and attempt to runsqlcmd. A "Failed to load resource" fault indicates that this host may be misconfigured.

Windows PowerShell Copyright (C) 2009 Microsoft Corporation. All rights reserved.  PS C:\> sqlcmd Failed to load resource file SQLCMD.rll.