Historian Release Notes
Version: 7.2
| Description | Tracking ID |
|---|---|
| Replacement of Oracle Java with AdoptOpenJDK Starting Historian 7.2 release, Oracle Java 1.0 distribution will be stopped and is replaced by AdoptOpenJDK 8. AdoptOpenJDK will be deployed as part of Historian 7.2 installation. AdoptOpenJDK uses infrastructure, build and test scripts to produce prebuilt binaries from OpenJDKclass libraries. Note: As Oracle started imposing licensing restrictions on its Java installations (starting Java 1.8 and higher versions), the direction of the Historian product is to replace Oracle Java with AdoptOpenJDK.ild and test scripts to produce prebuilt binaries from OpenJDKclass libraries. Important: Installing the Historian 7.2 version will not uninstall any existing Java installations on the target machine so that the existing applications that make use of pre-existing Java are not affected.
After Installing Historian 7.2, Historian will point automatically to AdoptOpenJDK. Customers using Oracle Java for running Historian versions prior to 7.2 with web components can move to AdoptOpenJDK. | F42505 |
| Enhanced OPC HDA Historian Server to support Aggregate functions Starting Historian 7.2 release, some of the OPC HDA aggregate functions are supported. The aggregate functions include both standard and custom functions. HDA aggregates is a function that is used to process raw data from an OPC HDA Server. The raw data is processed over a range of time divided into discrete intervals. These aggregates can be used to visualize the trends in the data and for other purposes. The standard aggregates supported are:
The custom aggregates supported are:
| F42500 |
| Enhanced OPC-UA collector to support user authentication Starting Historian 7.2 release, a secure channel can be established between the OPC UA collector and OPC UA server. The credentials provided by the user in OPC UA collector are used to establish a secure communication with OPC UA server. | F42507 |
| Introduced ODBC Collector Starting Historian 7.2 release, a new bi-modal ODBC (SQL) Collector is introduced. This data collector reads the data from any of the ODBC servers and writes it to Historian Server or Predix Time Series, such as other data collectors. This is available for installation in the list of collectors in Historian ISO package. | F42511 |
| Enhanced PI Collector to support PI Snapshot Previously, you had the ability to collect data from only PI Archive. Starting Historian 7.2, you can collect data from PI Snapshot as well. You can switch between the PI Snapshot and PI Archive data sources. | F42506 |
- Starting Historian 7.2 release, any Linux related components will not be shipped as part of the Windows Historian ISO. The Linux OPC UA Collector and Linux Toolkit can be installed using the Docker based Historian Installation.
- Customers upgrading to 7.2 Historian should purchase and use new 7.2 license. The old licenses prior to 7.2 will not work with 7.2 Historian. However, the new 7.2 license will work with previous versions of Historian.
| Description | Tracking ID |
|---|---|
The 7.1 ihArchiveDefrag_x64.exe caused issues in the defragmented archives. These issues lead some of the data queries to return incorrect results. The new ihDataArchiver_x64.exe has been fixed to interpret the issue correctly and return correct results. Also, ihArchiveDefrag_x64.exe has been fixed so that any future archive conversions will not have this issue. Perform either of the following (based on your scenario), to resolve this issue:
| DE113206 |
| Previously, when you queried a string tag with Lab sampling mode, some records returned null value but with Good Quality. This issue has been resolved. Now, in this scenario, Good Quality is not returned. | DE108592 |
| Previously, PI collector crashed on start up when General5 key was set to Snapshot. This issue has been resolved. | DE77558 |
| Previously, PI to Cloud Collector crashed randomly. This issue has been resolved. |
DE116602
|
| Previously, Trigger tag disappeared when moving a Tag with Collection Type, Unsolicited from one Calculation Collector to another Calculation Collector. This issue has been resolved. | DE108593 |
| Previously, filtered data query did not time out after the time duration set in Historian Administrator. This issue has been resolved. | DE108599 |
| Previously, Data Archive crashed randomly. This issue has been resolved. | DE108601 |
| Previously, Calculated tag was not being updated after it had encountered a bad tag value. This issue has been resolved. | DE99374 |
| Previously, issues occurred in Historian OPC UA collector with Polled Historian tags. These issues have been fixed. | DE107839 |
| Previously, Local Calculation Collector did not process the calculations when you used aliases. This issue has been resolved. | DE31230 |
| Previously, for the sampling modes, InterpolatedToRaw, LabToRaw and TrendToRaw, the system always returned Bad Quality when the number of samples was less than the total of samples returned from the query in the server. This issue has been resolved. | DE93368 |
| Previously, when a query was created, and an output range selected was bigger or smaller than the number of samples returned from the query, the timestamp was not formatted properly. This issue has been resolved. | DE108598 |
| Previously, there was a memory overflow error in ClientAccess.API.dll when data was queried with interval greater than one hour. This issue has been resolved. | DE107834 |
| Previously, in Historian Administrator, when you queried a tag that contained a huge amount of data in the specified time range, a blank screen appeared. This issue has been resolved. | DE96655 |
| Previously, the migration tool iFix to Historian command line stopped functioning in 5.5 and above. This issue has been resolved. | DE108596 |
| Previously, there were security and access issues after upgrading to Historian 7.1. These issues have been resolved. | DE106008 |
| Previously, Universal Client rejected Login Credentials after being idle for certain time. This issue has been resolved. | DE111032 |
| Previously, Tag level security did not work for OPC HDA client application. This issue has been resolved. | DE58352 |
| Previously, an error occurred while accessing Plant Applications Administrator. This issue has been resolved. | DE103073 |
| Previously, an error occurred when you selected the Alarm button in Excel Add-In. This issue has been resolved. | DE112410 |
| Previously, issues occurred when you queried the tags with calculation property as NULL. These issues have been resolved. | DE108600 |
| Description | Tracking ID |
|---|---|
| AdoptOpenJDK is installed in only C-Drive, when you choose to install Historian in the any other drive. | DE112542 |
| Historian 7.1 Sim1 uninstallation fails on some of the machines. Workaround: Stop all Historian Server services and then uninstall Historian Sim1. | DE114135 |
| Tags which are associated with ENUM are not correctly displayed in the destination machine when connected using OPC HDA Collector. | DE113677 |
| Compression is not applied for OPCHDA Cloud collector. | DE114500 |
| When you update the archive duration from 1 Day to 1 Hour using Historian Administrator, Day based archives are created instead of Hour based archives in Mirroring system. | DE114615 |
| When you upgrade a Collector to the latest version the settings are not updated. | DE115227 |
| When compression is enabled for Cloud Collector tag, an extra value is stored before the compression timeout. | DE115323 |
| User is not able to log in to Plant Applications, if Historian is installed after installing Plant Applications. | DE115530 |
| Wonderware Collector is crashing when you select and delete all the source tags at once. | DE115868 |
| Prefix is not getting added to the messages when message prefix is enabled in Server to Server Collector configurations. | DE113857 |
| Compression is not working in OPC HDA Collector. | DE114864 |
| Readattime option is not working while querying the data from OPC HDA Server using Matrikon Client | DE115033 |
| Tag level Security - Administrator group user cannot browse and edit the tag if Read or Write group is already configured. | DE115633 |
|
Data loss is observed in Server to Cloud Collector backfill | DE115651 |
| In case, the user is planning to install products like Cimplicity or iFIX, Historian must be installed last. | DE92870 |
|
Alarm Archiver is not uninstalling completely. Workaround: Uninstalling Historian Alarms and Events alone will not clear all binaries and services. To uninstall completely, Historian server needs to be uninstalled first, this in turn will uninstall Historian Alarms and Events as well. | DE93236 |
|
Following are the issues that are consolidated as known issues with Installers of various Historian components: DE91421 : WPC Collector .exe is not upgraded in the windows service after upgrade from 7.0 SP5 to 7.1. DE91413 : Excel Add-In not retaining default server setting on upgrade DE91424 : On upgrading Collectors it does not retain Historian server name DE92530 : Upgrade of Alarm Archiver from 5.5 to 7.1 is uninstalling previously installed excel add-in DE93236 : Alarm Archiver is not uninstalling properly DE93253 : Start collector shortcut is not removed from Start / Program Menu after uninstalling OPC DA and OPC collector DE91414 : Client tools installation asking for OPC prog ids DE91419 : Collectors getting installed when only client tools are installed DE91461 : 7.1 excel addin doesn't ask for historian server name while installing, 5.5 excel addin asks DE91503 : Upgrade dialog box is displayed while performing uninstallation of Client Tools (Proficy historian) DE92870 : Historian install fails if its installed before CIMPLICITY or iFIX DE92912 : Alarm and Event service is removed from system after upgrading from SP6 to 7.1 Workaround for the above issue is: Uninstall the component that has the issue from the above list and then install the respective Historian 7.1 component afresh. Make sure appropriate backups (Such as : registry, data files, credentials, custom settings etc.) are taken before uninstalling the component. | DE94396 |
| If the tag is renamed (not permanent rename - Aliasing) the tag name is available for selection in the browse tag list(shown in blue color). If the user tries to select and add the tag, an error message is throwing denoting "Error Adding Tags". | DE91020 |
|
In a domain environment, collectors which are running under local system account are not connected to Historian Enterprise OR PH5.5. User need to run the collector as Specific user account and then start the collector service to connect to Historian Server. | DE93416 |
| In the Excel Add-In, the search message functionality is not returning expected output when start/end time format is mm/dd/yyyyy HH:mm:ss. | DE93928 |
| Using Historian Microsoft Excel Add-in plugin, querying for Historian tags data would work consistently across multiple versions of Microsoft Excel only when the with length of the tag is less than or equal to 180 characters. It is possible that with the latest versions of Microsoft Excel (2016) length could be more. | DE93442 |
| In Trend Client, due to long length (around 256 characters), the display of all tags is not properly aligned. You may see the same issue in Current value charts. | DE94749 |
|
Historian SDK sample (VB) is shipped with Historian Server Install only and not with the Client Tools Install. Work around: Use the Historian SDK samples (VB) from Samples\SDK folder. | DE95660 |