--- manual: IM 36K01A50-01EN title: CI Server Release Information edition: 5th Edition, Feb. 2026 (section "Platform and installation"); other sections still from the 3rd Edition, Sep. 2023 version: R1.05 (first written for R1.03); only "Platform and installation" re-checked so far status: from docs ("Platform and installation" compared with the 5th edition on 2026-10-08; Start-menu folder checked on the R1.05 test server) --- # Release Information: known issues and cautions (R1.05) Known limitations and workarounds that the other manuals do not cover. Check this list before recommending a workflow in any area. Section numbers refer to the manual. The "Platform and installation" table follows the 5th edition (R1.05); the other sections were written from the 3rd edition (R1.03) and are re-checked with their skills. ## Platform and installation | Area | Issue | What to do | |---|---|---| | Dual-redundant platform (1.1) | Without a Vnet/IP card, guest time sync by NTP makes host messages in the historical alarm overview show wrong timestamps. | Accept, or use Vnet/IP time sync. | | Dual-redundant platform (1.1) | After both computers restart, the former standby may come up as *Guest OS (Isolated)*. | In the Redundancy Management Tool set Next Status to *Standby*, then restart that computer. | | IT Security tool (1.3) | Remote Desktop to the CI Server may fail after applying IT Security if OS patch levels differ. | Patch both the server and the RDP client to the latest level. | | IT Security tool (1.3) | Changing Windows region/language after applying IT Security causes problems. | Set region and language **before** applying IT Security; never change afterwards. | | IT Security tool (1.3, R1.04+) | Upgrading from R1.03 or earlier where the IT security defaults were changed: a dialog offers to reset the account lockout settings (threshold, counter reset, duration). | Answer Yes (No returns to the start of the IT security setup); afterwards set any custom lockout values again. | | Windows (1.4) | CI Server started from the command line on Win10 / Win11 needs elevation. (The R1.03 Server 2016 start-menu note is gone.) | Always use *Run as administrator*. | | Windows (1.4) | Custom fonts can cause visual glitches in the Engineering and Edit modules. | Avoid custom fonts. | | Windows (1.4, R1.04+) | After a user without rights to the CI Server programs opens the CI Server Start-menu folder, its icons stay blank for everyone. | In an elevated prompt, in `C:\ProgramData\Microsoft\Windows\Start Menu\Programs\CI Server` (likewise *CI Server Remote Connect*, *YOKOGAWA Security*, *YOKOGAWA Redundancy*) run `COPY /B * +,,` to touch the shortcuts. The manual's path has typos; the folder name was checked on the R1.05 test server (2026-10-08). | | Install path (1.9) | The MELSEC EZSocket installer fails if CI Server is in a non-default path that contains spaces (still in the 5th edition). | Non-default install paths must have no spaces. | | MELSEC (1.9, R1.05) | iQ-R support now uses EZSocket 5.9, installed from `\Windows\EZSocketPcRedistributableInstaller` (`RunInstaller` as administrator); Mitsubishi reports a vulnerability in it. | Uninstall older EZSocket first. Keep the EZSocket folder writable by Administrators only, run antivirus, keep the PC off untrusted networks (VPN/firewall for remote access), open no untrusted files or links. | | Virtual machines (1.19) | Live migration, failover and shared-storage path switching lose acquired data/alarms; failover during engineering can corrupt the engineering data. | Migrate only when no engineering is in progress; keep engineering backups. | | Virtual machines (1.19) | Serial-only drivers (Siemens 3964R, telemetry integration), Siemens SAPI-S7 and MELSEC are unavailable on VMs; many other drivers work over TCP/IP only. | Check driver support before choosing a VM. | | Virtual machines (1.19) | Do not use VM replication; do not mix physical and virtual machines in HAC; only thin clients may RDP into a virtual CI Server. | Design accordingly. | | Virtual machines (1.19) | The software medium must be mounted as an ISO on the VM (e.g. via Hyper-V Manager › Media › DVD Drive › Insert Disk). | Read "DVD drive" in the manuals as the mounted ISO drive. | ## Services **ACCESS (1.5)** - OPC classic on Win10 / Win11 / Server 2019 / 2022 needs .NET 3.5 (5th edition; R1.03 listed Server 2016). Install it from the Windows medium (`DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source::\sources\sxs`), then re-run the OPC Core Components Redistributable in `%TLS_EXE_PATH%`. - OPC AE: items in the tree root (no section) appear as `.NAME` and some clients can't use them as alarm sources. Put alarm-source items inside a section. **ALARM (1.6)** - Shelving cannot restrict OPC AE items by status/type. - Shelving more than 500 alarms can overflow the DURM queue; after a Portal–Core link loss, restart the shelf overview. **BUS (1.7)** - Secure MDUR on Linux: create `/tls/pki` manually before configuring the secure connection. **DATABASE (1.8)** - With Active Directory login, up to ~15 s may pass between the login form closing and the application appearing. Expected behavior. **EQUIPMENT (1.9)** - MELSEC iQ-R: R1.03 needed Mitsubishi EZSocket 4.4 from `%TLS_ROOT_PATH%\tls\exe\EZSocketPcRedistributableInstaller`; R1.05 uses EZSocket 5.9 from the install media (see the MELSEC row in the table above). Uninstall older EZSocket first and run `RunInstaller` as administrator. - IEC 61850: add the line, then the station (General tab: device IP; Options tab: domain prefix and report object), then points. The element address is ``; the point I/O address is only the part **after** the prefix (the prefix is added automatically). Wrong delimiting means no reports/elements are created. (R1.03 edition; this precaution was removed in the 5th edition, see the L41 summary §3.32 for R1.05.) **PROCESS (1.10)** - Java classes that access datasets must get the DSS session with `getDssSession()` (never `Dss.createSession()` or `DssContext.getSession()`), must never close it, and must be recompiled and reset after the change. Otherwise results are undefined (e.g. `ADT-E-ECL_UNKNOWN` in the system log). - When making items with SIGNALs, handle root-level items: if `SECTION` is empty use the tag alone, else `SECTION || "." || tag`. Prefer automatic naming. - Section-based SIGNAL creation does not support process area definitions. **REPORT (1.11)** - AD + printer management can make report generation fail (looks for the user's default printer). Workaround: create a printer destination not bound to a device and set it as the default destination in the AD user profile. - Report features of Schemes take effect only after restarting the Engineering module. **USER (1.12)** - Remote Connect is for client machines **without** CI Server; don't install it on a CI Server. - HTML5 displays cannot be validated via Remote Connect; engineer them on a CI Portal. - HTML5 is a lightweight/mobile HMI with fewer components than Java displays (details in Edit Module, IM 36K10C50). Use Google Chrome; other browsers may render differently. - SSO leaves a landing page open that the user must close. SSO needs Active Directory, so Windows only. - `jwuiutl` over Remote Desktop is denied by default. To allow it: Setup File Editor › `dssana.sup` › *Login Control* tab › row *Client system name ``, Display and Symbol Utility* › Login method = *No* › restart CI Server. Needed by CI Exchange (CENTUM VP / Prodigy) load and conversion scripts. - Remote Connect operator interface may fail to start (Java network read issue): retry, or clear the Java cache (Java Control Panel › Temporary Internet files › Delete files). - Auto-login is for server / CI Portal applications only, not Remote Connect. - "Application blocked" for `.jnlp` over HTTPS is caused by the self-signed web server certificate. Fix with a CA/domain-issued certificate (preferred) or add `https://localhost:8443` to trusted sites (less safe). - Web HMI display names are case sensitive. - Custom Java components must be signed by Yokogawa before use. - Edit module quirks: item properties editor Value field font too small; *Update item/parameter* on the Attributes sheet ignores the first change (repeat it or use the Actions sheet); a symbol custom property must not reuse an existing property name; choosing *Open display* in an event's Action combo adds a duplicate event (delete it); function components must stay inside the drawing area and must not be grouped. - Same-size labels may render at slightly different sizes (Java anti-aliasing). Use *Apply text smoothing* in the CI Portal setup file, or a non-integer zoom such as 99.999 %. - HTML5 limitations: no login name in the status bar; frame border styles map imperfectly; Windows display scaling must be 100 %; no rotation or column filters on alarm overview / shelved alarm overview; transparency and margin properties are ignored. ## HMI, GIS and OPC UA **HMI general (1.13)** - Date/Time field with *editable* or *disable* set shows a black foreground in the operator interface (correct in HTML). - Up/down buttons differ in size between operator interface and HTML. - With *Fit display*, tooltips and selection dialogs of trend / alarm overview are misplaced. Uncheck *Zoom enabled* on those components, or design displays at the target resolution. **GIS (1.14)** - Click info is not shown for symbols built with a data bar. Use simple symbols as map markers. - Don't use symbols containing alarm overview, trend or report components in GIS (high memory in Chrome; alarm overview filters don't receive item names). - Symbols/map layer may disappear or draw behind the map after long runs (Ctrl+wheel zoom restores). In Chrome, disabling hardware acceleration fixes symbols drawn behind the map. **OPC UA (1.15)** - PubSub upload fails with *Internal error* if a published dataset has zero items. Remove or revert those datasets. - The datatype combo in PubSub Reader item mapping has no effect. - Variables/properties of `CIAlarmConditionType` / `CISystemEventType` nodes can't be read (`BadNotReadable`) or subscribed individually (`BadNotSupported`); subscribe to the alarm event. - CI Core memory for external OPC UA clients: under 20,000 items no extra memory; 20,000–99,999 add 8 GB; 100,000–199,999 add 16 GB; beyond that add 8 GB per extra 100,000. ## Server Core / Portal (1.16) - Secure DURM with an invalid certificate common name continues **unencrypted** (only logged). After installing/refreshing certificates, check the message log that they were accepted. - Remote Connect Engineering module is slow against a redundant CI Core. Use RDP to the Core, or temporarily run the redundant platform in single mode. - Several MQTT stations on one MQTT line with brokers unavailable can time out during offline engineering. Use one station per line, or a temporary local broker. - GIS component properties *Apply* increases Edit module memory each time; close the dialog and display to recover. - Object Selection dialog can hang the Edit module when a section has many objects (DSSSDA at high CPU). Type the object name directly; to recover, stop that DSSSDA instance in Performance Monitor, close the Edit module, restart CI Server. - Enterprise Edit Module: shelved alarm overview shows nothing if added before the alarm overview, on another layer, or with different alarm source locations. Add the alarm overview first, same layer, same source locations. - Alarm overview CI attributes: changing checkboxes on the Attributes tab can reorder the Columns tab. Workaround: *Uncheck all* › Apply › re-check › Apply › reorder on Columns › Apply. - Engineering module CI attribute names: pick *Add new record* or an existing name from the drop-down; cancel the *Add new CI attribute* dialog if it appears unexpectedly. - OPC UA alarm event type filters and alarm template settings that are in use can't be deleted, and a same-named one on another station also becomes undeletable. Use unique names per station; to recover, copy under a new name, repoint, then delete. - EALs can't be edited in bulk in the Engineering module. Use `dssqld` on dataset `EXTERNAL_ALARM_DF`. - Retrieve from archive does not restore alarm attribute databases (alarms visible, attributes not). - ODBC writes: Microsoft Access can't write to R1.03.00+; SQL Server Management Studio and Excel via ODBC can't either. PowerShell and custom applications can (ODBC DSN `CiSimbaClient`, e.g. `UPDATE ITEM_VAL SET ITEM_VALUE_STR=..., STATUS_NUMBER=... WHERE NAME=...`). Alternatives: Excel Add-in, or `dssqld` on the Core/Portal. - Acknowledging external alarms over ODBC: filter on `NAME` in `ALARM_CURRENT` (e.g. `UPDATE ALARM_CURRENT SET ACK = 1 WHERE NAME = '