ClearSCADA

Please read the information below prior to installing ClearSCADA 2017 for important information on any known issues.

Issue when using Windows 10 Creators Update - build 1703 (issue reference: SUP-9419)

A problem has been identified within WebX clients after upgrading to the Windows 10 Creators update build 1703 whereby the scroll bars on an embedded list control (e.g. SQL Query, Event List, Alarm List on a mimic) in WebX no longer work as expected. We are actively working with Microsoft on this problem, which has been recently confirmed as an issue in MS Internet Explorer. MS Issue Reference: REG 117052415792436.

Current advice for ClearSCADA customers using WebX is that they should avoid upgrade of their Windows 10 clients to Creators Update build 1703 until this issue is resolved.

Customers impacted by the above are encouraged to raise this directly to Microsoft via their Support Channels, quoting the Issue Reference: REG 117072016066603, to help facilitate a timely resolution.

Recent testing has uncovered a potential work-around; when using Google Chrome browser and the IE Tab Extension (which simulates an Internet Explorer browser) version 10.7.31.1 we were able to successfully use the embedded mimic's scrollbars. The following considerations apply:

  • We have not formally tested WebX using Google Chrome’s IE Tab Extension.
  • Using Chrome web browser may be a problem for some customers (e.g. a Security Policy might exclude the use of Google Chrome browser, or the extension kits)
  • The extension may be using an older version of Windows library, and a newer version of the extension might reveal the problem again.

Thanks for your support, but overall we apologize for any inconvenience.

User Interface

Blurry Maps and/or Lists on high DPI displays using Text Scaling

High resolution displays that are configured to use Text Scaling can result in displays of ClearSCADA's Map Displays and Lists to be noticeably pixelated and blurry. The impact for Map Displays is aesthetic only and should not impact useability, however applying non-standard scaling impacts the display of Lists because the table content becomes too wide for the column width, obscuring some content from view.

Annotation not translated in WebX trends

Translated strings for a user with the user set to the locale for those translations, a trend created and an internal digital point's processed history trace added to it. Annotations are then added to the trend with the translation string: @this. ViewX and original WebX displayed the translation for @this correctly, but (new) WebX displays @this instead of the translation for @this.

Text Alarms not displayed within the WebX Alarm Banner

Text alarms are not displayed within the HTML5 Alarm Banner in WebX.
Text Alarms are typically associated with Server Licensing, Archiving, or Historic Granule Monitoring Alarms, although can also be generated by some drivers or via methods in Logic and Scripting. These Text Alarms are displayed correctly within the Embedded Alarm List.

User Authentication

Username Case Sensitivity (issue reference SUP-9320 & SUP-9324)

An issue has been identified that can cause either an "Access Denied" error and consumption of a WebX license, or display of an "Web Server license limit exceeded" error when attempting to execute mimic scripts after user login, which impacts:

  • Users using External Authentication where the User Account object's name isn't identical to the configured Windows/LDAP Username, and
  • Local users (managed by ClearSCADA, without External Authentication) if they do not pay attention to letter case (e.g. specific use of uppercase and lowercase characters, etc) when entering user name, even if Case Sensitive Usernames is unchecked in the ClearSCADA Server Configuration settings.

This issue has been investigated, and the following immediate work-arounds have shown to be effective:

  1. Ensure the username entered during login matches (including the letter case) the ClearSCADA user object name regardless of the user type (Local User Account or External User Authentication).
  2. If using External Authentication, login using the name of the ClearSCADA user object rather than the Windows/LDAP Username if they are different.

Crystal Reports

A problem with exporting Crystal Reports on Windows 8 and 8.1, and Windows Server 2012 and 2012 R2 has been identified. It is triggered by the report containing Boolean parameters with the "Exclusive group" option enabled. Subject to confirmation, the likely cause is the SAP crystal runtime rather than ClearSCADA 2017.

Installation

OPC Registration

On a clean installation of ClearSCADA 2017, the classes for OPCDA, OPCAE and OPCHDA are not registered. The user would need to open the Client Configuration dialog and click OK on the configured connection for the classes to be registered. This was changed to add support for the Systems.xml file.

Wonderware Historian (issue reference SUP-9319)

An issue has been identified within the Wonderware Historian (WWH) interface whereby it does not operate correctly after upgrade to ClearSCADA 2017 and causes a ClearSCADA server exception when starting the database. 

This can be resolved by performing a "repair" on the ClearSCADA 2017 Server installation in Windows Control Panel. After a repair of the installation has been performed, a restart of the ClearSCADA server should result in successful system operation.

Support for Internet Explorer 9/10/11

The following problems were identified:

  • When clicking on the 'List All <class> Objects' from a class information page in the database schema, the list of objects may not display correctly. This is a problem with the Internet Explorer's XSL transformation related to elements with content and children.
  • Script functions such as 'Mimic.OpenInset' and 'App.OpenWindow' may not display properly on IE9/10/11.
  • Hyperlinks to lists may not display correctly due to the cross site scripting security filter in Internet Explorer. This also includes links to trends generated using the TrendSpec specification in ClearSCADA. The workaround for this is to disable the Cross-Site Scripting (XSS) filter in the web browser.