Agents are shown as Active in Agent Status but do not appear in the Global View Databases Dashboard.
Database agents are missing and are not displayed in the Global View databases dashboard.
The message "There is no data to display" is displayed in the databases dashboard.
No database agents are seen in the databases dashboard.
In some instances the databases dashboard may appear like one of the following two images
An error similar to the following may appear in the FMS log
dbwc.scripts.loadGVData - Failed to create MSSQL data for agent id . error: Cannot get property 'nt_version' on null object"
The most common reason for an agent not to function as expected is topology duplication.
In this scenario, the agent was probably created more than once.
For example, the user has created the agent by using the database agent installer and then deleted the agent using the Agent Status panel and created it again by filling in Agent Status Properties (ASP) in the Agent Status page.
If not properly deleted from the topology, the agent will maintain two topologies:
Note that The Topologies are created in the FMS process and agent is running on the FglAM process. That explains why the agent is marked in green in Agent Status, while there is a failure on the FMS side.
Another reason for the agent to be shown as active in Agent Status and not shown in Databases Dashboard can be related to NTLM2, Microsoft security protocol.
A database group was created and is being viewed without the specified database being included.
There are mixed cartridge versions enabled, which are not compatible, either after a manual administrative change or after an FMS or Cartridge upgrade. You cannot mix cartridge component versions.
A FMS is rebooted after a license has expired causing some cartridges to be only partially enabled.
DBSS_Version_Info collection was not enabled (for SQL Server)
Best practices would be to create the agents from the agent installer wized only.
The database agent installer wizard will run validation checkup before allowing agent creation which may prevent agents duplications.
If an agent is green in Agent Status and is not shown in Databases Dashboard , suspect topology duplication.
Next step would be to delete the topology for the agent in the proper way:
Please pay attention that the agent deletion from Agent Status is NOT required in a duplicate topology scenario.
Edited the Database Groups, and put in the selected section, they were in the available section.
Enable the corresponding cartridge files at the same version level (for example, the DBSS_SQL_Server and DBSS_SQL Server_UI should be at the same cartridge level. The latest DB_Global_View_UI cartridge should also be enabled.
Best practice is for all of the database cartridges to be at the highest version and to match (as close as possible) the DB_Global_View_UI version. The highest DB_Global_View_UI cartridge should always be enabled to maintain optimal support for all database cartridge versions.
If the system is has a hotfix for the DB_Global_View_UI dashboard, please contact Support to provide a revised hotfix for this issue.
Apply the new replacement Foglight license and restart the FMS.
Enable the DBSS_Version_Info collection (for SQL Server)