Troubleshooting - Metasys - LIT-12011202 - Software Application - Metasys Database Manager - 13.0

Metasys Database Manager Help

Brand
Metasys
Product name
Metasys Database Manager
Document type
User Guide
Document number
LIT-12011202
Version
13.0
Revision date
2023-08-14
Product status
Active
Language
English

Use Table 1 to troubleshoot the Metasys Database Manager.

Table 1. Metasys Database Manager Troubleshooting

Problem

Condition

The Metasys Database Manager Monitoring Settings window appears every time you restart the ADS, ADX, OAS, NAE85, or LCS85.

If you do not enter values in the Email section of the Monitoring Settings window, the window appears every time the ADS, ADX, OAS, NAE85, or LCS85 restarts.

To prevent the Monitoring Settings window from reappearing:

  1. In the Email section of the Monitoring Settings window (Figure 1), enter the correct information into the appropriate fields. If you do not want to use the Email feature, enter at least three characters in the SMTP Server field and in at least one address field.
  2. Click OK.

You experience one or more of the following:

  • You cannot view all of the tabs.
  • You cannot access monitoring settings.

This problem occurs when you do not have sufficient access rights to use the Metasys Database Manager. See Required access rights.

Metasys Database Manager does not start, or the icon appears red, indicating an alarm state. Other users may log in to the same computer and not experience issues.

In some scenarios, only users without Windows administrator privileges experience these issues.

If you experience this scenario, try the following:

  1. Log in to the Windows OS as a user with administrator privileges (not as a Standard user).
  2. Right-click the Metasys Database Manager icon and then click Exit.
  3. Using Windows Explorer, browse to the following location:C:\ProgramData\Johnson Controls\MetasysIII\MDM
  4. Delete the following files:
    1. JCIAuditTrails.txt
    2. JCIEvents.txt
    3. JCIHistorianDB.txt
    4. JCIItemAnnotation.txt
  5. Do not restart the Metasys Database Manager. Log out of the OS.
  6. Log in to the Windows OS as a user who does not have administrative privileges (as a Standard user).

If the icon is still red, the Users group in the Windows OS may not have public access to the Metasys databases. In this scenario, do the following:

  1. Using Add/Remove programs, uninstall the Metasys Database Manager.
  2. Reinstall the Metasys Database Manager.

Instead of granting the entire Users group public access to the Metasys databases, you may prefer to grant access only to some Windows users. If this is the case, grant public access to the Metasys databases.

When a user logs on to their Windows computer, the following error message appears:

Metasys Database Manager. Status: Alarm. There was an error connecting to the target database. JCIHistorianDB. Metasys Database Manager Monitor.

Change the permissions on the MDM folder and the files it contains, complete the following steps:

  1. Navigate to C:\ProgramData\Johnson Controls\MetasysIII.
  2. In the MetasysIII folder, right-click the MDM folder, and click Properties.
  3. Click the Security tab, and click Edit.
  4. In the Group or user names area, click Users.
  5. In the Permissions for Users area, in the Full control entry, select Allow.
  6. Click Apply.

A Database Error box appears:

At least one database cannot be found. Make sure your Metasys software has been installed properly and that SQL Server service is running.

This error message appears if a timeout occurs when the Metasys Database Manager attempts to connect to the database. For example, the timeout may occur if the computer is busy executing a virus scan.

This message also appears if the user credentials used to connect to the SQL Server database do not have read access to the databases. See Taskbar icon and Database login.

The Current Database Server Connections field reads 0.

This may indicate that there are no connections to the SQL Server software.

This field reads 0 if the Windows user account does not have Administrator privileges.

While you monitor databases, a message appears indicating that one or more databases have exceeded their allowed size. However, you know the database size is less than the alarm limit.

This message may appear if your SQL Server software access credentials do not give you read access to the databases.

When you purge a database, the database size seems to increase.

The log file may increase during a purge. The Metasys Database Manager is working properly.

After you restart a computer that has Metasys Database Manager installed, the icon in the Windows system tray is red.

If the Metasys Database Manager comes online faster than one of the managed SQL Server databases and cannot connect to the managed database to determine the database size, the Metasys Database Manager tray icon turns red, indicating an alarm condition. As the size of the SQL Server databases increases, the databases require more time to come online, increasing the likelihood of encountering this alarm condition. Although the SQL Server database size may suddenly seem too large, the real cause of the alarm condition may be that the Metasys Database Manager has not yet established connections to the SQL Server databases.

The Metasys Database Manager connects with the SQL Server and other associated databases at user-specified time intervals. By the time of the next scheduled connection, the SQL Server database completes the startup, the databases are online, and the Metasys Database Manager icon turns green.

It is very unlikely that the SQL Server database has exceeded the size limits during this time. A user who is concerned about this possibility can restart Metasys Database Manager immediately.

When the databases have finished coming online, the Metasys Database Manager icon turns green. Until the databases have finished coming online, the Metasys Database Manager icon remains red. If the icon remains red after a restart, wait a few minutes to allow the databases to finish coming online, and restart the Metasys Database Manager.

You accidentally restore a database over an existing database.

If this occurs, you can restore the original database. The Metasys Database Manager created a backup of the original database before it was overwritten.

Automatic backups are stored in the Metasys Database directory at C:\ProgramData\Johnson Controls\MetasysIII\SQLData.

Backups use the following naming convention:

[yymmdd]FromRestore[databasename].bak

For example: 090605FromRestoreJCIHistorian.bak

To restore the original database, use the standard Metasys Database Manager restoration procedure in Restoring a database.

Metasys Database Manager does not start, or the icon appears red, indicating an alarm state. Other users may log in to the same computer and not experience issues.

Update the folder permissions on C:\ProgramData\Johnson Controls\MetasysIII\MDM to allow the Users group to write to the directory.