Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- May 2026

| Cause | Solution | |-------|----------| | ODBC timeout | Increase QueryTimeout in item → odbc.select[DSN,query,,30] (30 sec) | | Zabbix server timeout | Set Timeout=10 in zabbix_server.conf (restart server) | | Intermittent network | Deploy Zabbix proxy on same host as MSSQL. | | Agent overload | Increase StartAgents and StartPollersUnreachable. |

| Error Message | Zabbix Interpretation | Typical Impact | |---------------|----------------------|----------------| | Failed to fetch info data | The item’s pre-processing or retrieval script returned non-zero exit code or error output. | Immediate data loss for that poll. | | No data for 30m | The item has not received any new value for the last 30 minutes (configured in zabbix_server.conf or item’s update interval). | Sustained monitoring outage. |

-- For Zabbix dashboard to monitor fetch status
SELECT 
  h.hostid,
  h.name as host,
  i.key_,
  i.lastvalue as fetch_status,
  CASE WHEN i.lastvalue = '0' THEN 'OK' ELSE 'FAILED' END as status,
  FROM_UNIXTIME(i.lastclock) as last_check
FROM items i
JOIN hosts h ON i.hostid = h.hostid
WHERE i.key_ = 'ms.sql.fetch_success'
AND (i.lastvalue = '1' OR i.lastclock < UNIX_TIMESTAMP() - 1800)
ORDER BY i.lastclock DESC;

Zabbix item for MSSQL returns "failed to fetch info data -or no data for 30m-". Likely causes: query errors, permissions, network, timeout, template/item misconfiguration, or agent/ODBC issues. zabbix mssql failed to fetch info data -or no data for 30m-

| Cause | Solution | |-------|----------| | Permission denied | GRANT VIEW SERVER STATE TO zabbix_user; | | Missing database | Ensure referenced DB is online or use WHERE DB_NAME() = 'master' | | SQL syntax error | Test query in SSMS before putting in Zabbix item. | | Agent 2 misconfiguration | Use correct connection string: Server=.;Trusted_Connection=True; |

Sometimes, it’s not an error. A development SQL Server with no active databases, no user connections, and auto_close = ON will show zero for User Connections and Batch Requests/sec – resulting in “no data for 30m” because the trend function expects a positive delta. | Cause | Solution | |-------|----------| | ODBC

Fix: Adjust the trigger expression. Replace nodata(30m) with nodata(30m) and last()<>0 or simply increase the threshold for low-traffic servers.

This is a trending/front-end message from the Zabbix UI. It means the server has successfully requested data from the agent, but the value is persistently empty, NULL, or exceeds the zabbix.history sync period. Zabbix item for MSSQL returns "failed to fetch

This often indicates:

Key insight: Zabbix does not time out on “no data” – it actively receives empty data. The problem is logical, not network connectivity.

---