PI engine didn't use new credential changed in Connection Details dashboard. Workaround: Reactive the agent after changing the credential. | |||||||
Cannot use cluster server or AlwaysOn listener to monitor AlwaysOn environment on FIPS-enabled FMS. Workaround: Refer to KB 324797 for detailed information. | |||||||
Workaround: Click Cancel on Update SQL PI Failed and click Update SQL PI Components to update again. | |||||||
After DB agent restarts, there will be a 5 minutes data gap in the SQL PI baseline view. | |||||||
Workaround: Use hostname\username to setup PI Repository instead of only using username. | |||||||
“Context infos” display null in the Comparison Parameter dashboard. | |||||||
An error log showed in FMS log for loading heatmap component in FMS version before 5.9.3. | |||||||
Workaround: Contact Quest support to get the scripts for updating the loadGVData function. | |||||||
Due to the metric collection interval, value of Data files, log files, and disk space metrics will be occasionally missing on the Databases > Temdb dashboard. Workaround: Wait for 3 minutes, then you will see these metrics on the dashboard. | |||||||
It fails to run DBSSSQLAgentErrorLogProcessor processor of DBSS_SQL_Agent_Error_Log collection if the SQL Server Agent Service is not started. Workaround: Start the SQL Server Agent Service. | |||||||
DBSS_Error_Log_List collection fails if SQL Server 2017 Agent is not running on Linux. | |||||||
Logical Disk metrics of SUSE showing on the SQL Server Overview dashboard is different from its value showing in the Infrastructure dashboard. | |||||||
Alarm is not triggered while the error has been collected on the DBSS - SQL Server Error Log page. | |||||||
If AD authentication has been used to monitor SQL Server instance, the default option 'Log in to the host using the same account used for monitoring SQL Server' cannot be used to monitor Linux Operating System (OS). Workaround: Switch to use the option 'Log in to the host using different login credentials', then choose either of the following Linux authentication types: input AD account info, input other Linux account info, or use 'Select from stored credentials...'. | |||||||
Workaround: Either activate those host agents manually on the Agent Status dashboard or re-create those host agents. | |||||||
When monitoring SQL Server 2017 on Linux, an error message will be shown in Logs > SQL Agent Error Logs page. | |||||||
If you select either of DB_SQL_Server, DB_SQL_Server_UI, DB_Global_View_UI, SPIRepository* cartridges then click Reset on the Cartridge Inventory dashboard, the upgrade wizard will prompt again. Workaround: Do the following:
| |||||||
In the Master server of the federation environment, the values in Message of back up alarm are null. | |||||||
Databases Replication Dashboard does not show all Subscriptions when using multiple distribution databases. | |||||||
Failed to monitor SQL Server 2005 on premise while using no required permission DB credential. Workaround: Download the DB_SQL_Server_Grant_Permission_Script from Components for Download, execute the script at SQL Server client to grant permission to the new user, then use the new user to monitor SQL Server 2005 Instance. | |||||||
When the VMwarePerformance Agent exists, the Disk Latency in SQL Server Overview would always show “-” while enabling OS monitoring. | |||||||
Workaround: Implement trace flag -T1234. | |||||||
The DBSS- Deadlock Details alarm is disabled by default. | |||||||
Changes made in the Global Administrations > Alarms screen are saved when switching to another global administration screen, even if selecting “Yes” in the dialog box that asks whether to exit without saving changes. | |||||||
Editing a user-defined collection results in periodic overlap of data. | |||||||
When editing the properties of the Foglight Agent Manager concentrator (Dashboards > Administration > Agents > Agent Status), the name of the Foglight Agent Managers should be entered in the Downstream FglAMs section exactly as they appear in the topology, under Home > Agents > All agents > <Agent name> > RMI data > FglAM host property. | |||||||
Workaround: If WMI data is not retrieved, the instance name without the '' should be added in the field Service Name in the Agent Properties dashboard. | |||||||
Cluster data can be collected only if the xp_cmdshell parameter is configured. To configure this parameter, run the following commands: EXEC sp_configure ‘show advanced options’,1 --To update the currently configured value for advanced options. EXEC sp_configure ‘xp_cmdshell’, 1 —- To update the currently configured value for this feature. | |||||||
In case the privilege of OS monitoring is not set to the Local Administrator group on the host being monitored, see the Knowledge Article 215054. | |||||||
Performing an upgrade process on a large environment (more than 50 agents) takes time to complete. | |||||||
In the Global Administration > User-defined Collections screen, it is possible to create two collections that bear the same name with a different capitalization (for example: MyCollection and Mycollection); however, the more recently created collection will not appear in the topology, nor will it be displayed on the User-defined Collections panel. | |||||||
Workaround: In the Administration > Agents > Agent Status dashboard, click Deploy Agent Package, then follow on-screen instructions to deploy the SSAS package manually. | |||||||
If the WMI exception “Format specifier '%s' “ is entered in agent log the following workaround is recommended: For Windows® Vista® and Windows Server 2008 or above: According to http://support.microsoft.com/kb/929851, the default dynamic port range for TCP/IP has changed in both versions. The new default start port is 49152 and end port is 65535. Subsequently, monitoring instances that run under these operating systems can be carried out by setting a static (fixed) WMI port in Windows Server. | |||||||
| |||||||
Antivirus exclusions is required for the SQL Server-based SQL PI repository. For more information refer to the Microsoft’s official article https://support.microsoft.com/en-us/help/309422/choosing-antivirus-software-for-computers-that-run-sql-server. |
Time range changes are not affecting the execution plan dashboard. | |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center