Year 2038 Problem

From OPC Labs Knowledge Base
Revision as of 10:17, 5 April 2025 by User (talk | contribs) (Created page with "Date last updated: April 5, 2025 We have reviewed OPC Labs products for susceptibility to [https://en.wikipedia.org/wiki/Year_2038_problem Year 2038 problem]. The review has been made on the current version (2024.2) of OPC Studio products (QuickOPC, OPC Wizard, Excel Connector) We have found no explicit usage of signed 32-bit integer with Unix epoch for time representation in OPC Studio source code. OPC Studio products depend, however, on an environment it runs in. Spe...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Date last updated: April 5, 2025

We have reviewed OPC Labs products for susceptibility to Year 2038 problem. The review has been made on the current version (2024.2) of OPC Studio products (QuickOPC, OPC Wizard, Excel Connector)

We have found no explicit usage of signed 32-bit integer with Unix epoch for time representation in OPC Studio source code. OPC Studio products depend, however, on an environment it runs in. Specifically:

  • the operating system (Windows, Linux, or MacOS), and
  • the .NET runtime (.NET Framework, or "new" .NET).

As of date of this article, no actual test results (simulating current date of year 2038 and over) are available.

We make no statement about earlier versions of the software. Customers with past versions are advised to upgrade to version 2024.2 or later, in order to benefit from the review results stated above.

Retrieved from "https://kb.opclabs.com/index.php?title=Year_2038_Problem&oldid=5917"