When a node is in the Configuration Problem state one of the following class of problems has occurred:
| Configuration Problem | Definition |
|---|---|
| Standby connection rejected | Occurs on Standby, tried to connect to Main and standby denied request. |
| Configuration Unlicensed | A feature is unlicensed, see the License Details Window, available from the Server Icon. |
| Invalid Configuration | Standby has lost a connection to Main, but the standby is in an inconsistent state (for example, it was in the process of synchronizing) |
| Integrity Check Failed | Periodic database health check has detected an issue. |
| Database Load Errors | Problem reading database file on start-up. |
| Missing Database modules | Driver modules required for the database are not installed. |
| Invalid Database |
The database file is unsupported or is corrupt. Check that the build version of the database file is supported by your version of Geo SCADA Expert. You will need to start a partner to restore the configuration. If that is not possible, contact Schneider Electric for assistance. |
| Database File Errors | The database cannot start because a fatal error was encountered with the database files. |
| Blank Database | The database has no configuration. To protect partners against potential loss of data the database has been placed in a safe mode |
|
Invalid Metadata |
Metadata defined in metadata.xml file is invalid (for example, clashing fields) |
| Exception Occurred | The server has entered an exception state. |
| Isolated Standby |
This server was standby, but is now isolated from the main server. It is in this state because it is configured to go into an 'Isolated Standby' state if it loses its connection to the main server |
| Invalid Standby Configuration |
Connection rejected when the database server has attempted to connect (as a standby server) to the main server.  WARNINGinability to synchronize databases and take over as main With Geo SCADA Expert 2020 onwards, take care to ensure that Main and Standby servers all have compatible Connection Security configuration and valid certificates. We recommend that you renew certificates well in advance of their expiry dates. If the Main server is unable to connect to a Standby server due to differences in TLS (Transport Layer Security) configuration, then the Standby server will appear to attempt to synchronize endlessly with the Main server. Should a changeover occur in this situation, the Standby server will not be able to become Main. This is because it will have an invalid database due to the synchronization not having completed. For more information, see Configure the Connection Security Settings, and see Connection Security Tab (for Server-to-Server Communications).
Failure to follow these instructions can result in death, serious injury, or equipment damage. If a changeover occurs with no Standby available to take over as Main, the system will be offline until a server with a valid database is brought back online.
|
| Database Save Error | Server has failed to save the database (for example, file locked, out of disk space) |
| Journal Save Error |
Event journal has failed to save to disk (for example, file locked, out of disk space) |
|
Database and Journal Save Error |
A combination of the above items. |
More detail information can be obtained by selecting the node and then clicking on the Diagnose button.
Further Information
For more information about some of the above states, see The Server Icon.