Starting and Quitting System Server and Clients
Step Action
3
4
5
Result: The log-in window opens.
Enter your username without domain or prefix, your password, and click Log In .
Result: The system server console opens.
Click Action > Start .
Result: The system server starts.
Wait until the system server console displays the following message at the bottom of the window to start engineering and operation clients (see EcoStruxure ™ Process Expert,
Installation and Configuration Guide):
Server is ready .
Client/Server Connection
Overview
Clients connect with the system server through an Ethernet cable connection, for example to:
• Access the database.
• Access software Participants.
• Launch tasks that are performed by the system server.
• Receive notifications from the system server.
• Verify digital certificates and license rights.
You cannot use clients while the connection to the system server is interrupted or while the system server is not running.
You can test the client/server connection (see EcoStruxure ™ Process Expert,
Installation and Configuration Guide).
Notifications About Client/Server Connection Interruption
The table describes the various notifications that appear client-side for different scenarios where a client cannot connect to the system server or the virtual machine anymore.
Scenario
1
2
3
4
Operation in progress at the time of the interruption
No
You launch a task while the connection to the system server is interrupted.
Yes
Client notification
No
Notification that the client is unable to connect to the system server.
Notification about an unexpected communication interruption.
Yes. An action is performed in an open software
Participant window.
Corrective action
None
Launch the task again when the connection is reestablished.
Notification that the action in the
Participant cannot be performed and indication of the possible causes.
NOTE: If you are refining a
Control project online (see
EcoStruxure ™ Process
Expert, Control Participant
Services, User Guide) and have clicked the button to build and deploy changes after the connection was interrupted, the changes
If the system server is still running, the action completes server side and the notification of clients is updated when the connection is re-established.
If the system server has stopped, an
action is required, page 49
.
If the connection to the system server is still functional, save changes, close the Participant window, and start over once the problem is fixed.
If the connection to the system server is interrupted, refer to scenario 3.
If the reason for the connection interruption cannot be determined, you need to contact Schneider Electric
support, page 79
.
EIO0000001114.15
47
Scenario
5
6
Starting and Quitting System Server and Clients
Operation in progress at the time of the interruption
Client notification
The system server is stopped by user intervention.
are not deployed nor saved.
Notification in the
notification panel, page 54
to inform that the server is shutting down.
Corrective action
From this point on, you cannot perform any action on the client.
Restart the system server.
Contact Schneider Electric
support, page 79 .
Yes. An action is performed in an open software
Participant window.
None.
A message appears in the system server console.
NOTE: Refer also to the topic providing information to help troubleshoot client/ server communication (see EcoStruxure ™ Process Expert, Installation and
Configuration Guide).
The following figure shows an example of the notification that appears for scenario
2. The name or IP address and the port of the system server computer are indicated.
The following figure shows an example of the notification that appears for scenario
3.
The following figure shows an example of the notification that appears for scenario
4.
48 EIO0000001114.15
Starting and Quitting System Server and Clients
The following figure shows an example of the notification that appears for scenario
4 in case you are refining a Control project online.
After Re-establishing the Connection to the System Server
Clients automatically reconnect to the system server when the connection is reestablished or when the system server is running again. After reconnecting, clients display a notification to inform you of the communication interruption.
Unsaved changes are discarded and open windows are reloaded or closed automatically.
EIO0000001114.15
If the system server has stopped, the notification panel is empty when the system server restarts. To view the history of activity up to the interruption of the communication, open the
log files, page 59 .
After an unexpected interruption of the client/server connection, the states of both the engineering client and the system server may have become inconsistent. This can be the case, for example, if at the time of the interruption an operation was in progress such as an import of several Participant projects or pasting of many instances.
NOTICE
LOSS OF COMMUNICATION
After an interruption of the client/server connection, verify that the last operation executed by the software was completed successfully, and if necessary, repeat the last operation.
Failure to follow these instructions can result in unresponsive clients.
You are able to resume using the software when the connection to the system server is re-established or when it is running again.
49
