• Overview

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

The "MSSQL: Failed to fetch info data (or no data for 30m)" alert in Zabbix is a common trigger indicating that the master item used to gather SQL Server metrics—either via Zabbix Agent 2 —is failing to return results Common Root Causes & Fixes Missing or Incorrect Permissions

: The monitoring user must have specific rights to view server state and access the . Use the following T-SQL to grant required permissions: GRANT VIEW SERVER STATE TO [zabbix_user] VIEW SERVER PERFORMANCE STATE for SQL 2022+) GRANT VIEW ANY DEFINITION TO [zabbix_user] Read access to msdb.dbo.sysjobs msdb.dbo.sysjobservers msdb.dbo.sysjobactivity Zabbix Git repository ODBC Configuration Issues (ODBC Template) Port Formatting

: Microsoft SQL Server typically uses a comma for the port (e.g., Server = 192.168.1.10,1433 ) rather than a colon Trust Server Certificate

: If you are using a self-signed certificate, you may need to add TrustServerCertificate=Yes or use the flag if testing with $MSSQL.USER $MSSQL.PASSWORD

are set at the host level, as credentials stored directly in often fail to work with Zabbix Zabbix Git repository Zabbix Agent 2 Configuration Plugin Config Location mssql.conf

file is often placed in a subdirectory that Agent 2 doesn't read by default . Move it to the zabbix_agent2.d directory or ensure your zabbix_agent2.conf includes a path to it (e.g., Include=./zabbix_agent2.d/plugins.d/*.conf Restart Required

: Any change to the plugin configuration or the agent requires a full service restart to apply Encryption and Driver Version Modern drivers (like ODBC Driver 18) default to Encrypt=yes

. If your server isn't configured for it, connection attempts will fail Check for driver-specific errors in the Zabbix Server or Proxy logs

to identify network-related or instance-specific connection failures Troubleshooting Steps

Problem: MSSQL: Failed to fetch info data (or no data for 30m)

The error message "MSSQL: Failed to fetch info data (or no data for 30m)" typically indicates a communication failure between the Zabbix agent/server and the target SQL Server instance. This usually results from incorrect connection settings, missing ODBC drivers, or insufficient database permissions. Immediate Troubleshooting Steps

Check Connection Parameters: Verify that your macros or DSN settings are correct.

Server/Port: Ensure the address is set as ipaddress,1433 (use a comma instead of a colon for SQL Server ports). zabbix mssql failed to fetch info data -or no data for 30m-

Trust Certificate: If using newer ODBC drivers (v18+), encryption is often forced. Try adding TrustServerCertificate=yes or Encrypt=yes to your connection string or odbc.ini file.

Verify ODBC Driver Connectivity: Test the connection manually from the command line on the Zabbix server or proxy using isql or sqlcmd to rule out Zabbix-specific issues: isql -v

Confirm Database Permissions: The monitoring user requires specific rights to fetch performance data. Run these commands on your SQL Server:

GRANT VIEW SERVER STATE TO zabbix; (or VIEW SERVER PERFORMANCE STATE for SQL 2022). GRANT VIEW ANY DEFINITION TO zabbix;.

Zabbix Agent 2 Plugin Configuration: If you are using the MSSQL by Zabbix agent 2 template, ensure the plugin configuration file (mssql.conf) is in the correct directory (typically zabbix_agent2.d/plugins.d/) and that the agent has been restarted. Common Fixes from the Community

Username/Password Storage: Users on the Zabbix Forum suggest passing credentials as arguments from the Zabbix frontend rather than storing them in odbc.ini.

Preprocessing Issues: Check if the template's JSONPath preprocessing is failing due to spaces in counter names. For example, change Buffercachehitratio to Buffer cache hit ratio if the raw data includes spaces.

Zabbix Agent 2 Sessions: In mssql.conf, define your connection sessions clearly: Plugins.MSSQL.Sessions..Uri=sqlserver://:1433.

Are you using the ODBC template or Zabbix Agent 2 for this monitoring setup?

Problem: MSSQL: Failed to fetch info data (or no data for 30m)

PiotrJ. Junior Member. Joined: May 2023. Posts: 26. Problem: MSSQL: Failed to fetch info data (or no data for 30m) 21-09-2023, 19:

MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix The "MSSQL: Failed to fetch info data (or

ybcnyc. Junior Member. Joined: Jun 2022. Posts: 1. MSSQL monitoring - MSSQL: Failed to fetch info data (or no data for 30m) 16-06-

MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix

ybcnyc. Junior Member. Joined: Jun 2022. Posts: 1. MSSQL monitoring - MSSQL: Failed to fetch info data (or no data for 30m) 16-06- Microsoft SQL monitoring and integration with Zabbix

The error "MSSQL: Failed to fetch info data (or no data for 30m)" is a common trigger in Zabbix, signaling that the master item responsible for gathering server metrics is failing to retrieve or process information. This generally occurs when using the "MSSQL by ODBC" or "MSSQL by Zabbix agent 2" templates. Core Causes of the "No Data" Alert

When this trigger fires, the monitoring chain is broken at one of three levels: Authentication, Connectivity, or Configuration.

Insufficient Permissions: The monitoring user must have specific rights to query system views like sys.dm_os_performance_counters. Without VIEW SERVER STATE (or VIEW SERVER PERFORMANCE STATE for SQL 2022+), the "Get Info" queries return empty results.

ODBC Configuration Errors: If using the ODBC template, the Data Source Name (DSN) must be correctly defined in odbc.ini on the Zabbix server/proxy and match the $MSSQL.DSN macro in Zabbix.

Agent 2 Plugin Issues: When using Zabbix Agent 2, the mssql.conf plugin file must be present in the plugins.d directory, and the agent must be restarted to load it.

Network/Port Blocking: The SQL Server must be reachable over TCP port 1433 (or your custom port) from the Zabbix server/proxy or agent. Step-by-Step Troubleshooting Guide 1. Verify MSSQL Permissions

Ensure your Zabbix monitoring user (e.g., zbx_monitor) has the necessary permissions. Run these T-SQL commands on the target SQL Server: Zabbixhttps://www.zabbix.com Microsoft SQL monitoring and integration with Zabbix

This review focuses on the common Zabbix alert: "MSSQL: Failed to fetch info data (or no data for 30m)."

This is a generic trigger often seen when using the "MSSQL by ODBC" or "MSSQL by Zabbix agent 2" templates. It indicates that the master "Info" item—which discovery and other dependent items rely on—is not receiving data. Core Causes & Fixes 1. Database Permissions (Most Common) Troubleshooting Steps 5

The Zabbix monitoring user requires specific permissions to access system views and performance counters. If these are missing, the query that fetches "info data" will fail. Ensure the monitoring user has these permissions: SERVER STATE [zabbix_user]; DEFINITION [zabbix_user]; -- For SQL Agent jobs monitoring: dbo.sysjobs [zabbix_user]; dbo.sysjobactivity [zabbix_user]; dbo.agent_datetime [zabbix_user]; Use code with caution. Copied to clipboard 2. ODBC Driver Configuration (Zabbix Server/Proxy)

MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix

MSSQL: Failed to fetch info data (or no data for 30m) - suggestions * Posts. * Latest Activity. * Photos. Microsoft SQL monitoring and integration with Zabbix

Introduction

Zabbix is a popular monitoring tool used to track the performance and health of various systems, including Microsoft SQL Server (MSSQL) databases. However, sometimes Zabbix may encounter issues while monitoring MSSQL databases, resulting in errors such as "failed to fetch info data" or "no data for 30m". This guide aims to provide a step-by-step approach to troubleshooting these issues.

Possible Causes

Before diving into the troubleshooting steps, it's essential to understand the possible causes of these errors:

  1. Incorrect configuration: Incorrect or incomplete configuration of the Zabbix MSSQL monitoring setup.
  2. Connectivity issues: Issues with the network connectivity between the Zabbix server and the MSSQL database.
  3. MSSQL configuration: Incorrect configuration of the MSSQL database, such as disabled SQL Server Agent or incorrect permissions.
  4. Zabbix agent issues: Issues with the Zabbix agent running on the MSSQL server.

Troubleshooting Steps

5. Resolution Strategies

Abstract

Zabbix is a widely used open-source monitoring solution. When monitoring Microsoft SQL Server (MSSQL) instances via Zabbix agent items or ODBC queries, administrators frequently encounter two critical alerts: "Failed to fetch info data" and "No data for 30 minutes." These errors indicate a breakdown in data collection, leading to monitoring gaps and potential blind spots for database health. This paper analyzes the root causes, diagnostic methodologies, and resolution strategies for these specific Zabbix-MSSQL integration failures.

White Paper: Troubleshooting "No Data" for MSSQL Monitoring in Zabbix

Subject: Resolving "Failed to fetch info data" and "No data for 30m" errors for Microsoft SQL Server. Audience: System Administrators, DevOps Engineers, DBAs.

3.4 Network & Agent Intermittency (No data for 30m)

1. Introduction

Effective database monitoring requires consistent, timely metric collection. Zabbix typically collects MSSQL performance counters (e.g., buffer cache hit ratio, page life expectancy, blocking processes) using:

When Zabbix triggers "Failed to fetch info data" or "No data for 30m", the root cause is rarely the same. The former suggests an authentication or query execution failure; the latter suggests timeouts, deadlocks, or connectivity intermittency.

Step 4 – Monitor MSSQL Side

Run this query during failure window:

SELECT 
    session_id, 
    login_name, 
    status, 
    last_request_start_time, 
    last_request_end_time,
    text
FROM sys.dm_exec_sessions s
OUTER APPLY sys.dm_exec_sql_text(most_recent_sql_handle) t
WHERE login_name = 'zabbix_user';

Look for status = 'suspended' (blocked) or running for hours.

Step 3: Investigate MSSQL Server Configuration

  1. Check the MSSQL server configuration and ensure that it's running and accepting connections.
  2. Verify that the database and login credentials used by Zabbix have the necessary permissions.
  3. Check the SQL Server error log for any issues or errors related to the Zabbix connection.