It could be possible, that the zenon Runtime is closing with an unhandled exception. Under specific circumstance e.g. when a zenon client isn't connected to its configured server and a zenon everywhere client is connected and request for alarms, the runtime close unexpectedly.
It could be possible, that the zenon Runtime is closing with an unhandled exception. Under specific circumstance e.g. when a zenon client isn't connected to its configured server and a zenon everywhere client is connected and request for alarms, the runtime close unexpectedly.
An issue has been addressed so that the runtime no longer crashes under this situation.