[ Zabbix Server / Proxy ] │ ▼ (Connection Attempt) ┌────────────────────────────────────────────────────────┐ │ Common Failure Points: │ │ 1. Missing View Server State Permissions │ │ 2. Broken FreeTDS/unixODBC Driver Strings │ │ 3. TLS / Self-Signed Certificate Rejections │ │ 4. Agent 2 mssql.conf Plugin Misplacement │ └────────────────────────────────────────────────────────┘ │ ▼ [ Target MSSQL Database ] ──❌ Data Flow Blocked Method 1: Troubleshooting ODBC Monitored Environments

Common triggers:

if [ $? -eq 0 ]; then echo 0 # Success else echo 1 # Failed fi

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 .

“Failed to fetch info data from database.”

In your Zabbix server, add a log item:

If any returns empty, debug before production.

She called Tom, the database admin. "Hey, look at your SQL server. Zabbix is blind."

The Network Operations Center hummed its usual lullaby of cooling fans and low conversation. On the wall, a massive screen displayed a constellation of green dots—each one a server, a service, a heartbeat. In the center of that constellation, glowing a steady, reassuring emerald, was .

recovery_expression: | last(/MSSQL_Template/ms.sql.fetch_success)=1 and min(/MSSQL_Template/ms.sql.fetch_success, 5m)=1

If using a named instance, set the $MSSQL.INSTANCE macro correctly (e.g., MSSQL$INSTANCE ). 4. Root Cause: High Load or Timeout

Increase Timeout=30 in zabbix_agentd.conf and restart the agent. Also add ODBCPoolSize=50 if using ODBC pooling.

Encountering the "failed to fetch info data (or no data for 30m)" error can be frustrating, but it is highly diagnostic. It is almost always caused by one of the fundamental components in the data chain: connectivity, permissions, configuration, or a known software bug.

Several known issues in specific Zabbix versions can cause this error. Check the Zabbix Jira project for issues matching your version: