Zabbix Mssql Failed To | Fetch Info Data -or No Data For 30m- [2021]

The "Failed to fetch info data" or "no data for 30m" error in Zabbix for MSSQL typically indicates a connectivity or permission issue between your Zabbix server/proxy and the SQL instance. 🛠️ Quick Troubleshooting Checklist

7. The SQL Browser Service is Stopped (For Named Instances)

Zabbix’s ODBC DSN often uses Server=localhost\INSTANCE. This requires SQL Browser (UDP port 1434) to resolve the dynamic port. If SQL Browser is disabled, the connection hangs then fails. zabbix mssql failed to fetch info data -or no data for 30m-

"Waiting for what?"

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." The "Failed to fetch info data" or "no

ALTER INDEX ALL ON transactions REBUILD; Verify that there are no network connectivity issues

MSSQL: Failed to fetch info data (or no data for 30m) - suggestions * Posts. * Latest Activity. * Photos.

Part 3: Step-by-Step Diagnosis (From Zabbix Server to SQL)

When the error strikes, follow this A→Z workflow.

Step 5: Check Network Connectivity

1. Verify that there are no network connectivity issues between Zabbix and the MSSQL database server.
2. Check the firewall rules and ensure that they allow communication between Zabbix and the MSSQL database.