GVFOG-54

Fixed issue where some dashboards, copyright, and URL addresses have not been rebrand to Quest Software Inc.

GVFOG-50

Fixed issue where DB Groups Grid in the DB Global View could not be restored after disabling or upgrading the previous Global View cartridge.

GVFOG-33

Updated the Supported Foglight Version number on the Databases > Administration dashboard.

Out of Memory occurred when clicking an instance to access the Overview dashboard.

The "An error has occurred. Please check your logs." error showed on the Databases > Overview dashboard.

Clicking Version\Collation on the Overview dashboard leads to the previous Real Time page.

SQL PI Statistics debug messages were disabled by default.

Fixed issue where the Up_since metric could not be synchronized from FMS Child to FMS Master.

Removed the Time Range settings from the Set Input Parameters step for Index Fragmentation Report.

Failed to add Reporting Services using a custom ReportServer name.

The "Callback failure: no result received from callback" error was randomly occurred when setting up DB agent the first time.

Fixed issue where there was no databases popped up in the Specify Databases for Exclusion dialog box.

Fixed issue where inconsistency was occurred between disk latency metric and graph on SQL Server instance overview.

Removed redundant permission file from the Management Server module.

Fixed the performance issue occurred when importing a large number of AD groups into the Management Server 5.7.5.7.

Excluding database moves all databases that contain the name of database being selected.

An error was occurred on the Alarms > Settings dashboard if the agent name contains slash.

Fixed issue where systemID collection was disabled by the IC agent created using the DB wizard.

DBSS - Long Running Job alarm will not be triggered on SQL Server 2008.

The "Failed to invoke agent callback" error prompted when setting up the SQL Server Agent.

SSFOG-444

Fixed issue where EXECUTE permission was denied on the object 'agent_datetime'.

SSFOG-558

The Timeout error occurs when enabling OS monitoring in the Management Server 5.7.1.

Workaround: Upgrade the Management Server to 5.7.5 or later.

SSFOG-551

The following metrics are missing on the Databases > Temdb dashboard: data files, log files, and disk space.

SSFOG-442

Anti virus applications block the SPM installer.

SSFOG-502

History data is missing if user upgrades the Foglight for SQL Server cartridge 5.7.5.37 using the SPM installer.

SSFOG-561

PI extension cannot be enabled for DB agents that are deployed on mixed environments (Linux® and Windows®).

Workaround: Use the same version of DLP for both Linux and Windows environments. See the Knowledge Article 215534 for details.

SSFOG-520

DB agents need be re-upgraded after upgrading the Foglight Management Server.

Workaround: Make sure to wait for more than 10 minutes between upgrade of the Foglight Management Server and Foglight for SQL Server.

SSDB-16097

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 available at
https://support.quest.com/kb/215054.

SSDB-16092

When PI is enabled, Microsoft Visual C++ 2010 Redistributable Package needs to be installed on Foglight Management Server and Foglight Agent Manager. It can be downloaded from here: https://www.microsoft.com/en-US/Download/confirmation.aspx?id=14632.

n/a

In case of mixed environments (Linux® and Windows®), upgrading Foglight for SQL Server to the latest version causes the agent monitored by SQL PI with SQL PI repository on Linux to stop monitoring.

n/a

Monitoring Analysis services is supported only on Agent Managers running on Windows which must have a version of .NET 3.5 or higher installed.

n/a

If the WMI exception "Format specifier '%s' " is entered in agent log the following workarounds are recommended:

• Use WinRM which of course avoid the wmi issue

• Verify that enough permission are granted to WMI: https://support.quest.com/kb/90733

SSDB-15192

SQL BI - Reporting services, integration services and Analysis services are not supported on cluster configuration.

n/a

In cases when Foglight or the Agent Manager are installed on a VM the following need to be reserved:

• Memory - the full amount of the required machine memory

• CPU - the amount of CPU MHz

SSDB-14323

The SQL Server Error log collection requires you to use WinShell. Follow the instructions below to configure the correct settings:

• Configuring the Command-Shell Connection Settings

• Configuring Windows Management Instrumentation

SSDB-13479

In environments configured to use Agent Manager in High Availability mode the chosen Agent Manager hosting the SQL PI repository will host watchdog and maintenance agents that cannot participate in the Agent Manager high availability utility.

SSDB-13199

Selecting a batch text in the lock tree may navigate to a non-equal batch in the TSQL Batches dimension.

SSDB-9277

In SQL Server® 2012, when a database is part of an availability group and is currently accessible for connections, when the application intent is set to read only, several collections will fail.

SSDB-9138

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
GO
--To update the currently configured value for advanced options.
RECONFIGURE
GO
—- To enable the feature.
EXEC sp_configure ‘xp_cmdshell’, 1
GO
—- To update the currently configured value for this feature.
RECONFIGURE
GO

SSDB-8987, SSDB-7326

On Microsoft® Windows® 2008 R2, a SQL Server version 2012 instance with a name that contains inverted commas (''; (for example:'X641_ENT1') can encounter issues with the retrieval of WMI data. This is by design on the part of Microsoft.

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

SSDB-8949

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.

SSDB-8826

A Foglight Agent Manager (FglAM) residing on a Linux/UNIX machine cannot use Windows Remote Management (WinRM) to establish a connection with a Windows server. Connection using WinRM can only be carried out by a Foglight Agent Manager (FglAM) residing on a Windows machine.

SSDB-8388

In an environment that includes a Foglight Agent Manager concentrator, when upgrading the environment where the concentrator does not contain any regular agents, the concentrator is not upgraded. Therefore, after the upgrade process takes place the Foglight Agent Manager concentrator has to be deployed manually.

SSDB-7866

When running the agent installation wizard on a monitored host whose OS version is Windows 2008 R2, the OS validation fails.

Workaround: review the following knowledge base article: https://support.quest.com/kb/SOL63439

SSDB-7241, WCF-12907

Currently users can create a recursive service, which calls itself and thereby causes an endless loop. If a user creates such a service the Databases dashboard will not be displayed.

SSDB-7090

Reuse and copy of user-defined collections is only possible for collections that were created after the 5.6.4 version of the product was installed.

SSDB-7059

The reports wizard contains multiple "all reports" tabs. Each tab is for a different database type.

SSDB-3045

In a Federation environment, deleted agents are still displayed in the Global View > Databases  table.

SSDB-3061

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.

SSDB-3039

The DBSS- Deadlock Details alarm is disabled by default.

SSDB-2455

User-defined collection names and fields must be entered in Latin characters (A to Z), without any special symbols.

SSDB-2379

When working with Global View while the screen resolution is set to 1024 by 768 pixels, it is advisable to switch to the browser's full view (F11 toggles between full and normal views in all browsers).

SSDB-2060

On SQL Server 2008, deadlocks on two different databases of the same instance become one chained deadlock.

Workaround: Implement trace flag -T1234

SSDB-5248

Editing a user-defined collection results in periodic overlap of data.

SSDB-5542

Creating a user-defined collection with more than one SQL in it will not alert the user, however, only the first SQL in the collection will be executed.

ODB-2984

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.

ODB-2829

When running user-defined collections on dynamic tables, deleted items are still kept in the topology. As a result, the number of rows displayed on the user-defined collections table will exceed the configured value for maximum allowed rows.

ODB-1606

Performing an upgrade process on a large environment (more than 50 agents) takes time to complete.

SSDB-10920

row_count metric is supported from SQL Server version 10.50.2500 and above

n/a

In the Execution Plan comparison popup, the date of the selected plan is the insert time to the SQL PI repository and not the execution time.

SSDB-11283

Execution plan may not be resolved

SSDB-11657

Time range changes are not effecting the execution plan dashboard.

n/a

In the Execution Plan Comparison popup for statement - the estimated plan appears only as the selected plan on the left side. It cannot be selected from the list.

SSDB-11582

Sometimes, query_hash is changed by SQL Server and generating a plan using the Generate button fails. SQLhash isn't found in XML so the screen displays No operation was found and the execution plan changes are missing.

n/a

Anti-Virus Protection tools installed on Windows® may negatively impact CPU and system performance of machines running Foglight the Agent Manager and the SQL PI repository.
To reduce resource consumption it is highly recommended that you exclude the following directories from being scanned by the Anti-Virus tools:

• <installation directory>:\Dell\<foglight>

• <installation directory>:\Infobright

• <installation directory>:\Dell\<FoglightAgentManager>

n/a

WMI-related issue

Problem: WMI support is affected by the firewall

Workaround: For Windows versions prior to Windows 2008/Vista, use the following steps:

1. Open TCP port: 135.
   WMI by default uses the port range 1024 to 5000.
2. Open up a range of ports above port 5000.
   Port numbers below 5000 may already be in use by other applications and could cause conflicts with your DCOM applications. It is recommended to have at least 100 ports opened, as several system services rely on these RPC ports to communicate with each other.
3. Add the registry key, including additional ports.
   • Use the RPCCfg.exe (Windows Resource Kits) by running: rpccfg.exe -pe 5009-5009 -d 0
   • Manually add the registry keys under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet

For Windows Vista® and Windows Server 2008:

According to Microsoft® http://support.microsoft.com/kb/929851, the default dynamic port range for TCP/IP has changed in these versions. The new default start port is 49152 and end port is 65535.

Subsequently, monitoring instances that run under these operation systems can be carried out by using either of the following options:

• Configure the firewalls to allow traffic between servers in the dynamic port range of 49152 through 65535 (less secure).
• Limit the port range that is used in each monitored server.

n/a

As a result of the change introduced in Java 6 update 29 to how data is sent to databases, users may experience connection failures when using the Microsoft JDBC Driver for SQL Server® to connect to SQL Server. This interoperability enhancement is available in the following SQL Server versions:

• SQL Server 2012 Production version and later
• SQL Server 2008 Service Pack 3 Cumulative Update 4
• SQL Server 2008R2 Service Pack 1 Cumulative Update 6
• SQL Server 2008R2 Service Pack 2

n/a

Third Party Limitations

Monitoring an SQL Server instance that resides on a Windows 2008R2 requires a workaround as follows:

1. Browse to https://support.quest.com/ and log in
2. Perform solution https://support.quest.com/kb/SOL65870

n/a

Some base values are not updated when using the Win32_PerfRawData_PerfDisk_LogicalDisk WMI class to calculate performance data in Windows Vista or in Windows Server 2008, because this class does not contain the PercentDiskTime_Base metric.

Workaround: A hotfix is available on Microsoft site, http://support.microsoft.com/kb/961435/en-us.

n/a

Due to a known Microsoft issue (https://support.microsoft.com/en-us/kb/3036328), on SQL Server instances version 2014 the SQL text presented may be truncated.

n/a

The Windows System Center 2012 Endpoint Protection tool may negatively impact CPU and system performance of machines running Foglight and the Agent Manager. To reduce resource consumption it is highly recommended that you exclude the following directories from being scanned by the tool:

• c:\Dell\<foglight>
• c:\Infobright
• c:\Dell\<FoglightAgentManager>

n/a

SQL's and execution plans may not be collected on SQL Server 2014 as a result of a Microsoft bug "

"The values of column query_hash and query_plan_hash are NULL for DMV sys.dm_exec_requests in SQL Server 2014"  http://support.microsoft.com/kb/2953592

n/a

The Foglight Time Bar Chart click event does not work with Chrome version 40.x.x.x and 39.x.x.x. https://code.google.com/p/chromium/issues/detail?id=428308

Foglight Management Server

5.7.0 or later

All platforms supported by this version of the Foglight Management Server

Foglight Agent Manager

Note: The monitoring agents available in this version of Foglight for SQL Server support the Agent Manager HA failover mode, except for the Agent Manager monitoring SQL PI agents. For more information about this mode, see the Agent Manager Guide.

5.8.0 or later

All platforms supported by this version of the Foglight Agent Manager