locked
Linked server returned message "communication link failure". RRS feed

  • Question

  • Hi,

    I am getting the below error while trying to execute a Store Procedure with a Linked Server.

    Note that the same query is executing successfully when we running it manually.

    No packet drops detected during the execution. Any clue what is causing this problem.

    OLE DB provider "SQLNCLI11" for linked server "xxxxx" returned message "The specified network name is no longer available.".
    OLE DB provider "SQLNCLI11" for linked server "xxxxx" returned message "Communication link failure".
    Msg -1, Level 16, State 1, Line 0
    Session Provider: Physical connection is not usable [xFFFFFFFF].

    Regards,

    TF

    Tuesday, October 17, 2017 1:03 PM

All replies

  • Look in the SQL Server errorlog on the remote server to see if there are any stackdumps that coincides with these messages. That is not the only possible reason, but let's start there.

    Please also post the output for "SELECT @@version" for both instances.

    Exactly how do you call the procedure remotely? Just EXEC, or is part of INSERT-EXEC, or is it inside some other module or trigger?


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Tuesday, October 17, 2017 8:21 PM
  • Hi,

    Both servers have the same SQL version:

    Microsoft SQL Server 2012 (SP3) (KB3072779) - 11.0.6020.0 (X64) 
    Oct 20 2015 15:36:27 
    Copyright (c) Microsoft Corporation

    Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    I am using EXEC to call the Procedure.

    Note that I am using SQL Failover Cluster instance.

    Regards,

    Tarek


    • Edited by TarekF Wednesday, October 18, 2017 8:04 AM
    Wednesday, October 18, 2017 7:54 AM
  • Beware that SP4 for SQL 2012 came out recently. Applying SP4 may or may not resolve the issue.

    Did you check the SQL Server errorlog on the remote server?


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Wednesday, October 18, 2017 9:08 PM