The Server Icon
When you install ClearSCADA on a server and run it as a service, the server icon is displayed in the Windows taskbar. The appearance and color of the server icon depends on its state:
The server is running and is the Main server.
The Main server is running but is experiencing an excessive load on the database. This icon only appears for the Main server.
The server is shutting down.
The server is a Standby server and is in the process of synchronizing with the Main server.
The server is offline.
The server is a Standby server and has synchronized with the Main server.
The server is attempting to determine its status (it will then change to indicate whether it is Main, Standby, or has detected an error).
The server has detected an error.
If the server icon is magenta, you should investigate the cause of the detected error. Right-click on the server icon to display a context-sensitive menu. If the context-sensitive menu displays one of the following options:
Select the Start Database option.
A dialog box is displayed containing information about the error that has been detected:
If you are running a new database on a Main server and expect it to be empty, select the Start Database option on the dialog box to continue. If you are working on a Standby Server, you need to check that the Main server is running and is connected correctly before you select the Start Database option—if the Main server is not running, the Standby server will run with the empty database and will switch to Main. When the real Main server connects to the standby that is now Main, the real Main server will switch to Standby and the blank database will overwrite the real database. For this reason, only select the Start Database option on a Standby server if you are certain that the Main server is running and can connect to the Standby server correctly.
When you select the Start Database option, the server will run the empty database and you can access it via ViewX or WebX.
If you expect to run a database that contains database items, select the Stay in Safe Mode option and then check the name and location of your database files. To do this, display the latest log file for the server (see Display a Server Log File) and examine its contents. In the log file, it specifies the location in which the server looks for the database files (ClearSCADAData.dat or ClearSCADA.dat depending on your system build).
Use Windows Explorer to check that your database files are named correctly and are stored in the correct location (rename them or move them if they are incorrectly named or stored in the wrong location). You also need to check that the Windows SYSTEM user has sufficient security permissions to access the database files (ClearSCADA uses the SYSTEM user to access the database files). When the files are correctly named and in the right location and can be accessed by the Windows SYSTEM user, restart the server (see Start and Stop the System Server). The server should now be able to run the database.
If the server continues to detect errors, please contact Schneider Electric.
This means that the modules (drivers) that are required by the database are not installed on the Standby server. The Main server and Standby server need to have the same drivers installed (the Standby server can have extra drivers as well if required).
If you want to preserve the database configuration, select the Stay in Safe Mode option so that the server does not attempt to run the database. You will need to install the missing modules on the Standby server, and then restart the Standby server (see Start and Stop the System Server).
If you do have no need to install the missing drivers, select the Discard Configuration option. This instructs the server to run the database and dispose of any configuration that requires a driver that is not installed.
If the server continues to detect errors, please contact Schneider Electric.
The server has detected an internal error. Please select the Stay in Safe Mode option and contact Schneider Electric for assistance. It is beneficial to our engineers if you can provide a copy of the latest server log files for analysis.
The server has detected an internal problem. Please select the Stay in Safe Mode option and contact Schneider Electric for assistance. It is beneficial to our engineers if you can provide a copy of the latest server log files for analysis.
If the Invalid Database option is displayed, it means that the database file is unsupported or is corrupt. You need to check that the build version of the database file is supported by your version of ClearSCADA. For assistance, contact Schneider Electric.
If the Invalid Metadata option is displayed, it means that the server has detected a problem with the registry key settings. If your system uses extra database fields, check their configuration and correct any mistakes (see Extra Database Fields). If the extra database fields are configured correctly, you should contact Schneider Electric for advice.
Select the Invalid Standby Configuration option to display a dialog box. The dialog box provides information about the differences between the configuration on the Main server and the configuration on the Standby server:
The differences can include:
- The Standby server is not configured as a partner to the main server. You need to reconfigure the main server.
- The Standby server does not have the modules (drivers) required by the main server available. You need to install the modules on the Standby server.
- The configuration of certain server features, such as alarm limits, on the Standby server is different to the configuration settings on the main server. You need to reconfigure the servers so that they have the same settings.
- The multiple point state alarms on the Standby server differ to those on the main server. You need to reconfigure the servers so that they have the same settings.
When you have checked that the Standby server configuration settings are identical to those on the Main server, you can select the Retry Transfer option. If the configuration is the same, the server should run correctly.
If the server continues to experience difficulties, select the Stay in Safe Mode option and contact Schneider Electric for advice.
If the context-sensitive menu contains the options Database Save Error, Journal Save Error, or Database and Journal Save Error, it means that the server is unable to save the database or journal files. You should locate the files and check that they can be accessed by ClearSCADA (use Windows to provide the Windows SYSTEM level user with full access to the files and permission to unlock the files). You should also check that the disk to which the files are written has memory available. This is because a full disk can also cause the server to detect a database and/or journal save error.
If the files are accessible and the disk has a suitable amount of available space, contact Schneider Electric for advice.
Select the Isolated Standby option to display a dialog box that prompts you to choose between:
- Go Main
- Stay Standby
When these options are available, it means that the server is a Standby server that has become isolated due to a network failure.
If you know that the Main server is still running, select the Stay Standby option. The server will remain as a Standby server and will reconnect with the Main server as soon as the network connection is restored.
If the Main server is not running, select the Go Main option to switch the Standby server to Main. The Standby server will become the Main server and will run independently. When the network is restored, the server will arbitrate with the other server(s) to avoid a Main-Main situation.
If the Configuration Unlicensed option is available it means that the server does not have a valid license and so cannot run the database. You need to set up a valid license (see Server License Settings).
If the Exception Occurred option is available it means that the server has detected an internal problem. Please contact Schneider Electric for assistance. It is beneficial to our engineers if you can provide a copy of the latest server log files for analysis.