Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- __full__ Review
Move mssql.conf out of the subfolder directory directly into C:\Program Files\Zabbix Agent 2\zabbix_agent2.d\ .
This article will guide you through the root causes and provide actionable steps to resolve this issue in modern Zabbix versions (6.0+). Understanding the Error
Note: If using the MSSQL plugin directly, you can also look for Plugins.MSSQL.Timeout=15 inside the configuration file. For Zabbix Server or Proxy:
: For the default instance, use MSSQLServer . For named instances, use MSSQL$InstanceName .
Or increase the time to 2 hours and rely on other liveness checks.
Then from (as the Zabbix agent service account):
Update your connection string or the host's $MSSQL.ODBC.STR macro to explicitly trust the target database certificate:
: For ODBC, this must match the name defined in your /etc/odbc.ini file. 2. Check Database Permissions
: Ensure the monitoring user has VIEW SERVER STATE and VIEW ANY DEFINITION permissions.
Zabbix templates rely on user-defined macros to adapt to different environments. The most frequent configuration errors involve the $MSSQL.INSTANCE macro. If this macro is set incorrectly, the JSONPath queries used to extract data from the performance counters will fail because they will be looking for the wrong instance name. This typically results in "Preprocessing failed" errors for dependent items, as the data exists but Zabbix cannot find it using the provided path.
: Verify you have installed the zabbix-agent2-plugin-mssql package or the equivalent Windows plugin. 5. Debugging "No Data"
