Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- [95% Quick]

A: ODBC items execute on the server/proxy, not the agent. Ensure your Zabbix server has ODBC drivers installed.

Fix these in sequence, and the MSSQL template will return to reliable, continuous data collection.

Failed to fetch info data (or no data for 30m) zabbix mssql failed to fetch info data -or no data for 30m-

[MSSQL_PROD] Driver = ODBC Driver 17 for SQL Server Server = 192.168.1.100,1433 Database = master

Timeout=30

The Zabbix agent cannot reach the SQL Server due to firewall rules, incorrect URI/DSN configuration, or SSL/TLS certificate mismatches.

A: No. Often it’s just a query accessing a missing database or a permission error. A: ODBC items execute on the server/proxy, not the agent

If you use active Zabbix agent + ODBC (rare), check proxy logs instead.

If the error is intermittent (e.g., "No data for 30m" followed by data), check if the queries are timing out due to blocking. If the SQL Server is under heavy load, and the monitoring user tries to read DMVs, it might get blocked. Granting higher permissions (like sysadmin ) generally bypasses some locking contention, but introduces security risks. A safer alternative is optimizing the QueryTimeout in the ODBC DSN. Failed to fetch info data (or no data