Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Server Startup and Shutdown Sequences

Geo SCADA Knowledge Base

Access vast amounts of technical know-how and pro tips from our community of Geo SCADA experts.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Geo SCADA Knowledge Base
  • Server Startup and Shutdown Sequences
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Labels
Top Labels
  • Alphabetical
  • database 32
  • Web Server and Client 31
  • WebX 19
  • Request Form 18
  • Lists, Events & Alarms 16
  • ViewX 15
  • Application Programming 12
  • Setup 12
  • Telemetry 8
  • Events & Alarms 7
  • Lists 7
  • Mimic Graphics 7
  • Downloads 6
  • Support 5
  • IoT 5
  • SCADA 5
  • Geo SCADA Expert 5
  • Drivers and Communications 4
  • Security 4
  • DNP 3 3
  • IEC 61131-3 Logic 3
  • Trends and Historian 2
  • Virtual ViewX 2
  • Geo Scada 1
  • ClearSCADA 1
  • Templates and Instances 1
  • Releases 1
  • Maps and GIS 1
  • Mobile 1
  • Architectures 1
  • Tools & Resources 1
  • Privacy Policy 1
  • OPC-UA 1
  • Previous
  • 1 of 4
  • Next
Latest Blog Posts
  • OPC UA - Driver and Server
  • Requirements for Generating a Valid OPC UA Server Certificate
  • Load Events Using LoadRecord and LoadRecords
  • Geo SCADA Embedded Component Licenses
  • Geo SCADA 2023 Known Issues
Related Products
product field
Schneider Electric
EcoStruxure™ Geo SCADA Expert

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Anonymous user
Not applicable
‎2021-06-09 10:41 AM
0 Likes
0
3273
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2021-06-09 10:41 AM

Server Startup and Shutdown Sequences

Originally published on Geo SCADA Knowledge Base by Anonymous user | June 09, 2021 07:41 PM

📖 Home  Back  
The start up and shutdown sequences consist of a number of steps that are completed in turn. If a step is unable to complete, it may cause the start up or shutdown procedure to stop.

Any issues relating to the steps in the start up and shutdown procedures are indicated in the server's log files.

The start up and shutdown sequences are described below:


Startup Sequence




The start up sequence consists of 25 steps:

  • Load the database modules (drivers)

  • Initialize the historian

  • Initialize the data file cache. Note that this step only applies to ClearSCADA 2007 R1

  • Open the configuration file

  • Read the header of the configuration file and check the version number

  • Read the structure of the configuration (groups, parent and child relationships etc.)

  • Load the configuration of each database object

  • Load the deleted object information

  • Open the data file

  • Load the data file and check its version number

  • Load the data for each database object

  • Check for errors in the load process

  • Initialize the Event Journal and scan for event files on disk

  • Initialize each database object

  • Initialize each historic point and scan the disk for historic files

  • Perform an integrity check on Group Template-Group Instance relationships

  • Repair any broken Group Template-Group Instance relationships

  • Check the database integrity

  • Validate the configuration of each database object

  • Calculate database statistics (memory usage, total amount of historic data etc.)

  • Remove any historic data that is not associated with the points in the loaded configuration

  • Initialize the database objects for Main-Standby transfer

  • Start the database's internal housekeeping threads

  • Log an event to indicate that the server has started

  • Switch from using the start up log file to the main log file.

Typically, the start up process follows this procedure and there are no problems. However, if there are errors, the process may stop before completing or may complete with errors (the server status icon will indicate that there was an error).

Issues relating to the start up process are usually caused by:


  • Missing database files
    * The data.dat file not matching the version of the ClearSCADAConfig.dat file
    * The configuration containing objects that are not supported by the ClearSCADA installation i.e. the objects relate to a driver that is not installed as part of your system.



Diagnosing Problems: You can use the log file to determine which step of the start up sequence has caused a problem - in the log file for the server, each step of the start up sequence begins with [START]. You can access the start up log file via the Server icon in the Windows taskbar.




Shutdown Sequence



The shutdown sequence consists of 12 steps:


  • Stop any new incoming connections

  • Send a shutdown command to all clients except those clients that use diagnostic connections

  • Close all connections to non-diagnostic clients

  • Stop the web server

  • Stop all standby connections

  • Stop internal database management threads

  • Flush the Event Journal to disk

  • Flush all outstanding historic data to disk

  • Save the database

  • Send shutdown command to diagnostic clients

  • Close all diagnostic connections

  • Stop the server



Each phase of the shutdown sequence is detailed in the latest log file for the server. The steps are described as step n of n, for example, step 9 or 12. If there has been a problem with the shutdown sequence, you will be able to determine which step caused the problem by looking at the last step included in the main log file (accessed via the server icon in the Windows taskbar).

Go: Home Back

Author

Biography

Anonymous user

Link copied. Please paste this link to share this article on your social media post.

  • Back to Blog
  • Newer Article
  • Older Article
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of