[ISS Support Case] Plant Scada upgrading

Last updated: October 17th, 2025

Description

Will be finding a time to sit in for an upgrade.

Author: Kevin Modlin
Published: October 17th, 2025

Details:

Product: Citect

Version: 2023 R2

Solution: [Solution is visible below when you're logged in and have a current subscription]

Date Created:	09/19/2025
Case:	99213

Give feedback about this article

Recommended articles

[ISS Support Case] Protection Key not found

Their license is showing as activated but not in use on a new install of Plant Scada.

[ISS Support Case] HST file not being created for new Tag.

Integrated process analysis. -Two variable tag's. -existing tag was also a trend variable. -new tag, create a variable and a trend that references that variable. -Both display in the HMI just find. -Trend archive property mismatched. -Not creating HST file for this new tag.

[ISS Support Case] Citect, Licensing issue.

Version: 7.5, SP1 Patch 6. -License is not working. -Using Hardkey. -Runtime manager is saying no key found or no license available from the network.

[ISS Support Case] Log storage

We are requesting support for an issue encountered after upgrading our AVEVA Plant SCADA system from version 7.5 to 8.5 (Update 10). In our current Citect 7.5 environment, we have alarms and logs configured in the devices.dbf file (configured in Plant SCADA Studio ? Setup ? Devices tab). For example, we have a log set to generate a text file whenever a user acknowledges all alarms by pressing a button on a screen. In version 7.5, these alarm and log files are successfully written to a single server file location, allowing all user actions from any client or server machine to be consolidated in one place. After the upgrade to Plant SCADA 8.5 Update 10, the behavior has changed: each machine (server or client) now stores changes made by users locally, rather than writing to a centralized server location. This requires setting up log and alarm folders on each client and server individually, then periodically backing them up or merging the files manually. This process is inefficient and time-consuming compared to our previous centralized setup. Request: Is there a workaround or configuration option that would allow devices.dbf to function in the same way it did in Citect 7.5logging user actions from all machines into a single server-based file locationrather than maintaining separate local copies on each machine?