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

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

This troubleshooting guide explores why this error occurs across both and Zabbix Agent 2 monitoring methods, along with exact strategies to resolve it. Root Causes of the Error

Navigate to your MSSQL host in . Verify the following macros are defined at the host level:

When the error strikes, follow this A→Z workflow. zabbix mssql failed to fetch info data -or no data for 30m-

USE master; GRANT VIEW SERVER STATE TO [zabbix_user]; GRANT VIEW ANY DEFINITION TO [zabbix_user]; USE msdb; GRANT SELECT ON sysjobs TO [zabbix_user]; GRANT SELECT ON sysjobservers TO [zabbix_user]; GRANT SELECT ON sysjobactivity TO [zabbix_user]; ``` ### 3. Check Zabbix Macros Ensure the following **Macros** are set correctly on the Host level in the Zabbix frontend: * `$MSSQL.DSN`: The name used in your Linux `odbc.ini`. * `$MSSQL.USER` / `$MSSQL.PASSWORD`: Valid SQL credentials (note: some drivers fail if these contain special characters like `@` or `$`). 💡 **Pro Tip:** Check the **Zabbix Server logs** (`tail -f /var/log/zabbix/zabbix_server.log`) while the error is active. It will often give you the specific ODBC error code, such as `[08001]` for network issues or `[28000]` for login failures. --- If you'd like, let me know: * Which **Zabbix version** are you using? * Are you using the **ODBC template** or **Agent 2**? * What **OS** is your Zabbix server running on? I can help you pinpoint the exact configuration file line to change. Use code with caution. Copied to clipboard Zabbix 7.0 MSSQL ODBC Connection

After fixing the issue once, document the exact DSN, login permissions, and UserParameter overrides in your runbook. The next time SQL Server patches or a failover occurs, you’ll recover in minutes – not days.

The template uses macros to securely store connection information. Navigate to your host's configuration page and set the "Macros" tab. You must define the following, as the official documentation dictates: Problem: MSSQL: Failed to fetch info data (or

If your SQL Server instance uses a non-default port, specify it after a comma in the Server line, like Server = 192.168.1.100, 14330 .

When the "no data for 30m" message appears, it means that the master item — usually responsible for calling a discovery rule or running an SQL query (like SELECT * FROM sys.dm_os_performance_counters ) — has failed to execute successfully or return data. The trigger fires after 30 minutes of no new data. Host status becomes "Red" or "Unsupported" for MSSQL items. Graphs show gaps. 1. Root Cause: Insufficient SQL Permissions (Most Common)

Log into the machine running Zabbix Agent 2 and run the zabbix_agent2 binary with the test flag: USE master; GRANT VIEW SERVER STATE TO [zabbix_user];

Verify the time on the Zabbix Server, Proxy, and MSSQL server are synchronized (check NTP settings).

If you are using the , the Zabbix server or proxy must have the correct ODBC drivers installed and configured. Steps to Fix:

: If you can connect via sqlcmd but not Zabbix, you may need to specify TrustServerCertificate=Yes in your odbc.ini file or ensure the Microsoft ODBC Driver 18 is properly handling encryption. Database Permissions

To resolve this issue efficiently, it helps to understand why the master item stops retrieving data. The problem typically falls into one of four categories: