The Geo SCADA Expert database has a primary measure of performance, the total database lock time. This time is a percentage value, and is used to measure how busy the server is when performing data read, calculations, and fulfilling client requests.

The lock statistics are shown in detail in other pages of the Server Status tool: on the General/Locks page and the Database/Lock Diagnostics Read and Lock Diagnostics Write pages. They are also recorded in the Geo SCADA Expert Server Snapshot Log Files.

Geo SCADA Expert also monitors a single metric each minute - the 'Database Lock Usage' statistic. This measures the overall database read and write lock usage per minute. This value is compared against two alarm thresholds and will raise (text/one-shot) alarms whenever the thresholds are exceeded.

This warning message indicates that the 'Database Lock Usage' statistic has exceeded a configured threshold. The threshold levels can be adjusted from the defaults if required (see Specify the Total Lock Time per Minute Alarm).

With Geo SCADA Expert 2021 onwards, you can opt to enable Database Emulation when you upgrade the version of Geo SCADA Expert that is running on your servers (see Database Emulation Configuration). This can prove a useful temporary stage while you run checks to ensure that the upgrade has been successful. While Database Emulation is enabled, the database files continue to be saved in the same format as the version of database that was running on the servers just prior to the upgrade. This provides a smoother downgrade path, if you decide to downgrade following the upgrade.

Once checks that been made to ensure that the upgrade is successful, you should disable the Database Emulation (see Disable Database Emulation after a Successful Upgrade). This enables Geo SCADA Expert to provide access to the database items and properties that are only available from the version of software to which your servers have been upgraded. To accommodate this, the database files are then stored in the format that applies to the upgraded version of the software.

The Emulating Database Version warning message indicates that Database Emulation is currently enabled on this particular server. It displays the version of Geo SCADA Expert software that is currently being emulated. This comprises the version of Geo SCADA Expert that the server was running just prior to the upgrade.

The message is removed once Database Emulation has been deactivated. Once this has happened, the database files get saved in the format that applies to the version of Geo SCADA Expert software to which the server was upgraded. (Details about the upgrade version are shown in the Version entry that appears at the top of the Information category.)

For more information, see Types of Emulation Supported by Geo SCADA Expert.

The 'Everyone' User Group is a built-in User Group. Every User Account that is created on your system is automatically associated with the 'Everyone' User Group and automatically inherits the access and permissions that are assigned to that User Group. This includes the Guest User Account (a built-in User Account) that can be used to access the database from various clients without logging on.

On new installations, the 'Everyone' User Group and the Guest User Account are inactive and not assigned any security permissions by default.

This warning message indicates that the 'Everyone' User Group is enabled on your system and is configured to provide all User Accounts with some form of access to the whole database (from the 'Root' Group onwards). If the Guest User Account is also enabled, this means that users will also have some form of access to the whole database without logging on. We strongly recommend that you remove any security permissions from, and then deactivate the 'Everyone' User Group and Guest User Account. Instead, 'configured' User Groups and User Accounts should be used to provide the relevant levels of access to the database.

If the 'Everyone' User Group has to be used, it MUST be assigned the minimum permissions required, with access restricted where possible to just the relevant parts of the database.

For more information, see Guest User Account and Everyone User Group, and see Allocating Security Permissions.

You can enable an Exception Dumps feature on each server. When enabled, the server generates diagnostic files (in the form of minidumps) if there is an exception (application error).

This warning message indicates that the Exception Dumps feature is enabled on this server, and that the feature is configured to generate a 'Full' exception dump file. This setting can result in very large but comprehensive dump files that take a long time to generate. We strongly recommend that 'Normal' exception dump files are configured (rather than 'Full' exception dump files). You should only set the Dump Type to 'Full' if instructed to do so by Schneider Electric. Regardless of the option chosen, ensure that the minidump files are set to be written to a suitable partition that has sufficient disk space and does not impact on the space used for other files.

For more information, see Enable or Disable Exception Dumps, and see Define the Server Logging Settings.

This warning message indicates that Geo SCADA Expert has made an unsuccessful attempt to access the main server log file. This message is displayed only if an issue occurs when attempting to access the database log file for the main server (rather than other diagnostic log files such as server snapshot and exception log files).

The warning message indicates the reason for the issue (such as 'Access is Denied') and the resulting action by Geo SCADA Expert (such as 'LOGGING SUSPENDED'). If a log file fails to open, Geo SCADA Expert will retry to open the log file when a new line is to be logged. Providing that the retry is successful, logging will then resume. With such a situation, the log file will include a 'LOGGING RESUMED...' entry. This indicates that some log file data might be missing in between the previously logged entry and this statement.

For more information, see Log Files.

The Super User account is a special user account that has access to all Geo SCADA Expert features and database items. The Super User account is created when Geo SCADA Expert is first installed, to enable administrators to set up the system security and create custom 'configured' administrator-level User Accounts. Thereafter, the Super User account should be disabled to help prevent unrestricted high-level access to all areas of the system.

This warning message indicates that the Super User account is still enabled on your system. We strongly recommend that you ensure that suitably configured custom administrator-level User Accounts exist on your system, and that you should then seriously consider disabling the Super User account.

For more information, see Super User Account, and see Disable the Super User Account.

By default, when you upgrade the version of Geo SCADA Expert software that is running on your Geo SCADA Expert server, an automatic backup is made of your database. The files are stored in a format that corresponds to the version of Geo SCADA Expert software that was running on the server just before the upgrade. If you decide that you want to roll back the Geo SCADA Expert software following the upgrade, you can downgrade back to that previous version of software and restore the backed-up database.

This warning message indicates that the feature to generate an automatic database backup on upgrade is disabled. Therefore an automatic backup of your database will not be made if you upgrade the Geo SCADA Expert software on this particular server machine. You should consider reinstating the automatic backup feature before the next software upgrade.

For more information, see Automatic Database Backup on Upgrade, and see Disable Automatic Database Backups on Upgrade.

You can enable a Database Watchdog feature on each server. When enabled, the feature detects whether the server has 'frozen' (whereby excessive system loading or an error has caused the server to go into an invalid state).

This warning message indicates that the Database Watchdog feature is enabled on this server, and that the feature is configured to generate a 'Full' watchdog dump file. This setting can result in very large but comprehensive dump files that take a long time to generate. We strongly recommend that 'Normal' watchdog dump files are configured (rather than 'Full' watchdog dump files). You should only set the Dump Type to 'Full' if instructed to do so by Schneider Electric. Regardless of the option chosen, ensure that the minidump files are set up to be written to a suitable partition that has sufficient disk space and does not impact on the space required for other files. If Geo SCADA Expert is unable to create a dump file due to lack of space, it will delete the partially created file.

For more information, see Configure the Database Watchdog Settings.

This warning message relates to Original WebX.

As Original WebX clients connect to your system via the network, extra security measures are required; these include the use of certificates to encrypt client-server communications.

This warning message indicates that a weak certificate is being used for the Web server. We strongly recommend that your Web security settings are tightened to use a secure key algorithm and a private key length of at least 2048 bits.

For more information, see Define the Certificate Settings for Original WebX Clients, and see Using a Trusted Certificate from a Certification Authority.

This warning message relates to Original WebX.

The message indicates that the specified port is currently configured for use by the web server, however Geo SCADA Expert has detected that the specified port is already in use by another service or application. To assist with its identification, the message indicates the port number and whether it is configured as the HTTP or HTTPS port.

If such a message is displayed, you should:

1. Determine which application is currently using the configured port and, if the port is unneeded based on the usage of that application, reconfigure or unassign that port number.

2. If the existing port allocation cannot be changed, then change the web server configuration to use a different port number. If you change the HTTP port, then ensure that you change the port number both in the Server Configuration Tool and the IIS Manager application.

3. Repeat the changes on any other servers in your system as required.