Post reply

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

  • July 12, 2017 at 5:54 am

    #327357

    Hi,

    We have configured  Transactional Replication between SERVER A and SERVER B and Server C is Configured as distributor. When I check the SnapShot agent status, It is showing as "Named Pipes Provider: Could not open a connection to SQL Server [5]. "

    I have googled the issue and checked the configurations below

    1. SQL service running and defined port is added to firewall setting.
    2. SQL browser is running as all servers
    3. Remote Desktop is enabled.
    4. Ping is happening between the servers
    5. TCP/IP and NamedPipes have been enabled in Network configuration protocols
    6. Shared Memory(1), TCP/IP(2), NamedPipes(3) are in the given order

    I am struck here in debugging the issue. When I checked https://docs.microsoft.com/en-us/sql/tools/configuration-manager/sql-server-browser-service,
    it understood that NamedPipes will use SQL Browser's default port 1434. I thought to check whether this port is added in firewall exception. But before that I feel to post the issue here to get right solution and check list.

    Please help.

    🙂

  • July 13, 2017 at 2:29 am

    #1950689

    Can somebody share your valuable thoughts and suggestions on this.

    🙂

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply