Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- đź’Ż

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

tester777. Junior Member. Joined: Aug 2020. Posts: 9. #1. MSSQL: Failed to fetch info data (or no data for 30m) - suggestions. 18-

Common triggers:

Connect to your SQL Server instance via SQL Server Management Studio (SSMS) and execute the following script to grant the necessary rights to your Zabbix login: zabbix mssql failed to fetch info data -or no data for 30m-

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.

: Verify that your macros or DSN settings are correct.

Open your mssql.conf file and define your connection parameters using named sessions. This prevents you from exposing cleartext passwords across global macros: Increase the Timeout parameter in zabbix_server

Then from (as the Zabbix agent service account):

If using Microsoft ODBC Driver 18 for Linux/Windows, encryption is on by default, leading to certificate failures if not configured correctly.

Log into the machine running Zabbix Agent 2 and run the zabbix_agent2 binary with the test flag: Joined: Aug 2020

The most effective way to resolve this "no data" error is to use in your configuration. This bypasses common connection issues by explicitly defining the URI and credentials in the plugin configuration.

If using the ODBC template, the Data Source Name (DSN) must be correctly defined in odbc.ini on the Zabbix server/proxy and match the $MSSQL.DSN macro in Zabbix.