The monitoring user lacks sufficient permissions (e.g., sysadmin or specific VIEW SERVER STATE rights).
This issue typically stems from connectivity, configuration, or authentication problems between the monitoring agent and the SQL Server: mssql: failed to fetch info data (or no data for 30m)
Ensure the correct ODBC Driver (e.g., Driver 17 or 18) is installed on the agent. The monitoring user lacks sufficient permissions (e
The error message “MSSQL: failed to fetch info data (or no data for 30m)” typically appears in monitoring systems, ETL pipelines, or application logs when a client attempts to retrieve metadata, status, or time‑series information from a Microsoft SQL Server instance but receives no response within a 30‑minute timeout window. This paper outlines the common root causes, diagnostic steps, and preventive measures. This paper outlines the common root causes, diagnostic
If this is a one-time event, it was likely a temporary network glitch or a momentary resource spike. If it is persistent, it is likely a firewall block or a permission issue with the monitoring user.
Thanks for the question and using MS Q&A platform. * I have encountered a similar issue and found that the error "Failed to fetch" Microsoft Learn Resolving no data error for MSSQL performance metrics If you encounter 'The user does not have permission to perform this action' message while running the query, then update the permi... PitStop ManageEngine Troubleshooting DBM Setup for SQL Server - Datadog Docs Check the TCP connection from the agent to the host by running telnet host port to make sure there is network connectivity fro... Datadog Docs MSSQL: Failed to fetch info data (or no data for 30m) - ZABBIX Forums Jun 16, 2022 —
If using , verify that the mssql.conf plugin file is correctly configured and included in the main agent configuration. Check for these specific macros in the Zabbix frontend: