Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- (PRO)

Using the same DSN, username and password as the isql test fails in Zabbix with the following error: Cannot connect to ODBC DSN: [

Before diving into the troubleshooting steps, it's essential to understand the possible causes of these errors:

Ensure the DSN listed in odbc.ini matches the $MSSQL.DSN macro. zabbix mssql failed to fetch info data -or no data for 30m-

Zabbix nodata trigger, really a lifesaver | by Werner Dijkerman

From the Zabbix server or proxy:

The Zabbix trigger alert indicates that your Zabbix server or agent cannot retrieve performance metrics from your Microsoft SQL Server instance. This error usually stems from an environment-level breakdown rather than an issue with SQL Server itself, often caused by misconfigured authentication, missing database permissions, network/firewall blocks, or TLS certificate mismatches .

The "Failed to fetch info data" or "no data for 30m" error in Zabbix for MSSQL typically indicates a connection or permission failure between the Zabbix agent (or server/proxy via ODBC) and the SQL Server Immediate Troubleshooting Steps Using the same DSN, username and password as

Restart the Zabbix Agent 2 service.

Before diving into the solutions, it's helpful to categorize the problem. The error typically falls into one of the following areas, each with distinct symptoms: The "Failed to fetch info data" or "no

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

Open /etc/zabbix/zabbix_agent2.conf (Linux) or zabbix_agent2.conf (Windows) and update the timeout: Timeout=15 Use code with caution.