This specific error in typically triggers when the monitoring system hasn't received any data from the MSSQL instance for a prolonged period (30 minutes), often due to ODBC configuration issues or insufficient permissions for the monitoring user . Alert Message Draft
: If you can connect via sqlcmd but not Zabbix, you may need to specify TrustServerCertificate=Yes in your odbc.ini file or ensure the Microsoft ODBC Driver 18 is properly handling encryption. Database Permissions zabbix mssql failed to fetch info data -or no data for 30m-
: MSSQL named instances often use dynamic ports. Ensure your DSN or macro includes the correct port (e.g., Server = 192.168.1.1,1433 ). 1. Fix Connection & Driver Issues This specific error in typically triggers when the
USE master; GRANT VIEW SERVER STATE TO [NT SERVICE\ZabbixAgent]; GRANT CONNECT SQL TO [NT SERVICE\ZabbixAgent]; Server = 192.168.1.1