This is a generic trigger often seen when using the "MSSQL by ODBC" or "MSSQL by Zabbix agent 2" templates. It indicates that the master "Info" item—which discovery and other dependent items rely on—is not receiving data. Core Causes & Fixes 1. Database Permissions (Most Common)
: If multiple MSSQL hosts are failing, increase the number of ODBC pollers in your zabbix_server.conf by setting StartODBCPollers=5 (or higher) and restarting the service. 2. Verify SQL Permissions zabbix mssql failed to fetch info data -or no data for 30m-
: Any change to the plugin configuration or the agent requires a full service restart to apply Encryption and Driver Version Modern drivers (like ODBC Driver 18) default to Encrypt=yes This is a generic trigger often seen when
: If the SQL instance is under heavy load, the info fetch might timeout. Try increasing the parameter in the Zabbix server/agent configuration files. Detect Issues in Your Zabbix Instance Before It's Too Late 25 Mar 2026 — Database Permissions (Most Common) : If multiple MSSQL
MSSQL_CMD="/opt/mssql-tools/bin/sqlcmd" SERVER="localhost" DB="master" QUERY="SELECT 1 as FetchTest"