Mssql: Failed To Fetch Info Data - (or No Data For 30m) Work

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

Verify credentials in your Zabbix macros (e.g., $MSSQL.USER and $MSSQL.PASSWORD ) or your ODBC connection string . 3. Fix Performance Counters (Perfmon)

# Example test using sqlcmd sqlcmd -S -U -P -Q "SELECT @@VERSION" Use code with caution. mssql: failed to fetch info data (or no data for 30m)

The monitoring user lacks sufficient permissions (e.g., sysadmin or specific VIEW SERVER STATE rights).

Ensure TCP/IP is enabled in the SQL Server Configuration Manager under "Protocols for [Instance Name]". Problem: MSSQL: Failed to fetch info data (or

If you see "SSL Provider: certificate verify failed," you may need to set TrustServerCertificate=yes in your connection settings.

Confirm that the MSSQL instance is accessible on its assigned TCP port (default 1433) using tools like telnet or test-netconnection . The monitoring user lacks sufficient permissions (e

The most basic cause is a service interruption or blocked communication path.

Analysis and Mitigation of “MSSQL: Failed to Fetch Info Data (or No Data for 30m)”

MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix Comment * Joined: Nov 2020. * Posts: 7.

Ensure no firewalls are blocking communication between the monitoring server and the database. 2. Validate Monitoring User Permissions

Начните вводить чтобы увидеть результаты.
Корзина