Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- [patched] -

This failure usually cascades, causing all dependent items (like CPU usage, buffer cache hit ratio, and table sizes) to stop receiving updates, eventually triggering the "No data for 30m" alert. The most common culprits include: Expired or incorrect SQL Server authentication credentials. The Zabbix user lacking required permissions in MSSQL. Network firewalls blocking TCP port 1433.

<item name="MSSQL: Info fetch status" key="mssql.info.fetch.status"> <type>Zabbix agent</type> <key>perf.ms sql[fetch.status]</key> <value_type>Numeric (unsigned)</value_type> <units>status</units> <delay>60s</delay> <description>1 = fetch failed, 0 = fetch successful</description> </item>

Increase the Timeout parameter in zabbix_server.conf or zabbix_proxy.conf to a higher value (e.g., 10s or 30s).

Use this checklist to systematically eliminate the error: zabbix mssql failed to fetch info data -or no data for 30m-

Zabbix requires explicit permissions to query system dynamic management views (DMVs) and the msdb database. Lacking these permissions will cause the master item query to fail entirely, triggering the "no data" alert.

Increased QueryTimeout from 5 to 30 seconds in Zabbix item configuration and scheduled backup outside peak monitoring.

Before diagnosing Zabbix, you must confirm that the ODBC layer works. This failure usually cascades, causing all dependent items

Example:

PiotrJ. Junior Member. Joined: May 2023. Posts: 26. Problem: MSSQL: Failed to fetch info data (or no data for 30m) 21-09-2023, 19:

The "MSSQL: Failed to fetch info data (or no data for 30m)" error is usually not a bug but a symptom of a missing dependency, misconfiguration, or permission issue. By systematically verifying the ODBC layer, the SQL Server permissions, the Zabbix macros, and the timeout settings, you can quickly restore full monitoring functionality. Regular testing using manual tools like isql and reviewing the Zabbix logs are the most effective ways to diagnose and prevent this error from recurring. Network firewalls blocking TCP port 1433

Two weeks ago, they had disabled the weekly index rebuild on the transactions table to speed up a different report. They had forgotten to re-enable it. The indexes had fragmented into digital gravel. A simple count query now took the server hostage.

Typically C:\Program Files\Zabbix Agent\zabbix_agentd.log (Windows) or /var/log/zabbix/zabbix_agent2.log (Linux).