2 Replies Latest reply: Feb 15, 2012 4:22 AM by martin.susil RSS

Connect to remote database not using named pipes

DaveAz
Currently Being Moderated

We occasionally get this error when monitoring jobs on remote database:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I was asked to find out if we can get APM SQL Experience Monitor to connect to the remote database via TCP/IP instead of Named Pipes.

Is this possible, and if so, how?

More Like This

  • Retrieving data ...