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

The cause of this "no data" scenario is almost never a single, obvious problem. It is typically the result of a breakdown somewhere in the complex chain of connections that spans from the Zabbix server all the way to the SQL Server's internal performance counters. This guide provides a systematic, step-by-step approach to diagnose and resolve the issue.

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.

You’ve configured Zabbix to monitor your critical Microsoft SQL Server instances. The templates are applied, the user macro is set, and for a few hours, everything looks perfect. Then, without warning, your dashboard turns grey. The dreaded error appears: zabbix mssql failed to fetch info data -or no data for 30m-

zabbix_get -s <SQL_HOST_IP> -k "perf_instance[\MSSQLSERVER,'SQLServer:Databases(*)\Data File(s) Size (KB)',_Total]"

A frequent mistake in /etc/odbc.ini is defining the SQL Server port using the standard Port = 1433 directive. The Microsoft SQL Server ODBC driver does not process ports this way. It requires the port to be appended to the server IP address or hostname using a , not a colon or a separate line. Incorrect: Server = 192.168.1.50 and Port = 1433 Correct: Server = 192.168.1.50,1433 2. Address TLS Encryption and Certificates The cause of this "no data" scenario is

These permissions are the minimum required for the official "MSSQL by ODBC" template to function correctly.

Typically C:\Program Files\Zabbix Agent\zabbix_agentd.log (Windows) or /var/log/zabbix/zabbix_agent2.log (Linux). This is a trending/front-end message from the Zabbix UI

Driver=ODBC Driver 17 for SQL Server;Server=192.168.1.50,1433;Encrypt=yes;TrustServerCertificate=yes; Use code with caution. 3. Test Outside Zabbix Using isql

USE master; GRANT VIEW SERVER STATE TO zbx_monitor; GRANT VIEW ANY DEFINITION TO zbx_monitor; ALTER SERVER ROLE [sysadmin] ADD MEMBER [zbx_monitor]; -- Optional for full access

You are staring at your Zabbix dashboard, and the dreaded red indicator has appeared. The trigger message reads:

It outputs an explicit error message (e.g., "Login failed", "Connection refused") which points directly to the problem. Testing ODBC Connections: