Reload a Process

Runtime > Runtime Manager > Reload a Process

You can reload the configuration for a server processes during runtime. This will reload any updated database files, allowing you to implement some project configuration changes without performing a full restart. For more details see the topic Server Side Online Changes.

To reload a process:

Right-click on the process and choose Reload from the shortcut menu.

The Status column will change to indicate that a reload is in progress. Once the reload is complete (successfully or otherwise), the Message column describes the result of the operation.

Message	Description
Reload could not start because another reload was being commenced.	Check that no reloads are currently active before you attempt the reload again.
The last reload was completed at {time}, on {date}.	Indicates the reload was successful.
Reload could not start because the requested components in this process are disabled.	All components in the selected process are disabled due to license restrictions or a Citect.ini file setting (for example, [Trend]Disable is set to 1).
Server reload failed. Please check Citect syslog for more information.	View for the syslog.dat file to determine why the reload was unsuccessful.
Unknown error: {0}	{0} represents the error code returned by the system when a reload of the database files was attempted.

Note: It is recommended that the ServerGetProperty Cicode function be used with the LibRDBMemTime and LibRDBDiskTime properties to check if there is a change to the Cicode library before attempting a reload. Following a reload please check the corresponding server's syslog.dat file for any reload messages. The Cicode changes will not be reloaded, therefore a restart may be more appropriate.

UNINTENDED EQUIPMENT OPERATION

Restart the server process if a "Cicode library timestamp differs" error is detected. The library mismatch is indicated on the server in either the hardware alarm or the server's syslog.dat file.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Note: A message in the Syslog.dat file and hardware alarm of "Cicode library timestamp differs" (error code 454) will be raised if the Cicode library used by one or more server runtime databases is different from the one in memory. The timestamps will be different if the project has been fully recompiled (with or without Cicode modification), or if the project has been incrementally recompiled after any Cicode has been modified.