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

This piece will trigger when:

| Layer | Common Causes | | :--- | :--- | | | Firewall rules blocking port 1433; network instability between Zabbix server and SQL Server; DNS resolution failure; dynamic ports being used on the SQL Server side. | | ODBC & Driver | Microsoft ODBC driver not installed on the Zabbix server/Proxy; incorrect ODBC DSN configuration in odbc.ini ; missing or incorrect library paths in odbcinst.ini ; FreeTDS/unixODBC configuration issues. | | Authentication & Permissions | Incorrect username/password in Zabbix host macros; missing or incorrect GRANT statements for the monitoring user on the SQL Server (e.g., VIEW SERVER STATE ); credentials stored in odbc.ini instead of Zabbix macros (a common mistake). | | Zabbix Configuration | Unconfigured or misspelled required host macros ( $MSSQL.DSN , $MSSQL.USER , $MSSQL.PASSWORD ); incorrect instance name for named instances in macros; missing StartODBCPollers setting in zabbix_server.conf . | | SQL Server Internal Issues | Incorrect instance name handling for performance counter queries; differences in naming between default and named instances leading to JSONPath preprocessing failures; SQL Server service downtime or heavy load causing timeouts. |

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

: Check that the path to the ODBC driver in /etc/odbcinst.ini is correct.

If the connection is successful, you should see a blank screen. zabbix mssql failed to fetch info data -or no data for 30m-

USE master; GO CREATE LOGIN [NT AUTHORITY\SYSTEM] FROM WINDOWS; GO GRANT VIEW SERVER STATE TO [NT AUTHORITY\SYSTEM]; GO

USE master; GO -- Grant view server state to allow reading performance counters GRANT VIEW SERVER STATE TO [your_zabbix_user]; GO -- Grant view any definition to see database structures GRANT VIEW ANY DEFINITION TO [your_zabbix_user]; GO -- Grant permissions to the msdb database for backup monitoring USE msdb; GO GRANT SELECT TO [your_zabbix_user]; GO Use code with caution. Step 3: Increase Zabbix Timeout Settings

isql -v <DSN> <USERNAME> <PASSWORD>

Tom pulled up his own tools. "It's up. CPU 12%. Memory fine. Locks… no deadlocks. Connections…" He paused. "Huh. I see the Zabbix proxy connected. But it's just… waiting." This piece will trigger when: | Layer |

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

$MSSQL.DSN : Ensure this matches the Data Source Name configured in your /etc/odbc.ini file. If you are using a DSN-less connection, leave this macro empty and rely on the connection string.

ybcnyc. Junior Member. Joined: Jun 2022. Posts: 1. MSSQL monitoring - MSSQL: Failed to fetch info data (or no data for 30m) 16-06- Microsoft SQL monitoring and integration with Zabbix

The second part of the trigger—"no data for 30m"—simply confirms that the item has stopped receiving data entirely, rather than just receiving a "zero" value. | | Zabbix Configuration | Unconfigured or misspelled

On your Zabbix server or proxy, install the necessary packages:

Note: If your scripts are downloaded from the internet, you may need to unblock them using Unblock-File .

Grant the necessary permissions to the Zabbix Agent service account.