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

Look for an entry like ODBC Driver 18 for SQL Server or similar. If missing, install the msodbcsql package from Microsoft.

This comprehensive guide will help you understand, troubleshoot, and resolve this issue. Troubleshooting Zabbix MSSQL Failed to Fetch Info Data 1. Understanding the Error

[MyMSSQL_DSN] Driver = FreeTDS Servername = MyMSSQLServer zabbix mssql failed to fetch info data -or no data for 30m-

If the port is open, you must also double-check that the DSN in /etc/odbc.ini points to the correct port.

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: Look for an entry like ODBC Driver 18

Map the explicit instance prefix to the matching host macro. Phase 1: Verify SQL Server Access & Permissions

You’ve configured Zabbix to monitor your critical Microsoft SQL Server instances. The templates are applied, the user macro is set, and for a few hours, everything looks perfect. Then, without warning, your dashboard turns grey. The dreaded error appears: Troubleshooting Zabbix MSSQL Failed to Fetch Info Data 1

For cleaner approach, use dependent items:

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?

: Zabbix needs to read from the msdb database for job status:%%MAGIT_PARSER_PROTECT%% sql USE msdb; GRANT SELECT ON dbo.sysjobs TO zabbix; GRANT SELECT ON dbo.sysjobservers TO zabbix; GRANT SELECT ON dbo.sysjobactivity TO zabbix; GRANT EXECUTE ON dbo.agent_datetime TO zabbix; %%MAGIT_PARSER_PROTECT%% 3. Agent 2 Plugin Configuration

The most frequent cause is a simple credential mismatch. Ensure your Host Macros are correctly set: : The SQL login name. $MSSQL.PASSWORD : The corresponding password.