SQL monitoring support for Windows Server 2025

[steven spray]

Hello

I provisioned  a new server for monitoring but am unable to establish a connection with the sqlserver probe. The connection test eventually times out with "Probe has to be started for connection test".

Dealing with this warning in the past, it was due to TLS being required. Not this time, I can confirm this server has no TLS, encryption or even custom ports.

As a quick test (5 seconds) I disabled the local firewall and the connection was successful.

I've never seen this behaviour. There is adequate comms and I can update the probes no problem. All the required ports (48000-48099) are also open bidirectionally.

I suspect this might be because the underlying OS is Server 2025 but I'm not entirely sure. I always check the CA Compatibility Matrix but this was last updated in 2022 so the info is not dependable.

Any ideas anyone?

Thanks for reading
Steven

[Christopher Pearson]

While 2025 is supported for robot, as of the MAY 2025 matrix found here:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/23-4/installing/product-compatibility/ca-uim-probes-support-matrix.html

no probes have yet been certified on 2025.

As to the firewall, what comes to mind to me would be 1433 being blocked when the firewall is turned on.

[steven spray]

Thanks for the reply Christopher

Indeed, that was the next thing I tried to open the SQL ports, no dice. I actually found these were already open so I removed the double rules I created. For reference, below is the Compatibility Matrix page I always consult. I will now update my bookmark with this new link you shared. I'm not sure why this old/defunct one still exists confusing some of us, maybe just for posterity? ¯\_(ツ)_/¯

CA UIM Compatibility Matrix

I will play around with the firewall to see if anything I do short of disabling it sticks, maybe adding an explicit rule for the HUB IP, maybe even the secondary HUB/relay, will see.