Wonderware Historian Server 2014 R2 (version 11.6.13100) SP1

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.