Historian Client 2017 Update 3 SP1 Patch01

Материал из archestra.info
Перейти к: навигация, поиск

Wonderware Historian

Wonderware Historian

In This Document

Wonderware Historian 2017 Update 3 SP1 P01

Wonderware Historian 2017 Update 3 SP1

Wonderware Historian 2017 Update 3 SP1 P01

Latest revision: 5/28/2020

About This Readme

This Readme provides information about Wonderware® Historian Server version 17.3.101, which is part of the Wonderware System Platform 2017 Update 3 Service Pack 1 Patch 1.

For information about new features, hardware and software requirements, product compatibility, installation and upgrades, and user documentation, see the Wonderware System Platform 2017 Update 3 Service Pack 1 Patch 1 Readme.

About this Patch Release

The System Platform 2017 Update 3 SP 1 Patch 01 release resolves a number of issues, documented in each product Readme file. For more information about System Platform 2017 Update 3 SP1 Patch 01, see the System Platform 2017 Update 3 SP 1 Patch 01 Readme, available for download with the Patch Manager.

Important!

  • Installation - Wonderware Historian Server 2017 Update 3 SP1 must be installed before you can install this patch.

If you plan on upgrading to Historian Server 2020:

  • Some resolved issues included in this patch are not built into Historian 2020. Therefore, if you upgrade to Historian Server 2020 after applying this patch, you may need to apply specific hot fixes to your upgraded Historian Server 2020 system. The issues NOT INCLUDED in Historian 2020 are listed in a separate table.
  • If, after applying this patch release, you then upgrade to Historian 2020, you may need to apply specific hot fixes if one or more of the issues described below affect your system. If this occurs, contact AVEVA Global Customer Support (GCS) for the hot fix(es).

    IMPORTANT: This patch cannot be applied to Historian 2020. Instead, contact AVEVA Global Customer Support (GCS) for the specific hot fix(es) that are applicable to your installation.

Known Issues

  • If the user account that launches the application belongs to a nested security group (group within a group), the application content that uses historical data retrieval will fail.
  • While a Historian server is starting up, if any clients are running queries, then an error message is logged stating Event Storage Unknown exception caught and the query fails. Once the server has started, further queries complete successfully as expected.

Resolved Issues In This Release

This section describes issues that have been resolved in Wonderware Historian version 17.3.101.

These issues are listed by their Change Request (CR) number and any assigned Service Request (SR) number. The left column of the table shows the original Change Request in which the issue was identified. The Related Change Requests column lists other change requests that are related to the original change request.

Original Change Request

Related Change Requests

Description

L00157653

L00156930

When a tag name contains invalid characters, aahTagRename.exe is unable to rename it.

L00157511

L00156063

SR 103161235: Timestamp saved in history block is occasionally 1-2 milliseconds less than the timestamp sent by the DAServer.

L00157510

L00155264

SR 45511424: Live values do not match the PLC value if a value was set in the swinging door and this setting is deactivated.

L00157655

L00157090

When replicating more than 2000 rows, not all rows are replicated.

L00157508

L00154351, L00155346

SR 48912637: Counter retrieval mode does not return the correct value.

L00157509

L00154425, L00154497

SR 48912640: Slope retrieval mode does not return the correct value.

L00157599

L00153952

SR 103160744: Visibility animation on DSC tags not correctly replayed in InTouch OMI.

L00157638

L00153181, L00155841

SR 48912765: Gaps in the Insight Trend when compared to Historian Client Trend for the same data.

L00157650

L00156668

SR 103166984: After migrating A2ALMDB to history blocks using the aahBlockMigrator tool, "Operator" and "UserFullName" are inversed.

L00157600

L00153963

Alarm Client EAC Query filter takes several minutes to display new events.

L00157602

L00153981

SR 40219889, SR 103160070: "No historized attributes match your search" error when Insight app even though there is valid data in the historian.

L00157618

L00154614

SR 103162356: Upgrading from version 17.1 to version 17.3 results in all existing trends in Insight having their pen color set to blue.

L00157645, L00157631

L00156145, L00155071

SR 63912753: Internet Explorer shows a popup asking, "Are you sure you want to leave this page?" for unclear reasons.

L00157528

L00155195

SR 103162931: Newtags.tag from a published Intouch app contains all tags instead modified tags, causing a commit of all tags instead of only the delta.

L00157617

L00154587

Alarm overlays on trends are missing from the Insight OMI app, even though they are correctly shown on the standalone Insight web pages.

L00157629

L00155030

SR 10918548: Upgrading from version 17.1 to version 17.3 SP1 results in all existing trends in Insight having their pen color set to blue.

L00157659

L00156917

SR 103167638: Alarm client displays historized events with a one hour difference from the event time returned by SQL Query.

L00157959

L00156780

SR 40810223: Some tags do not show history values for a time period of a few hours, while the rest of the time the history values are correctly displayed.

L00157947

L00155737

SR 48912700: A script using the Historian SDK APIs fails to update data, logging an error message, "Error: error = 21 (Transaction validation failed)."

L00157957

L00156362

SR 103164925: Queries on the Events view decrease in performance after upgrading from 2014R2SP1 to 2017.

L00157632

L00155213

Tag rename utility does not allow special characters within existing tags.

L00157641

L00155995

Insight web client is unable to share a dashboard created and saved in Insight.

L00157656

L00157120

SR 50411566: Searching for tags in Insight shows less than 100 results when more results should be available.

L00157958

L00156658

SR 50411502: Newly-created tags are not added to the live table until restarting the Historian.

L00157960

L00156868

Auto summary replication fails, logging error 176 (buffer is full).

L00157961

L00156851, L00157040

SR 35313802: Certain queries experience a large decrease in performance after upgrading from 2014R2SP1 to 2017U3SP1.

IMPORTANT: The following issues are not built into Historian Server 2020. Therefore, if you upgrade to Historian Server 2020 after applying this patch, you may need to apply specific hot fixes to your upgraded Historian Server 2020 system.

Original Change Request

Related Change Requests

Description

L00158034

L00157712

SR 103170172: Query using two different tags in an IN clause fails, while querying the tags individually succeeds.

L00158033

L00157850

SR 103170055: Tag description changes are not propagated to tier 2, when the changes are made in tier 1 using the database export/import utility.

L00157658

L00157217

Replication does not work for tags with legacy data and new storage data, if the tag names differ in case, even with a case-insensitive database.

L00157843

L00157675, L00158186

SR 50411666: After a reboot, the Historian is only licensed for 50 tags, until the license is refreshed

L00158158

L00152118, L00157264, L00157879

SR 48310220: Multiple Insight client licenses are used when multiple charts are embedded within a single website.

L00158141

 

HCAP does not validate remote IDAS connections.

Related Topics

Wonderware Historian

Wonderware Historian 2017 Update 3 SP1

Wonderware Historian 2017 Update 3 SP1

Latest revision: 5/30/2019

About This Readme

This Readme provides information about Wonderware® Historian Server version 17.3.100, which is part of the Wonderware System Platform 2017 Update 3 Service Pack 1.

For information about new features, hardware and software requirements, product compatibility, installation and upgrades, and user documentation, see the Wonderware System Platform 2017 Update 3 Service Pack 1 Readme.

New Features In This Release

The Wonderware Historian 2017 Update 3 Service Pack 1 (version 17.3.100) includes:

  • Multi-tier replication support
    Historian supports multi-tier replication. Data originating at tier 1 can be replicated to tier 2, then again to tier 3, and so on. Replication from tier 1 to tier two can be simple or summary replication. Replication beyond tier 2 is simple replication.

Known Issues

  • If the user account that launch the application belong to a nested security group (group within group), the application content that uses historical data retrieval will fail.

Resolved Issues In This Service Pack

This section describes issues that have been resolved in Wonderware Historian version 17.3.100.

These issues are listed by their Change Request (CR) number and any assigned Service Request (SR) number. The left column of the table shows the original Change Request in which the issue was identified. The Related Change Requests column lists other change requests that are related to the original change request.

Original Change Request

Related Change Requests

Description

L00150895

L00153507

SR 103154157: In Historian Insight, zooming in and out causes the data values to flatline.

L00151702

L00152123

SR 103154364: Historian freeze. The OLE DB provider "INSQL" for linked server "INSQL" reports an error. The provider ran out of memory.

L00151983

L00152917

SR 103155728: The buffer for error logs from aahStorage is too small (error = 31).

L00152322

 

SR 103157464: The installation process was unsuccessful and produced error code 2753 (17.2 to 17.3 upgrade).

L00152622

L00153516

SR 48912446: NULL was not inserted on a network disconnect between Historian and the node running AppEngine.

L00152628

L00152934

SR 10918376: When adding, loading, or refreshing tags in Historian Insight, an error displays saying "Something went wrong. Your request didn't return any data."

L00152782

L00153360

SR 50411382: In Configuration Editor, expanding the editor and selecting any option (such as Data Acquisition) causes the editor to go blank. Historian must be restarted to resolve.

L00152807

L00153423

SR 103158292: While viewing a plotted tag, zooming in and out causes the value to change.

L00152931

L00153518

SR 35313630: Importing analog tags from InTouch come in as stairstep instead of as system default.

L00153223

 

SR 103159212: Cannot fetch a row from OLE DB provider "INSQL" for linked server "INSQL".

L00153338

L00153474

SR 51314499, SR 51314499, SR 63910742: While processing between Historian and two remote IDAS, a disconnect sometimes causes NULL with quality value 10 (communication loss) to be inserted to the store-forward data.

Related Topics

Wonderware Historian

Wonderware Historian 2017 Update 3 SP1 P01

Copyright © 2020 AVEVA Group plc and its subsidiaries. All rights reserved.   |   Contact Us