Historian 2014 R2 SP1 P01

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

Wonderware Historian Server 2014 R2 (version 11.6.14101) SP1 P1

Wonderware Historian Server

In This Document

Wonderware Historian Server 2014 R2 (version 11.6.14101) SP1 P01

Wonderware Historian Server 2014 R2 (version 11.6.13100) SP1

Wonderware Historian Server 2014 R2 (version 11.6.14101) SP1 P01

Latest revision: 5/12/2016

About This Readme

This Readme provides information about Wonderware® Historian Server R2 SP1 Patch 1 (version 11.6.14101).

For information about using the product, see the Wonderware Historian Server documentation.

Included in This Patch

  • Wonderware Historian InSight

    This browser client included as part of Wonderware Historian Server is an on-premises version of Wonderware Online InSight (formerly Wonderware Online). It provides an easy-to-use graphical interface for analyzing data, creating charts, and compiling dashboards of related information. Once you save your content, you can share it with other team members or reuse it in other documents.

  • Support for reindexing tags

    Updates to the Configurator tool allow you to reindex all available tags at any time.

  • Case-sensitive engineering unit handling

    Historian is able to handle case-sensitive engineering units (also called units of measure).

  • Faster Tier 1 to Tier 2 replication

    This version of Wonderware Historian Server has improved replication rates.

    If you use replication, we recommend updating Tier 2 with the patch first, and then updating Tier 1 to the same version. For replication to work properly, Tier 2 must have the same or newer version of Historian compared to Tier 1. If you update Tier 1 before updating Tier 2, your data will be held in store-forward until both tiers are updated to the same version.

To open and use Wonderware Historian InSight in IE or Chrome

  1. Open Internet Explorer or Chrome, and then type the following URL:

    http://<servername>:32569

    where servername is the name of the Wonderware Historian Server.

  2. Select the menu icon from the upper-left corner, and then select Help for more information.

To open and use Wonderware Historian InSight in Firefox

  1. Open Firefox and, in the address bar, type:

    about:config

  2. If prompted, agree to the caution statement from Firefox3.x or later.
  3. After the configuration page loads, in the filter box type:

    network.negotiate-auth

  4. Edit the value for "network.negotiate-auth.trusted-uris" by double-clicking the row and typing the following :

    <servername>:32569

    Examples: "historiansvr01:32569" or "localhost:32569"

To reindex all existing tags

  • In Configurator, click the Historian Search node, select Reindex Search Documents, and then click Configure.

Additional Licensing Information Related to the Wonderware Historian Search Service

(Website addresses in this section are from the respective companies at time of publication and subject to change at owners' discretion.)

The Wonderware Historian Search Service, Copyrights 2016 - Schneider Electric Software LLC leverages third-party components as follows: 

  • Elasticsearch, developed by the Apache Software Foundation (http://www.apache.org)

    Copyright 2009-2015 Elasticsearch  (Elastic is a trademark of Elasticsearch BV)
    Licensed  under the Apache License, Version 2.0 (the "License").
    You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.

  • Java SE from Oracle 

    Usage of this component falls under the Oracle Java SE agreement (http://www.oracle.com/technetwork/java/javase/terms/license/index.html) with a specific emphasis on commercial use and additional third party software licenses:

    • Use of the Commercial Features for any commercial or production purpose requires a separate license from Oracle. "Commercial Features" means those features identified in Table 1-1 (Commercial Features In Java SE Product Editions) of the Java SE documentation accessible at http://www.oracle.com/technetwork/java/javase/documentation/index.html.
    • THIRD PARTY CODE. Additional copyright notices and license terms applicable to portions of the Software are set forth in the THIRDPARTYLICENSEREADME file accessible at http://www.oracle.com/technetwork/java/javase/documentation/index.html. In addition to any terms and conditions of any third party open source/freeware license identified in the THIRDPARTYLICENSEREADME file, the disclaimer of warranty and limitation of liability provisions in paragraphs 4 and 5 of the Binary Code License Agreement shall apply to all Software in this distribution.

Known Issues

  • Silent-mode installation of the Configurator is not supported for this patch.

    Note: If you use silent-mode installation for the patch, you must manually run the Configurator to configure the Historian and search indexing services.

  • For servers running Wonderware Historian Server 2008 R2 or 2012 R2, Wonderware Historian InSight will not work properly in Internet Explorer if IE Enhanced security is enabled on the server. For these configurations, you must use the Server Manager console to disabled IE Enhanced security.
  • Some charts are not drawn for complete time range if that range includes both daylight savings and standard times.

Resolved Issues In This Patch

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

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

L00134384

L00139445,
L00139791

SR 192111982: Network issues cause null values to be stored for certain tags with a QualityDetail of 20 (recovery without store forward).

L00136862

L00139482,
L00139952

SR 54010047: When a string or discrete tag is created with the SDK using the Delta+StorageRate feature, StorageRate is set to 0.

L00137622

L00137758,
L00139176

SR 20114915: Customer doesn't see values being propagating to Tier 2 Historian.
(This issue was previously resolved in WSP 2014 R2 SP1.)

L00138977

 

Import times for CSV files are offset by one hour for date time stamps from November 1, 2015 2:00 a.m. to November 8 2015, 2:00 a.m.

L00139228

 

Historian Replication is not working for some tags. Others may have stopped working.

L00139750

 

Historian SDK toolkit is experiencing a disconnection issue.

L00139775

 

Query results from the History table all include wwTagKey=0.

L00139793

 

Analog summary values don't reflect the correct value in the PercentGood column.

L00140188

L00140311

SR 103138819: On Engine Failover, a null value is stored for slow-changing tags.

L00140212

L00140344

SR 51311138: After reboot or shutdown of Historian, a strange value gets inserted into the CentralInSql tag.

L00140229

 

The store forward disk limit is ignored, resulting in a full disk.

L00140279

L00140396,
L00140526,
L00140588

SR 103139097: Historian does not import a store/forward block after the block failed to pass an integrity check.

L00140317

 

SR 103139074: The AlarmClient (historical mode) disconnects from the History block if a large query filter is used. This error message displays: "Exception in Getting Alarms from Query The remote server returned an error: (400) Bad Request."

L00140601

L00140874

Replication stops working when the rollover value configured for source tag is greater than maximum size of int.

L00140708

 

The Embedded Alarm Control (EAC) and the Alarm DB View A2ALMDB are missing milliseconds from timestamp. Instead, zeros are displayed in the milliseconds portion of the timestamp.

top of document

Wonderware Historian Server 2014 R2 (version 11.6.13100) SP1

Latest revision: 1/13/2016

About This Readme

This Readme provides information about Wonderware® Historian Server version 11.6.13100, which is part of the Wonderware System Platform 2014 R2 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 2014 R2 Service Pack 1 Readme.

Resolved Issues In This Service Pack

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

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

L00136837

L00137065

L00138395

L00138487

SR 103136762, SR 1192111704, SR 192111735:

Failed to create a Metadata Server session (error = 20, not ready). InTouch reimports corrupt TagHistory, which causes tag type and scaling factors (MinEU, MaxEU, NinRaw, MaxRaw) to work improperly.

Note that we have addressed the root cause for this issue. User must still delete any corrupt tags from the TagHistory table.

L00136862

L00137216

SR 54010012: Slow-changing values are deleted by block management and no longer available for retrieval.

L00137003

L00139052

SR 103135142: The remote IDAS does not reconnect after disconnecting from network.

L00137149

 

SR 103135467: The database import/export utility does not export Application Server tags with their tag IDs.

L00137194

L00137348

SR 103135321: OLEDB provider shows that it is stopped in SMC and all SQL queries to extension tables return an error. To recover, SQL Server must be restarted. (All other Historian services work as expected.)

L00137280

L00137701

SR 35312700: An attempt to resurrect from TagHistory fails and this message displays: "Failed to add historian after 3 attempts."

L00137297

L00137579

SR 103135688: Installation of Wonderware Historian Server 2014 R2 P1 causes a history block's size to dramatically increase.

L00137603

L00137927

SR 103135876: Analog data is inconsistently replicated.

L00137774

L00138249

SR 19818861: An alarm displays as attributename.msg if Historian is logging alarms to A2ALMDB.

L00137827

 

Configurator logs this error message during Historian Server configuration: "Unexpected exception verifying Authenticode of application"

L00137864

 

SR 10917339: In Wonderware Historian Server 2014 R2 P1, aaLogger displays this message for each invalid tagname in a WideHistory query: "ERROR: Invalid column DBTYPE 12 in WideHistory table"

L00138090

 

During installation, the Historian Configurator displays a warning message saying that the configuration is not complete, even if the Configurator runs successfully.

L00138198

L00138649

SR 103136625: Scaled Historian Tag values read with aahIOsvrsvc - FSGateway seem to be not scaled.

L00138280

L00138405

SR 103136656: When combining a mixture of good and bad qualities in the cycle, a counter query with Optimistic quality rule returns a good quality instead of "uncertain".

L00138487

L00138639

SR 54810098: Repeated Historian warning errors are shown in the logger for various tags. For example: "StartDataRetrievalQuery failed..."

L00138592

L00138610

When importing scaled tags from InTouch history LGH files, double-scaling conversion occurs.

L00138626

 

L00138941

SR 103137059: When configuring Historian to log alarms, if the alarm filter includes a special character (such as "#"), the remote server returns this warning: Exception in Getting Alarms from Query / The remote server returned an error: (500) Internal Server Error.

L00139046

L00134730

L00139050

L00139051

SR 49410145: After applying a recent hotfix (L00134730), a query using integral retrieval mode results in a bad value.

L00139220

 

SR 103137726: After restarting, remote IDAS ignores deadbands for tags.

L00139312

 

SR 103137863: Losing and reestablishing a connection with Historian briefly before SF_MinTimeReached is reached causes the store-and-forward duration to increase. This happens because the server then must process a larger number of snapshots at the same time, thus retrieval is slower.

top of document

Avantis  |   SimSci  |   Skelta  |   Wonderware   |  Contact Us