Issues tables
Review the following tables for issues that were corrected in PATROL for Microsoft SQL Server 9.6 and for known issues that remain open.
Description | Fixed in | Found in | Defect ID |
|---|---|---|---|
Enabling SQL KM debug logs displays the password in clear text. | 9.6.41 | 9.6.40 | DRPKS-856 |
The 'SQL agent job failures' (getFailedJobs) parameter does not collect the failed jobs data due to the following error: | 9.6.41 | 9.6.40 | DRPKS-817 |
After the agent restarts, there is a delay in collecting the data for the SpaceUsedPCT parameter and the SpaceUsedPCT spike. | 9.6.41 | 9.6.40 | DRPKS-823 |
Microsoft SQL Server KM shows the wrong status for MSSQL Agent Service. | 9.6.41 | 9.6.40 | DRPKS-760 |
For PATROL Agent 20.08 and later, monitors under the devices are not discovered. | 9.6.40 | 9.6.30 | DRPKS-712 |
When you enable the Generate Detailed Events check box, only old failed jobs are considered for generating events. | 9.6.40 | 9.6.30 | DRPKS-752 |
When you update the Perfmon monitoring level from Most Important to Custom, the discovered perfmon objects are shown directly under the PATROL Agent on the Devices page. | 9.6.31 | 9.6.30 | DRPKS-704 |
When the monitoring of the Always-On feature fails, the Monitoring Status parameter still shows OK. | 9.6.30 | 9.6.00, 9.6.10, 9.6.11, 9.6.12, 9.6.20 | DRPKS-639 |
The configuration of Custom SQL Query by using the PATROL Console is not working properly. | 9.6.30 | 9.6.00, 9.6.10, 9.6.11, 9.6.12, 9.6.20 | DRPKS-636 |
In a local monitoring environment, when the database data or the log file is located on a mounted drive, the Space Used Percentage parameter sometimes shows a wrong value. | 9.6.30 | 9.6.00, 9.6.10, 9.6.11, 9.6.12, 9.6.20 | DRPKS-635 |
The Number of Blocking Processes parameter displays the number of blocked processes instead of the number of blocking processes. | 9.6.30 | 9.6.00, 9.6.10, 9.6.11, 9.6.12, 9.6.20 | DRPKS-632 (QM002298546) |
From the PATROL Console, the Perfmon exclude filter is not working correctly. | 9.6.30 | 9.6.00, 9.6.10, 9.6.11, 9.6.12, 9.6.20 | DRPKS-631 (QM002315447) |
When you have configured remote monitoring and restart the SQL server computer, the monitoring fails. | 9.6.30 | 9.6.00, 9.6.10, 9.6.11, 9.6.12, 9.6.20 | DRPKS-630 (QM002327690) |
The failed job is not detected when the job run duration is greater than the data collection interval. | 9.6.30 | 9.6.00, 9.6.10, 9.6.11, 9.6.12, 9.6.20 | DRPKS-629 |
The Mirroring HA parameter, Witness Server Status, shows an incorrect value. | 9.6.30 | 9.6.00, 9.6.10, 9.6.11, 9.6.12, 9.6.20 | DRPKS-628 |
The KM failed to monitor if the PATROL Agent default account password contains an ampersand (&). | 9.6.30 | 9.6.00, 9.6.10, 9.6.11, 9.6.12, 9.6.20 | DRPKS-627 |
The KM might stop monitoring unexpectedly if an infrastructure policy is disabled and then enabled or when the connection with TrueSight Infrastructure Management is disconnected and connected again. | 9.6.30 | 9.6.00, 9.6.10, 9.6.11, 9.6.12, 9.6.20 | DRPKS-614 |
Space Used Percentage parameters might show wrong value when database data/log file is located on a mounted drive. | 9.6.20 | 9.6.00 | QM002213947 |
The Long Running Transaction parameter doesn't detect long-running transactions when it is in idle mode. | 9.6.20 | 9.6.00 | QM002196734 |
TrueSight gives the wrong IP address (0.0.0.0) for Microsoft SQL Server device when the Instance to Device feature is enabled. | 9.6.20 | 9.6.00 | QM002173392 |
The parameters SQL Agent Hung Jobs and SQL Agent Job Failures do not detect jobs in case a job is owned by a user with no login account. | 9.6.20 | 9.6.00 | QM002165802 |
Perfmon Custom filtering feature doesn't work with TrueSight 10.5 | 9.6.20 | 9.6.00 | PSQL-580 |
In BMC PATROL for Microsoft SQL server, the XTP perfmon catalogs might not be monitored on SQL Server 2016. | 9.6.12 | 9.6.10 | PSQL-576 |
Icons were not available in the left pane of the PATROL Classic Console in version 9.6.00 of Microsoft SQL Server KM. | 9.6.11 | 9.6.00 | QM001889454 |
Time-based parameters and custom SQL queries could not be configured when a host name was in FQDN format. This issue was seen when the time-based parameters and custom SQL queries were configured by using PATROL KM menu commands. | 9.6.11 | 9.6.00 | QM001890739 |
In BMC PATROL for Microsoft SQL Server, the LongRunningTrans parameter displayed an incorrect value intermittently. | 9.6.11 | 9.6.00 | QM001891570 |
The Custom SQL query menu command did not support the equal (=) character. | 9.6.11 | 9.6.10 | QM001950251 |
In BMC PATROL for Microsoft SQL Server, the ParameterCount parameter displayed an incorrect value intermittently. | 9.6.11 | 9.6.10 | QM001896218 |
In BMC PATROL for Microsoft SQL server, when the PATROL_HOME environment variable contains a path with spaces, KM failed to monitor. | 9.6.10 | 9.6.00 | QM001878701 |
The SQLAgentHungJobs parameter displayed an incorrect value intermittently. | 9.6.10 | 9.6.00 | QM001891478 |
The ListenerState parameter displayed incorrect values when multiple IP addresses and/or IP Subnet masks were configured on the listener. | 9.6.10 | 4.5.10 | QM001878861 |
Always On collection did not work as expected when the listener had multiple IP addresses and/or IP Subnet masks. | 9.6.10 | 9.6.00 | QM001880275 |
The KM did not monitor clustered SQL instances as expected. | 9.6.10 | 9.6.00 | QM001880889 |
The KM failed to perform local monitoring if a user did not have Log on locally rights. | 9.6.10 | 9.6.00 | QM001880893 |
If an earlier version of the KM uses PATROL Agent default Account credentials as the monitoring user, an upgrade might use incorrect credentials. | 9.6.10 | 9.6.00 | QM001881197 |
The SpaceUsedPCT and SpaceAvailableMB parameters of the MSSQL_SERVER_DB_SPACE_FILE application class did not work as expected at the Filegroup and Database level. | 9.6.10 | 9.6.00 | QM001881909 |
The KM did not support multi-language. | 9.6.10 | 4.5.00 | QM001717072 |
The Role parameter of the MSSQL_SERVER_AON_AVAILABILITY_REPLICA application class might display an incorrect value. | 9.6.10 | 9.5.00 | QM001878768 |
Menu commands used to set the following collection intervals did not work as expected.
| 9.6.10 | 9.6.00 | QM001880428 |
While configuring the KM, if the Windows User field was left blank, the KM did not use the PATROL Agent defaultAccount user credentials for connection and discovery. | 9.6.10 | 9.6.00 | QM001881198 |
When the KM was loaded, No discovery program error was recorded in the PATROL error log file for all Always-On application classes. | 9.6.10 | 4.5.10 | QM001882051 |
In the KM, to align with the Microsoft view parameters, the following parameters must remain offline on Secondary replicas:
| 9.6.10 | 9.6.00 | QM001882969 |
The KM failed to detect a failover on a virtual PATROL Agent that was installed on the monitored cluster SQL instance environment. | 9.6.10 | 9.6.00 | QM001883071 |
Step_id and step_name information were missing from the annotations displayed by the SQLAgentJobFailures parameter. | 9.6.10 | 9.6.00 | QM001885923 |
The SQLAgentStatus parameter displayed an incorrect value when the service was running in cluster mode. | 9.6.10 | 9.6.00 | QM001890342 |
BMC PATROL for Microsoft SQL Server 9.6.00 could not be uploaded to the Distribution Server because of the dependency on the PPF files. | 9.6.10 | 9.6.00 | QM001876129 |
If the macro $Hostname was set as DOMAIN_NAME or if no DOMAIN_NAME was entered, the KM did not use the host name as the DOMAIN_NAME. In 9.6.10, the KM uses the host name as the DOMAIN_NAME if the macro $Hostname is set as DOMAIN_NAME or if no DOMAIN_NAME is entered. | 9.6.10 | 9.6.00 | QM001881199 |
The KM was not aligned with the Microsoft view of Always On Secondary availability groups. | 9.6.10 | 9.6.00 | QM001882971 |