Historian Server 2017 UPDATE 1 Readme

Posted on 613 views

About This Readme

This Readme provides information about Wonderware® Historian 2017 Update 1 (version version 17.1.000).

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

New Features In This Release

The Wonderware Historian 2017 Update 1(version 17.1.000) includes these features:

  • Autosummary backfill
    Beginning with Wonderware Historian 2017, an auto-summary feature provides the creation of auto-summary values for your analog tags. This dramatically reduces the time needed for data retrieval.
  • This release provides a Replication Backfill Manager. You can use this utility to backfill auto-summary values for time periods before Wonderware Historian 2017 was installed.
  • Block gap behavior
    Wonderware Historian is designed to store data in a contiguous series of history blocks. But there are two cases that may result in block gaps — that is, gaps between the history blocks:

    • If no data was acquired for the timeframe corresponding to a particular history block, that block will not be created.
    • If a history block is deleted for whatever reason, a block gap will result.

    By default, gaps in data are charted (for example, by Trend and InSight) as straight lines. If you want data gaps to display as empty, you can change the default using either a wwOption parameter called “BLOCKGAPS” or Windows Registry settings.

  • New Wonderware Historian InSight features
    Including:

    • Events — Your InSight charts can now include events captured through Wonderware Historian replication or the Wonderware Historian SDK.
    • Chart URL — You can create an InSight chart from a URL query. This is useful when you want to trigger the creation of an InSight chart from another application.

Known Issues

  • In Wonderware Historian InSight, if a tag name includes an HTML-specific character, such as < or >, it will not be shown in the search results.

Resolved Issues In This Release

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

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

L00145315

L00146140

SR 37511227: Tag search in Historian InSight is inconsistent.

L00145316

L00146141

SR 103141118: Migrate L00140741 and L00141226 to Patch1

L00145317

L00146142

SR 51311709: Historian reports this error: “Main Metadata Server failed to copy”.

L00145319

L00146146

SR 103141718: Historian InSight leaks memory in aahClientAccessPoint.

L00145320

L00146145

SR 50410723: When the search index translog file grew to 20G, it caused Historian to stop collecting data.

L00145321

L00146147

SR 54810238: The logger has warning messages saying “GetNextDataQueryResult failed”.

L00145322

L00146150

SR 51311862: The aahEventStorage.exe services are consuming a huge amount of memory.

L00145333

L00146148

SR 103142832: Some alarms are written in wrong order regarding AlarmState in A2ALMDB.

L00145337

L00146143

SR 103143213: v_AlarmHistory can’t handle more than one “like”comparison.

L00145338

L00146144

SR 192112349: aahIOSvrSvc returns the most recent value possible regardless of whether it is a streamed or store-forward value.

L00145339

L00146139

SR 50410945: Historian InSight can’t save a chart that contains a tag with engineering unit as “Hg”.

L00145340

L00146138

SR 48911639: If a user logs into Historian InSight but doesn’t belong to the same domain as Historian Server domain, InSight generates an “HTTP 500 Internal Server Error” message.

L00145369

L00146137

SR 103143736: The import process will fail for one tag if you try to import two tags with matching item names from different InTouch applications on different nodes. Only one tag is imported.

L00145380

L00146135

SR 48911430: The tagname for an alarm is recorded differently in A2ALMDB compared to WWALMDB.

L00145618

L00146086

SR 103140943: Remote IDAS shows it isconnected, but Historian show it as not connected.

L00145670

L00146558

SR 103145587: An issue exists with event tags after update.

L00145727

L00146297

The upgrade process generated a large number of warnings in the logger.

L00145765

L00146294

Alarms with a “UNACK_ALM” or “ACK_ALM” alarm state are missing when the v_AlarmEventHistoryInternal2 view is executed.

L00145827

L00146296

The Tag Rename utility (aaTagRename.exe) failed to rename tag that contains invalid characters.

L00145915

L00146325

SR 10917896: Historian Event Storage service takes up over 50% of CPU.

L00146008

L00146136

SR 35313276: The syntax “Insert into History where…” does not work.

L00146012

L00146085

SR 103138819: On engine failover, a null value is stored for slow changing tags.

L00146013

L00146084

Historian storage crashes on startup because of a corrupt history block.

L00146030

L00146594

SR 50411007: Trend doesn’t display data correctly when it comes from history blocks generated by different versions of Wonderware Historian.

L00146038

L00146295

Historian InSight doesn’t show saved content and keywords in its search results.

L00146049

L00146508

SR10917923: Historian has problems importing very large .LGH data files.

L00146071

L00146438

SR 103146311: An error was generated, saying “Failed to import store/forward block”.

L00146083

L00146450

SR 103146237: The product does not display properly in Windows 10.

L00146351

L00146393

SR 59210067, SR 47710038: When the Historian server is shut down and disabled, the Historian license is not forced back to the license server.

L00146448

SR 50313505: Selecting the built-in OI Server names from the I/O Server type list doesn’t work because IDAS requires an application name for communication, and not EXE name.

L00146463

L00146548

SR 50310785: Switching an I/O server from one remote IDAS to another using drag and drop doesn’t work.

Related Topics

Wonderware Historian

Wonderware Historian 2017

Wonderware Historian 2017

Latest revision: 3/16/2017

About This Readme

This Readme provides information about Wonderware® Historian 2017 (version 17.0.18000).

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

New Features In This Release

The Wonderware Historian 2017 (version 17.0.18000) release includes these features:

  • Updates for Wonderware Historian InSight
    This version these new InSight features:

    • Dashboard enhancements (customization and auto-refresh
    • Ability to plot discrete tags
    • Pan and zoom in line charts
    • Multi-axis and stacked tags mode in line charts
  • Enhanced auto-summary system
    Provides fast data retrieval, even for long data periods
  • Alarm and Events replication
    This version includes replication support to on-premises tier-2 servers or Wonderware Online InSight.
  • Cyber-security improvements in reducing Admin privileges needs
  • Support for Historian using a SQL Server instance
  • A new Schneider Electric licensing infrastructure
    Licensing is now server-based. A centralized license management system offers license server auto-detection and configuration for servers running Wonderware Historian 2017.

Known Issues

  • For servers running Wonderware Historian 2008 R2 or 2012 R2, InSight browser will not work properly if Internet Explorer Enhanced security is enabled on the server. For these configurations, you must use the Server Manager console to disabled IE’s 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 Release

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

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

L00135973

L00137532,
L00144021,
L00144104

SR 49410191, SR 49410040: “Administrators” group share permissions exist on InSQL8SF$ share name.

L00140741

L00141226,
L00141795

SR 103141118: (aahIOSvrSvc) When a tag is added that doesn’t exist, every tag after that will have bad quality.

L00140841

L00144160

SR 49810065: When using the Alarm system, an issue exists with AlarmDuration field.

L00140969

L00144161

SR 34114189: A query that uses Daylight Saving Time results in an error

L00141025

 L00142313

SR 103141718, SR 10917557: ClientAccessPoint leaks memory for ExecuteSqlStatement calls.

L00141226

L00144299

SR 103140340: When a tag from InTouch (via aahiosvrscv ) that didn’t previously exist in Historian is received, evey good tag added after that is marked as having bad quality.

L00141394

 L00143988

SR 192112147: Historian Data Importer crashes during the data import.

L00141495

L00141767,
L00142112

SR 103140601: Incorrect values for Query or Trend for “Latest” data after upgrade to 2014 R2 SP1.

L00141426

 

SR 37511227: Tag search is inconsistent in Wonderware Historian InSight (on-premises).

L00141506

 

SR 50410723: Search Index Translog file grew to 20G, causing Historian to stop collecting data.

L00141611

 

SR 51511796: Unable to access to Historian Online via OData interface after upgrading to SP2014R2SP1P01.

L00141649

 

SR 37511215: Counter query returns inconsistent data when timeframe changes

L00142080

 

SR 51311709: Two warnings showing up once per hour. Both include this text: “Main Metadata Server failed to copy…; last error = 80 (The file exists)”.

L00142231

L00142489,
L00142599

SR 51311862, SR 103141794: A huge amount of memory consumption occurred for aahEventStorage.exe services.

L00142287

L00144218

SR 103141346: When a customer changes an event tag configuration, the event history sends the wrong email messages.

L00142298

 L00143588

SR 54810238, SR 103143174: Warning messages are displayed in the logger: GetNextDataQueryResult failed (79;”Date and Time” –> <INFINITY>… error = 51 (Unknown client)

L00142674

 

Historian should support Min/Max Raw and Min/Max EU where the “min” is greater than the “max”

L00142820

 

SR 10917696: OData query returning duplicate tagname records.

L00142935

L00144145,
L00144146,
L00144090,
L00144091

SR 48911529: When the Alarm DB Logger Manager isn’t used, historical alarms from Application Server don’t have the “Tagname” field populated with the object name that generated the alarm.

L00143133

 

SR 48911458: While trying to run a query, the “GetNextDataQueryResult failed” warning posts to the SMC log and query fails.

L00143230

 

SR 103142952: Installing the patch Historian Search (64 bit) fails and returns code 1603.

L00143237

 

SR 103142832: (A2ALMDB) Some alarms regarding AlarmState are written in wrong order.

L00143436

 

SR 103143213: v_AlarmHistory supports only a single “like” comparison.

L00143664

 L00142523

SR 103140324: A racing issue occurs while creating the server storage node.

L00144023

 

SR 103143833: A constant growth of handles and the private memory set occurs on dnx. exe.

L00144228

 

SR 19714377: Tier-2 value of One Minute (1M) replicated analog tags is one value behind the current tier-1 value.

Leave a Reply

Your email address will not be published. Required fields are marked *

× 7 = 56