Not able to connect to SQL Database - fg_freeSpace_with_avail_disk statement has been terminated
search cancel

Not able to connect to SQL Database - fg_freeSpace_with_avail_disk statement has been terminated

book

Article ID: 138180

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

We are getting the error below while connecting to the MS SQL Server Database from UIM but when trying to test the database connection it is successful.

sqlserver:Profile: xxx\xxxx105002_profile/fg_freeSpace_with_avail_disk/Run Query - DB Provider: Code=0x0x80040e14 Source=Microsoft OLE DB Provider for ODBC Drivers Description=[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been terminated.

Environment

  • Release : 8.51
  • Component: UIM - SQLSERVER

Cause

- sqlserver probe configuration

Resolution

Use the latest GA version, 5.42.

http://support.nimsoft.com/Files/Archive/00089/sqlserver-5.42.zip

fg_freeSpace_with_avail_disk

Required permissions are documented here:

MS SQL Server Access Prerequisites

Monitors the amount of free disk space in database file groups in %. Free space for file groups (with auto growth enabled) is calculated after considering the available disk size on which the file group is located. Notes:

A single query is executed for all the databases of the SQL server. If ANY of the database fails to execute the query, the query is considered as failed for the SQL server.

***You require System Administrator privileges on the database server to execute this checkpoint.***

In case the query reaches the SQL timeout, the checkpoint processing will be terminated and the next checkpoint will be started.

How to Increase the MS SQL Remote Query Timeout?

  • Connect to MS SQL server via SQL Management Studio

  • In Object Explorer, right-click on the server name and then select Properties

  • In the new tab, click on Connections node

  • In Remote Query Timeout change it to your desired value or specify 0 to set no limit

  • Click on OK to save the changes