Installed SQL Monitor on a new server but Monitor service fails to start

Graham_B

We are moving SQL Monitor on to a new server, leaving the repository on the existing server. During the install process the Base Monitor service fails to start, leaving the service perpetually in the Starting state. I'm installing as an administrator on the server and the account the service uses is also an administrator on the server. Before running the installer we had de-activated the licenses on the existing server and stopped the Base Monitor Service. Looking at the Event log on the new server, I see this error

2019-05-20 03:05:56,097 [1] FATAL RedGate.SqlMonitor.Engine.Alerting.Base.Service.MonitoringAndStorageService [(null)] - Unhandled exception on start.

System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted

   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)

   at System.Net.Sockets.Socket.Bind(EndPoint localEP)

   at RedGate.SqlMonitor.Common.Networking.Server.AsynchronousSocketListener..ctor(IThreadPool threadPool, Action`1 streamConsumer, Int32 port, Int32 backlog)

   at RedGate.SqlMonitor.Common.Networking.Server.RpcSynchronousTcpServer.StartTcpServer()

   at RedGate.SqlMonitor.Engine.Alerting.Base.Service.MonitoringAndStorageService.OnStart(String[] args)System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted

   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)

   at System.Net.Sockets.Socket.Bind(EndPoint localEP)

   at RedGate.SqlMonitor.Common.Networking.Server.AsynchronousSocketListener..ctor(IThreadPool threadPool, Action`1 streamConsumer, Int32 port, Int32 backlog)

   at RedGate.SqlMonitor.Common.Networking.Server.RpcSynchronousTcpServer.StartTcpServer()

   at RedGate.SqlMonitor.Engine.Alerting.Base.Service.MonitoringAndStorageService.OnStart(String[] args)

What would be causing this error?

Graham_B

Problem resolved. Was installing 9.0.12, installed 9.0.2 instead and now all running as expected.

Russell D

I would have expected to see a different error than that to be honest but glad its up and running now.

VuCanDo

We just bought the SQLBelt.  Should I install SQL monitor in web server or directly on the PROD SQL Server?  I never install this product before

Russell D

Have a look here: https://documentation.red-gate.com/sm/getting-started, this should help.

semonbright

A SocketException is thrown by the Socket and Dns classes when an error occurs with the network. Most of the time these are connectivity issues due to different IP protocols (IPV4/IPV6) between the two server/computers trying to communicate or extra authentication rules setup on one of the computers for in/out connectivity.  Ways to troubleshoot this  SocketException are, check you have proper internet connection is there on your machine or not, and you are able to ping the remote server or not. Possible causes for the error:

    You are using the wrong IP address.

    You are using the wrong port.

    Firewall blocking the connection.