Affected component: SCADA Runtime Connector (zrsConn_zenonV6.dll - on the Runtime computer)
Source of the problem: When a timestamp is not set, the Runtime API delivers the start of unixtime, which is 1.1.1970 00:00 UTC, in local time. For time zones with UTC-N offset, this is a time on 31.12.1969, which causes an exception in the conversion to filetime format. Such timestamps are now detected and treated correctly as not set timestamps.
Affected component: SCADA Runtime Connector (zrsConn_zenonV6.dll - on the Runtime computer)
Source of the problem: When a timestamp is not set, the Runtime API delivers the start of unixtime, which is 1.1.1970 00:00 UTC, in local time. For time zones with UTC-N offset, this is a time on 31.12.1969, which causes an exception in the conversion to filetime format. Such timestamps are now detected and treated correctly as not set timestamps.
Export Alarm to SQL-Database and use SQL-Connector. For this case this is not viable.