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

Zabbix timeout settings being too low for heavy database queries. Misconfigured ODBC drivers or odbc.ini profiles. Step 1: Verify Authentication and Credentials

The "Failed to fetch info data" and "No data for 30m" errors in Zabbix's MSSQL monitoring can be frustrating, but by understanding the possible causes and following the troubleshooting steps outlined in this article, you should be able to resolve these issues. Remember to regularly review your monitoring configurations, test database connections, and monitor Zabbix agent logs to prevent these errors from occurring in the future. If you're still experiencing issues, don't hesitate to reach out to Zabbix's support community or a qualified IT professional for assistance.

zabbix_get -s <TARGET_IP> -k agent.ping

Run this query during failure window:

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

After a SQL Server failover, Zabbix stopped receiving data. Manual zabbix_get worked, but the server showed “no data for 30m”.

On the host macro level, set:

Do use sa or sysadmin – it’s a security risk and often blocked by compliance.

If manual fails, the issue is OS/ODBC layer. Zabbix timeout settings being too low for heavy

Set DebugLevel=4 in zabbix_agentd.conf . Restart the agent, then reproduce the issue. Look for lines containing odbc , sql , or UserParameter .