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

When using the "MSSQL by Zabbix agent 2" template, a faulty or missing plugin will prevent any data from being collected. Additionally, a known bug (ZBX-27040) causes the Agent 2 service to crash under specific versions when the MSSQL and Oracle templates are used together. Another issue involves a misconfigured URI macro "localhost," which can force the agent to query the wrong instance.

: This file defines the available ODBC drivers. Create or edit it to include your Microsoft ODBC Driver:

On the SQL Server, open → System DSN → Create a test DSN pointing to your instance.

Let's walk through a systematic approach to identify and resolve your issue. Follow these steps in order, verifying each component before moving to the next. zabbix mssql failed to fetch info data -or no data for 30m-

If this alert is active, check the following common causes identified by users in the Zabbix Community Forums :

If you use a non-standard port or a named instance, ensure the correct port is defined. Use telnet or nc from the Zabbix server to test connectivity:

"MSSQL: Failed to fetch info data (or no data for 30m)" typically indicates a communication or permission breakdown between Zabbix and your SQL Server When using the "MSSQL by Zabbix agent 2"

: In mssql.conf , define your connection sessions clearly: Plugins.MSSQL.Sessions. .Uri=sqlserver:// :1433 .

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

: If the SQL instance is under heavy load, the info fetch might timeout. Try increasing the parameter in the Zabbix server/agent configuration files. Detect Issues in Your Zabbix Instance Before It's Too Late 25 Mar 2026 — : This file defines the available ODBC drivers

: Check if the template's JSONPath preprocessing is failing due to spaces in counter names. For example, change Buffercachehitratio to Buffer cache hit ratio if the raw data includes spaces.

. This is most often caused by incorrect credentials, missing ODBC drivers, or misconfigured connection parameters. Common Causes and Solutions Missing or Misconfigured ODBC Driver