none
Named Pipes Provider: Could not open a connection to SQL Server [53].

    Question

  •  

    hi all,

    trying to set up linked server but it thows error listed above.

     

     

    Thanks,

    N P

    Thursday, July 31, 2008 6:44 PM

Answers

  • Hi N P,

     

    Error 53 is an OS error which maps to ERROR_BAD_NETPATH (The network path was not found). Depending on how you setup your linked server, a connection from the current SQL Server process to the remote one will be attempted. Due to the nature of the error, it seems to be attempted with Named Pipes protocol and some of the OS calls (like CreatePipe for instance) returns the OS error 53. In most of the cases this is related to the network name resolution of the remote server or it might be permissions-related, e.g. if your current SQL Server instance is running under Local System account (which doesn't have network access privileges).

     

    Please see the detailed description on how to setup a linked server in the SQL Server Books Online, but to start you could try the following:

    (a) Examine your current SQL Server service account (the local instance - the one where you are trying to setup the linked server to the remote machine). Depending on the authentication configured for the linked server, you might need to use an account which has network access. You could examine the service account using Management Studio or Configuration Manager

     

    (b) Check the network name of the remote server. To eliminate network resolution issues, try to connect to it from the local SQL Server machine via sqlcmd or try to setup the linked server with the IP address of the remote machine instead of the name.

     

    (c) Force using TCP/IP protocol instead of named pipes by either prefixing the server name with "tcp:" or by setting the protocols order (Configuration Manager) or by creating an explicit alias for it.

     

    If the issue persists, please post the exact error again and your linked server configuration (security, etc.).

    HTH,
    Jivko Dobrev - MSFT
    --------------------------------------------------------------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights.

     

    Thursday, July 31, 2008 10:01 PM

All replies

  • Hi N P,

     

    Error 53 is an OS error which maps to ERROR_BAD_NETPATH (The network path was not found). Depending on how you setup your linked server, a connection from the current SQL Server process to the remote one will be attempted. Due to the nature of the error, it seems to be attempted with Named Pipes protocol and some of the OS calls (like CreatePipe for instance) returns the OS error 53. In most of the cases this is related to the network name resolution of the remote server or it might be permissions-related, e.g. if your current SQL Server instance is running under Local System account (which doesn't have network access privileges).

     

    Please see the detailed description on how to setup a linked server in the SQL Server Books Online, but to start you could try the following:

    (a) Examine your current SQL Server service account (the local instance - the one where you are trying to setup the linked server to the remote machine). Depending on the authentication configured for the linked server, you might need to use an account which has network access. You could examine the service account using Management Studio or Configuration Manager

     

    (b) Check the network name of the remote server. To eliminate network resolution issues, try to connect to it from the local SQL Server machine via sqlcmd or try to setup the linked server with the IP address of the remote machine instead of the name.

     

    (c) Force using TCP/IP protocol instead of named pipes by either prefixing the server name with "tcp:" or by setting the protocols order (Configuration Manager) or by creating an explicit alias for it.

     

    If the issue persists, please post the exact error again and your linked server configuration (security, etc.).

    HTH,
    Jivko Dobrev - MSFT
    --------------------------------------------------------------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights.

     

    Thursday, July 31, 2008 10:01 PM
  • Thanks it was the permission related issue on my server and i dont have those rights so now i have resolved this issue.
    Saturday, August 02, 2008 12:49 AM
  • I get this error when I try to use asynchronous methods to access the database. Synchronous access works just fine so I don't think it is a permissions issue. Ideas?

    Kevin


    Kevin Burton
    Tuesday, November 09, 2010 5:09 AM