Resolved Issues

Description Tracking ID
Previously, when you viewed the Last 10 Values of the tags of Sever-to-Server collector, the trend was not visible, however, if you right-click on the tags, it was visible. This issue has been resolved in Historian 2024. 01092678 (DE205966)
Previously, there were Apache Tomcat vulnerabilities observed in Historian server. This issue has been resolved in Historian 2024. 01088103, 01086760, 01115035, 01114659, 01113071, 01107496, 01130189, 01118147 (DE204880)
Previously, using Web Administrator, when you viewed the Last 10 Values of a tag, the trend data was not displayed. This issue has been resolved in Historian 2024. 01086847 (DE205687)
Previously, on Configuration Hub, when you searched tags by their collection interval, the tags were not returned. This issue has been resolved in Historian 2024. 01083356 (DE205085)
Previously, there were OpenSSL 1.1.1k vulnerabilities observed in Historian. This issue has been resolved in Historian 2024. 01070308, 01050129 (DE204882)
Previously, when you attempted to extract 71 and more good quality codes using the Proficy Historian eDNA ETL tool, and then used them in configuration, all the codes were not being considered. This issue has been resolved in Historian 2024. 01093884 (DE212931)
Previously, when you attempted to start the Historian ETL PI Extract Settings, the settings did not start as the IHELPIExtract services did not start or respond. This issue has been resolved in Historian 2024. 01052974 (DE199961)
Previously, files with the wrong time format were not moved to the Error folder. Instead, they kept executing forever. This issue has been resolved in Historian 2024. 01093946 (DE212928)
Previously, there was an issue in creating a LAX file for unacknowledged and/or not closed alarm. This issues has been resolved in Historian 2024. 01098478 (DE212929)
Previously, when you attempted to load the LAX file containing custom attributes, it did not work. This issue has been resolved in Historian 2024. 01082173 (DE212930)
Previously, using the Proficy Historian Excel Add-in, when you attempted to export tags from a Historian with more than 82,000 tags, it appended an underscore at the beginning of the tag name. This issue has been resolved in Historian 2024. 01093704, 01095104 (DE204980)
Previously, when you attempted to browse, the Show ALL Children was disabled when you had collector with a large hierarchy. This issue has been resolved in Historian 2024 by providing recursive browsing support for the OPC UA Collector. 01106682 (DE208000)
Previously, STA model was not supported for OPC Collector. This issue has been resolved in Historian 2024 by adding support of the STA model. 01097084 (DE208654)
Previously, when you attempted to query string tags in trend mode, there was an increase in the DataArchiver memory until it stopped or became unresponsive. This issue has been resolved in Historian 2024 through memory optimization. 01112199 (DE210018)
Previously, after Historian alarms and events backup, purge, and restore procedures, not all alarms were available. This issue has been resolved in Historian 2024. 01109547 (DE213006)
Previously, when you used tag type Array of string and multifield, memory spike was observed. This issues has been resolved in Historian 2024. DE204209
Previously, due to memory leak issue, the Historian 2022 Server-Server Collector did not function. This issue has been resolved in Historian 2024 through memory optimization. DE203744
Previously, in operating system of specific languages, the iFIX collector stopped working when tags were browsed in Historian Administrator. This issue has been resolved in Historian 2024 by updating the latest APIs. 01092706, 01093358 (DE206183)
Previously, when the Historian local security was enabled, and the LDAP user was added to 'ih_security_admins' group, the LDAP user was not able to query data from Historian and did not load Historian plugin on Configuration Hub. This issues has been resolved in Historian 2024. 01081620 (DE208053)
Previously, in a redundant configuration, if you set fail over triggers, the OPC UA collector stopped working on both the collector machines. This issue has been resolved in Historian 2024. 01090819 (DE208653)
Previously, in a redundant configuration, there were bad values observed in OPC UA Collector. This issue has been resolved in Historian 2024. 01066966 (DE199964)
Previously, in a redundant configuration, there were bad values observed in OPC UA Collector and lot of logs were created. This issue has been resolved in Historian 2024. 01080450 (DE201897)
Previously, the MQTT Collector had memory leak. This issue has been resolved in Historian 2024. 01100809 (DE206909)
Previously, the OPC client ReadRaw call caused Server to fragment memory. This issue has been resolved in Historian 2024. 01112205 (DE210166)
Previously, the collector HDA became unresponsive after adding new tags. This issue has been resolved in Historian 2024. 01094822 (DE205288)
Previously, the OPC Classic HDA Collector restart took more time than expected. This issue has been resolved in Historian 2024. 01090894 (DE205285)
Previously, the OPC Classic HDA Collector was failing with Geo SCADA, bot being on the same machine. This issue has been resolved in Historian 2024. 01047010 (DE199907)
Previously, when you viewed the Last 10 Values of a tag using the OPC UA Collector in Historian Administrator, the data values were reported to be of bad quality, although, the values came from another good tag. This issue has been resolved in Historian 2024. 01111077 (DE210392)
Previously, you were able to enter a Scada Buffer Duration value beyond the actual supported maximum value in the Scada Buffer Duration(Days) field. This issue has been resolved in Historian 2024 by adding a conditional check on the maximum value that is being entered. 01100502 (DE208287)
Previously, when using the OPC UA HDA Collector, tags with bad quality in the Archive were incorrectly shown as having good quality. This issue has been resolved in Historian 2024. 01074939, 01082827 (DE202695)
Previously, the Filtered Data window screen in Excel Add-in was very small. This issue has been resolved in Historian 2024 by increasing the dimension (Height, Width, Top, and Left). 01071028, 01071216, 01084176, 01096784, 01098978 (DE173096, DE199256)
Previously, when you query Alarms and Events, the Perform_Comment field was blank, although it existed in the database. This issue has been resolved in Historian 2024.

01095954, 01085812 (DE205472, DE205095)
Previously, restoring .zip archives from Historian 7.1 to a Historian 2022 server resulted in an empty archive. This issue has been resolved in Historian 2024. 01048625 (DE199965)
Previously, the OPC UA collector stored the data quality as 'GOOD' when the actual quality was BAD. This issue has been resolved in Historian 2024. 01019528 (DE181224)
Previously, there were some differences in data retrieval using the interpolated or calculated mode between Historian versions 3.1 and 9.1. This issue has been resolved in Historian 2024. 01048854 (DE201650)
Previously, both tags, one of type 'Byte' and the other of type 'Quad Integer', were incorrectly returning same value for the datatype when queried through the User API for properties. This issue has been resolved in Historian 2024. 01055391 (DE199962)
Previously, the configuration manager became unresponsive on primary node unexpectedly, preventing the users from adding tags. This issue has been resolved in Historian 2024. 01072354 (DE212949)
Previously, although the OPC UA Data Access Collector was able to connect and browse some folders but could not see the items that are located under sub-folders. This issue has been resolved in Historian 2024. 01114602 (DE210148)
Previously, the Data Archiver stopped working frequently and there was no information in the log. This issue has been resolved in Historian 2024. 01107015 (DE212951)
Previously, when Historian server stopped working, restarting the services caused the Configuration manager to become unresponsive. This issue has been resolved in Historian 2024. 01107511 (DE209451)
Previously, when using the Excel Add-in for Current Value and Raw Data, if the tag quality was 'BAD', then BAD was displayed instead of the actual value in the Value column. This issue has been resolved in Historian 2024. 01058496 (DE199960)
Previously, when using Condition Based Collection, the Historian OPC Collector stopped working. Also, excessive logs were created. This issue has been resolved in Historian 2024. 1043533 (DE196097)
Previously, when you ran an Interpolated Query in Excel Add-in by setting a specific time interval, the query returned incorrect value. This issue has been resolved in Historian 2024. 1065803 (DE199958)
Previously, in Excel Add-in, the Calculated Data with Query Criteria as String returned incorrect values. This issue has been resolved in Historian 2024. 01031714 (DE198804)
Previously, when the connection to the OPC UA Server was lost, the OPC UA Collector was displaying the tag quality as GOOD, even though the actual quality was BAD. This issue has been resolved in Historian 2024. 1052808 (DE200995)
Previously, on Non-web Admin, when viewing the Default Collector Compression Timeout setting, the value was not visible or updated correctly if the Deadband type was set to Absolute. This issue has been resolved in Historian 2024. 01083360, 1009963 (DE203189)