Zabbix Mssql Failed To Fetch Info | Data -or No Data For 30m- 2021
Navigate to your MSSQL host in . Verify the following macros are defined at the host level:
If the SQL service is running, the issue might be between the Zabbix Server and the Agent on the SQL host.
Create a dedicated SQL Server login specifically for Zabbix. Avoid using the sa account for security and auditing reasons. Open SQL Server Management Studio (SSMS) and run the following T-SQL script, replacing zbx_monitor and YourStrongPassword with your chosen username and password:
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. zabbix mssql failed to fetch info data -or no data for 30m-
Ensure the file sits directly in /etc/zabbix/zabbix_agent2.d/ .
: If using ODBC Driver 18, it defaults to encrypted connections. If you don't use SSL, add TrustServerCertificate=yes to your connection string or use Encrypt=no . 3. Validate ODBC Connectivity
Set the global plugin timeout using:
If you are using the , the Zabbix server or proxy must have the correct ODBC drivers installed and configured. Steps to Fix:
Look for status = 'suspended' (blocked) or running for hours.
Additionally, if the template uses the msdb database, grant specific permissions: Navigate to your MSSQL host in
Increased QueryTimeout from 5 to 30 seconds in Zabbix item configuration and scheduled backup outside peak monitoring.
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
. This is most often caused by incorrect credentials, missing ODBC drivers, or misconfigured connection parameters. Common Causes and Solutions Missing or Misconfigured ODBC Driver Avoid using the sa account for security and auditing reasons
Look for an entry like ODBC Driver 18 for SQL Server or similar. If missing, install the msodbcsql package from Microsoft.