Connect to remote database not using named pipes

Question

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?

martin.susil · Answer

Actually SQL Server User Experience Monitor should be working over TCP when you are trying to monitor remote SQL server.

Are you sure that TCP is enabled on that remote server and there is no firewall blocking the connection? If so, please open a support ticket and reference this thread. We will look into it.

aLTeReGo · Answer

The APM SQL User Experience Monitor currently only supports Named Pipes. There is no way to switch this to use TCP/IP sockets. I will however log this as a feature request.