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

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

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

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 failure in the communication link between the Zabbix Agent (or Server) and the SQL Server instance zabbix mssql failed to fetch info data -or no data for 30m-

If you tell me you are using (Windows or Linux) for the Zabbix Agent, I can give you the specific configuration files to check. If you'd like, let me know: Are you using ODBC or Agent2 ? Is it a standalone SQL server or AlwaysOn AG ? Are other metrics working?

Are you using the or Zabbix Agent 2 for this monitoring setup?

USE master; CREATE LOGIN zbx_monitor WITH PASSWORD = 'YourStrongPassword'; CREATE USER zbx_monitor FOR LOGIN zbx_monitor; Problem: MSSQL: Failed to fetch info data (or

The "Failed to fetch info data" error typically originates from the or MSSQL by DB for Windows templates. It indicates that the Zabbix agent or proxy successfully initiated a connection to the server port, but failed to execute the internal discovery queries or retrieve performance counter data. The most common reasons for this failure include:

For a database administrator or a monitoring engineer, this is a high-priority alert. It implies that Zabbix has lost visibility into your SQL Server instance. Is the database down? Is the network blocked? Or is it just a permissions hiccup?

By following these troubleshooting guides, you should be able to resolve the "Failed to fetch info data" or "No data for 30m" errors and ensure that your MSSQL database is being monitored correctly by Zabbix. Is it a standalone SQL server or AlwaysOn AG

This specific error in typically triggers when the monitoring system hasn't received any data from the MSSQL instance for a prolonged period (30 minutes), often due to ODBC configuration issues or insufficient permissions for the monitoring user . Alert Message Draft

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

The Zabbix monitoring user requires specific permissions to access system views and performance counters. If these are missing, the query that fetches "info data" will fail. Ensure the monitoring user has these permissions: SERVER STATE [zabbix_user]; DEFINITION [zabbix_user]; -- For SQL Agent jobs monitoring: dbo.sysjobs [zabbix_user]; dbo.sysjobactivity [zabbix_user]; dbo.agent_datetime [zabbix_user]; Use code with caution. Copied to clipboard 2. ODBC Driver Configuration (Zabbix Server/Proxy)

Performance counters are fragile (localization, missing objects). For critical metrics, use db.odbc.select with custom T-SQL.

: Test the connection manually from the command line on the Zabbix server or proxy using isql or sqlcmd to rule out Zabbix-specific issues: isql -v