Zabbix Agent 2 with Plugins: Error with MSSQL Service's TCP port state

[ElVengador]

Hello guys,

I have configured Zabbix Agent 2 and Plugins - both Version 7.0.6 - and want to monitor my SQL Server. It's a Server 2016 Standard on a Windows Server 2019 Standard and I have done all the steps in the documentation. BUT I always get the message that the Service's TCP port state is down. I receive all performance data but the item for the port always says "Down". I am monitoring 2 instances, created separated hosts in Zabbix with the FQDN of my SQL-Server and it's running as expected as the port state described above.

Does anyone know what's the problem here? And before anyone asks: Yes, I tested also with disabled Windows Firewall.

Thank you and best regards, Michael

[Jan_Prusinowski]

Use a tool like netstat to check if the SQL Server is actually listening on the expected TCP port:

netstat -ano | findstr :<port_number>

[rmc]

It is a very strange problem.
I have the exact same thing, everything works fine but "service is unavailable" is always in problem state.
Funny thing is that when I copy that trigger (which is from the template) and do not change anything but the name, it is working perfectly.

So it seems that maybe some macro's are not read correctly by the template or something?

If anybody has info on this, I would be very happy


Edit: I still would like to know why, but this solves my problem:

https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/498739-mssql-service-is-unavailable

[cyber]

Edit: I still would like to know why, but this solves my problem:
https://www.zabbix.com/forum/zabbix-...is-unavailable

If you change your item type from "simple check" to "zabbix agent", as is described in that thread, you effectively change, who is asking and from where ... "simple check" -> server/proxy performs the check towards host: port, "zabbix agent" -> server/proxy asks specific agent to perform the check. First one can have all kind of network restrinctions on the way, second one most probably performs the check locally inside the host.