Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- 〈UPDATED 2025〉

"MSSQL: Failed to fetch info data (or no data for 30m)"

The error is a common trigger in Zabbix templates, typically indicating that the Zabbix Agent 2 or ODBC poller is unable to communicate with your Microsoft SQL Server instance. This guide covers how to resolve this for both Zabbix Agent 2 and ODBC setups. 1. Verify Authentication and Macros

Server/Port

: Ensure the address is set as ipaddress,1433 (use a comma instead of a colon for SQL Server ports). zabbix mssql failed to fetch info data -or no data for 30m-

"MSSQL: Failed to fetch info data (or no data for 30m)"

The error typically indicates a communication failure between the Zabbix server/proxy and the Microsoft SQL instance, often stemming from ODBC misconfiguration , authentication issues , or network restrictions . Key Troubleshooting Areas "MSSQL: Failed to fetch info data (or no

Leila frowned. Zabbix never screamed. It whispered. And this whisper was wrong. Verify Authentication and Macros Server/Port : Ensure the

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)

Zabbix Server logs

This error appears in the or Item configuration preview . It means the Zabbix agent (or proxy) executed an item key—typically perf_instance["MSSQL$INSTANCE",...] or a custom UserParameter—and the SQL query returned no valid result set, a permissions error, or a malformed response.