Last revision: 11/9/2017
This document contains important information about Wonderware System Platform 2017 Update 1. This update of Wonderware System Platform 2017 includes a software development kit (SDK), and new features and enhancements for the component products of Wonderware System Platform.
You can upgrade directly to Wonderware System Platform 2017 Update 1 from the following versions:
Server-based Licensing
Wonderware System Platform 2017 Update 1 utilizes the new server-based licensing subsystem introduced in Wonderware System Platform 2017. This new licensing subsystem provides centralized license management, and replaces the file-based licensing system that was used in prior releases. Licenses must be activated before use.
If you are upgrading from Windows Server 2014 R2 SP1 (with or without patches), you must first install and configure a license server node, and activate the licenses to ensure continuous plant operation. The license server is typically installed on the Galaxy Repository node, but you can use a dedicated license server. See the "License Installation and Activation" section of the Wonderware System Platform Installation Guide (WSP_Install_Guide.pdf), located at the root of the DVD.
InTouch OMI
Wonderware System Platform 2017 introduced InTouch OMI, the first Operations Management Interface to leverage both Human Machine Interface (HMI) and Supervisory Control and Data Acquisition (SCADA) systems and deliver a next generation visualization experience. Key features added for Update 1 include a Software Development Kit (SDK) to allow programmatic additions to InTouch OMI.
InTouch OMI extends traditional HMI and SCADA applications to deliver a convergence platform for both Operational Technology (OT) as well as Information Technology (IT).
One key aspect of InTouch OMI is its ability to automatically assemble applications based on a data model, resulting in minimal engineering and manageability that has not previously been available.
InTouch OMI enables the first industrial application that will deliver a tailored and contemporary experience to any environment or device, including control rooms, industrial panels, desktops, laptops, tablets and phones.
Readme Files for Other Products in this Release
To access individual product Readme files, insert the Wonderware System Platform installation DVD and click on the link. Review the known and resolved issues contained in each Readme file for the following component products are updated for this release:
The Wonderware InTouch Access Anywhere Readme file is included at the end of this Readme.
When InTouch HMI 2017 Update 1 is installed on a Windows Server 2016 system with Remote Desktop Services enabled, WindowViewer will fail to launch. WindowMaker cannot be closed unless shut down using Task Manager.
Workaround:
http://www.catalog.update.microsoft.com/Search.aspx?q=KB3194798
Important: You can install the Microsoft update before or after Wonderware System Platform. However, we recommend installing the Microsoft update before you install Wonderware System Platform.
For important information about this product release, go to the Schneider Electric Software Global Customer Support (GCS) web site. Information on the GCS web site includes product requirements, compatibility, as well as downloads from previous releases. After you log in, you can filter search results by product name and the release/version.
System Platform 2017 Update 1 provides several significant new features and product enhancements.
Software Developer Kit
See New Features in Wonderware InTouch OMI 2017 Update 1 for more information.
Enhanced Product Integration
System Platform 2017 provides a tighter level of integration between its component products. This improved integration between components increases usability, functionality, and performance.
Enhanced Security
System Platform 2017 is more secure than ever. Security enhancements have been added to this release of Wonderware System Platform and its component products.
Centralized License Management
All products included with Wonderware System Platform 2017 now leverage the server-based Schneider Electric Licensing System.
InTouch OMI ViewApp
The InTouch OMI ViewApp, an advanced visualization HMI component, is now integrated into Wonderware System Platform to provide enhanced visualization, graphics management, and other functions and capabilities. Features include:
Note: In this release, InTouch OMI ViewApps do not automatically populate the InTouch Access Anywhere applications list.
Resolution Independence for Displays
InTouch Operations Management Interface eliminates the need to configure run-time graphic elements for specific screen resolutions and configurations. Multiple form factors (including (phones and tablets), screen resolutions, aspect ratios, and multi-monitor displays can be used, and content will automatically resize to fit the target screen.
Support for Touch-Enabled Displays
The InTouch OMI ViewApp supports touch and multi-touch gestures, such as pan, zoom, swipe, close, and double-tap. Automatic detection of touch-screen devices is built-in.
Application Server 2017 Update 1 provides support for the latest versions of Microsoft products, and adds a Software Developer Kit that lets you create your own InTouch OMI apps.
Software Developer Kit
The most significant new feature in Wonderware System Platform 2017 Update 1 is the release of the Software Developer Kit as an installable component. This lets you build your own .NET-based apps for use in your InTouch OMI ViewApps, and interface directly with a number of integrated APIs and SDK namespaces, as well as a number of sample applications.
The InTouch OMI SDK installs automatically when you install the Wonderware Application Server IDE component. A link has been added from the Start Menu to the SDK help (Start > Wonderware Documentation > InTouch OMI SDK Help).
Integrated Apps
InTouch OMI now includes built-in apps to simplify the task of building full-function ViewApps. Among the built-in apps are apps for ViewApp navigation, for displaying geographical information (MapApp), an alarm app, and a historical playback app.
Enhanced Alarm Aggregation with Dynamic Navigation
In addition to showing alarm severity, status and number, alarm aggregation now lets you quickly select, via built-in navigation, the area or object that is in alarm and respond to it.
InTouch 2017 Update 1 provides support for the latest versions of Microsoft products and includes several new features. Refer to the GCS Technology Matrix for the list of supported Microsoft products. The following section summarizes the major features introduced in InTouch 2017 Update 1.
InTouch Web Client
The InTouch Web Client provides access to running InTouch HMI application using any major HTML5 web browser from a server or client computer. No special hardware or software are needed to support the Web Client. Users simply use their web browser to show a log on page to authenticate themselves and view a running InTouch application in read only mode.
A single user can access the Web Client if it is unlicensed. Multiple concurrent users can access the Web Client after it is licensed.
For more information on the InTouch Web Client, see Viewing InTouch Application Graphics in a Web Browser (ITWebBrowser.pdf) in your Wonderware installation location. The typical installation location is: C:\Program Files (x86)\Wonderware\InTouch.
Cross Reference Utility
The standard InTouch Cross Reference utility has been significantly enhanced to include ArchestrA symbols in an application's standard InTouch tag cross reference list. A cross reference search for ArchestrA symbols can be conducted by the criteria shown below, which will be included as part of the Cross Reference utility's InTouch Tag Use.
Script Editor Search and Replace Utility
The InTouch Script Editor has been enhanced with a Find and Replace utility to search a script based upon an entered search string. The Find utility includes a set of options to search by string case, conduct a directional search, or only search within a selected area of the script. The Find utility also includes the capability to select a type of search, including wildcard and regular expression searches.
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
The requirements for using Admin privileges are reduced.
Support for SQL Server instances
Support has been added to allow Historian Clients to use a SQL Server instance to connect to the Historian.
Updates for Wonderware Historian InSight
Web Help - Browser-based User Assistance
Web help components have been delivered in this release. Web help opens in the default browser on your local computer. Help displayed in a browser allows more dynamic and searchable user assistance including standard web browser navigation and tutorial videos.
Typically, help content is installed on your local machine as part of the documentation library, and displays in your browser without requiring an Internet connection. To open the help, use one of the following methods (depending on the editor/UI you are using):
C:\Program Files (x86)\ArchestrA\Framework\Docs\1033\NGX\index.htm
Browser Requirements and Recommendations
Internet Explorer is recommended. You can also view web help Firefox. If you use Firefox, you may need to install and use an IE rendering extension (for example, IE Tab) to ensure that video content is shown.
Browser Permissions for Displaying Web Help
Each browser and Windows operating system combination has its own security permissions. Using Internet Explorer (version 8, 10, or 11) as an example, you may see a dialog requesting you to "Allow blocked content" each time you invoke the web help. This dialog is triggered by the presence in the help system of JavaScript components that control internal navigation and topic display elements such as pop-up or in-place-expanding display blocks that contain text and graphical images. The text and image content is itself non-active.
You can accept each occurrence of this dialog, or you can set the following option in Internet Explorer, depending on your IT security requirements: In Internet Options, click the Advanced tab, then navigate to the Security section. Enable the "Allow active content to run in files on My Computer." Permissions and security settings will vary depending on your specific browser.
Playback of Tutorial Videos
The web help may contain a number of brief tutorial videos. To play these videos, you must have Microsoft Media Player installed on your local machine. In Windows Server operating systems, you must enable the "Desktop Experience" feature using Server Manager.
Internet Explorer (or IE-rendering in other browsers) may be required for viewing video content. If using a browser other than Internet Explorer without IE rendering enabled, videos may not be visible.
Windows operating systems and SQL Server versions may impose hardware requirements that exceed the minimum requirements for Wonderware Application Server 2017 Update 1. Refer to the following Microsoft Web sites for Windows and SQL Server hardware requirements.
Windows requirements
Note: Wonderware System Platform 2017 Update 1 is not supported on Windows 10 versions prior to version 1607 (Anniversary update; OS build 14393).
SQL Server requirements
For system sizing examples, see the Wonderware System Platform Installation Guide.
The latest product information for each Wonderware System Platform product is listed in the Global Customer Support (GCS) Technology Matrix. Each link includes:
Minimum Required Operating System Version
The following table shows the minimum operating system for each product. See the GCS Technology Matrix for a list of all supported operating systems.
Product |
Minimum Required Operating System Version |
|
Client OS (x86 and x64) |
Server OS (x64 only) |
|
Windows Server 2012 (Embedded or Data Center) |
||
Wonderware System Platform 2017 Update 1 web clients
The following web clients are included with Wonderware System Platform 2017 Update 1:
The client programs listed above can be used with most common web browsers. Compatible browsers include:
System Requirements by installation size
Small installation (1 to 25,000 I/O per system):
Medium installation (25,000 to 50,000 I/O per system):
Large installation (50,000 to 400,000 I/O per system):
When installing SQL Server, use the program version (32 or 64-bit) that matches the operating system.
Upgrading SQL Server with Wonderware products installed is supported.
The following virtualization software and cloud-based virtual environments are supported for Wonderware System Platform 2017 Update 1:
In order to establish communication with other components and services on the network, Wonderware System Platform (WSP) and ArchestrA Service Bus (ASB) services require certain network ports to be opened in the Windows Firewall. Typically, these ports are automatically opened for the Windows Firewall during installation. However, if the Windows Firewall service is disabled or not running at the time of installation, or if an alternative firewall is in use, you will need to manually open the appropriate network ports in the firewall. For more information about port configuration, see "Configuring ArchestrA Service TCP Ports" in the Wonderware Application Server User Guide (filename: IDE.pdf).
Due to the Data Execution Prevention (DEP) feature in Windows operating systems, any ActiveX control built with ATL version 7.1 or earlier will fail to host, or will behave unpredictably in InTouch, either in WindowMaker or WindowViewer.
The ActiveX controls and error message, along with solutions to resolve the behavior, are described in detail in TechNote 522, "Some ActiveX Controls NOT Supported in InTouch 2012 R2 (Version 10.6)". You can download this TechNote from the Schneider Electric Software Global Customer Support (GCS) website.
The process to configure remote alarm retrieval queries has changed for interactive applications such as InTouch HMI when running on currently-supported Windows and Windows Server operating systems.
When InTouch WindowViewer is started and generates alarms from an interactive Windows or Windows Server desktop session, an AlarmViewer control (running within InTouch HMI) on a remote node must be specially configured to query the alarms. The source alarms will not appear unless the AlarmViewer control's alarm query is configured.
This type of query only works for InTouch HMI as an alarm provider running in a Terminal Services session, not for InTouch HMI running in a console session.
To configure the AlarmViewer's alarm query
\\nodename:ip_address\intouch!$system
where nodename is the name of the node that is providing the InTouch alarm and ip_address is the IP address that you determined in step 1.
Windows Server 2008 R2 and later operating systems no longer support the /console switch as a means of starting the remote desktop (RDP) client, also known as Session 0 or Terminal Server Console session. In Windows Server 2008 R2 and later operating systems, Session 0 is no longer an interactive session, and is reserved only for Windows services. Windows Server 2008 R2 and later operating systems treat all remote connections as remote RDP sessions regardless of /console, /admin, or any other switches used to make the connection.
This impacts InTouch HMI functionality such as Alarm Manager that depends on the Terminal Server Console session. The impact to Wonderware Application Server is minimal as most Wonderware Application Server processes run as services. One impact to Wonderware Application Server is to carry forward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. While both Wonderware Application Server and InTouch HMI can be configured as alarm providers, only one alarm provider can be configured at any one time.
Refer to the Wonderware InTouch HMI Readme for further information about InTouch HMI applications running in the Terminal Server Console.
If you are running WindowViewer within a Terminal Server session and want to access alarms from WindowViewer in a client session, you must use the syntax \\terminalservernode:<IP address>\InTouch!$System to access the alarms, with a colon (:) after the node name. The IP address is that of the client computer connected to the session.
NetDDE is not supported for InTouchView applications.
By design, an InTouchView application does not serve data to any other source, including InTouch HMI itself. When WindowViewer starts, it verifies if the application is an InTouchView application. When WindowViewer detects an InTouchView application, it does not register to become a DDE server. ArchestrA Symbols make use of the client layer when accessing InTouch tags, and appear as a third-party client trying to access WindowViewer as a data server. As a result, ArchestrA Symbols cannot communicate with InTouch tags when used with an InTouchView license.
In ArchestrA Symbols, InTouch:‹tagname› is still a valid method of referring to an InTouch tag on a local node.
Wonderware System Platform 2017 Update 1 with InTouch HMI 2017 Update 1 supports User Account Control-enabled operations on run-time nodes.
This section describes specific behaviors and restrictions when using the supported versions of Windows and Windows Server operating systems with Wonderware Application Server.
Wonderware Application Server supports User Account Control-enabled operations. Starting the IDE requires elevated privileges.
Scenarios involving remote node communication fail if the Historian node is using the Windows 7, Windows 8, Windows Server 2008 R2, or Windows Server 2012 operating system.
For example:
Workaround:
cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
This sets LocalAccountTokenFilterPolicy registry entry value to 1. In doing so, an elevated token for the user is generated.
When the Wonderware Historian Client application is running on Microsoft Windows 7, Windows Server 2008 R2, and later operating systems, User Account Control can be enabled and running as non-administrator.
IMPORTANT: Wonderware System Platform 2017 Update 1 installs .NET 4.5.2 if the currently installed version of .NET is 4.5 or lower. If .NET 4.5.1 or later is installed, no change is made to the .NET Framework. Prior to upgrading your existing applications to Wonderware System Platform 2017 Update 1, we strongly recommended that you:
After upgrading to Wonderware System Platform 2017 Update 1, you should perform application testing on application scripts and on script libraries used by the application to ensure they continue to function properly under .NET 4.5.2. We also recommend you test the upgrade in a staging system prior to upgrading your production system.
Wonderware System Platform 2017 Update 1 leverages Microsoft .NET Framework 4. The Wonderware System Platform installation program will install .NET 4.5.2 if your system uses version 4.5 or lower. No change is made if your system uses .NET 4.5.1 or higher. Multiple versions of the .NET Framework can coexist. On nodes where SQL Server is installed, .NET 3.5 is also installed by Wonderware System Platform to support SQL Server. In this scenario, other applications you have on the same machine with dependencies on .NET 3.5 will access .NET 3.5. Wonderware System Platform 2017 Update 1 will use .NET 4.5.1, 4.5.2, or later.
All user-supplied .NET code that runs in the context of InTouch HMI and Application Server requires .NET Framework 4.5.1 or higher. Although .NET Framework 4.5.1 (and later) is highly compatible with applications that are built with earlier .NET Framework versions, you may have to update your scripts, if your .NET scripts were created prior to Wonderware System Platform 2014. These changes may also affect .NET controls developed with .NET 3.5.
In ArchestrA scripting, some .Net codes could fail if not using proper text encoding, and could cause a script to exit without completion. The UTF8Encoder is the default BinaryStream decoder in .Net 4.5. To enable an ArchestrA script to decode ASCII XML data, for example, insert the following snippet:
BinaryReader streamReader = new BinaryReader(ms, new ASCIIEncoding());
To learn more about changes introduced in different versions of the .NET Framework, refer to the following Microsoft resources:
What's New in the .NET Framework: |
http://msdn.microsoft.com/en-us/library/ms171868%28v=vs.110%29.aspx |
What's obsolete in the .NET Framework Class Library: |
https://msdn.microsoft.com/en-us/library/ee461502%28v=vs.110%29.aspx |
Migration Guide to the .NET Framework 4.6 and 4.5: |
https://msdn.microsoft.com/en-us/library/ff657133%28v=vs.110%29 |
.NET Framework 4 Migration Issues: |
http://msdn.microsoft.com/en-us/library/ee941656%28v=vs.100%29 |
SQL Server is required for Application Server, InTouch, and Historian Server. We recommend that you install and configure the supported SQL Server version before you begin the Wonderware System Platform installation program. If you select SQL Server Express during Wonderware System Platform installation, it will be installed automatically (applicable to small installations only).
The Wonderware System Platform installer will install all prerequisites except the SQL Server requirement for installing the Historian Server. If you select the Historian Server for installation, and if the supported version of SQL Server is not already installed, you must exit the installation program, install the supported SQL Server version, then resume the installation.
Other considerations are:
If you accidentally delete the aaAdministrators group from the SQL Server security logins, you must run the aaConfig SQL Utility to restore it. Refer to the Wonderware Application Server User's Guide, "About ArchestrA User Accounts", for further information and procedures about restoring the aaAdministrators group.
For Wonderware Historian Client:
For detailed installation instructions in English, see the Wonderware System Platform Installation Guide (WSP_Install_Guide.pdf) or Wonderware System Platform Installation Help (WSP_Install_Guide.chm). This guide supersedes the separate installation guides for the individual products. The Installation Guide pdf file is located in the root directory of the Wonderware System Platform installation DVD. The Installation Help chm file is located in the InstallFiles directory of the installation DVD.
The information provided in this Readme file and the InTouch Readme file supersedes the InTouch HMI Installation Help (Install-InTouch.chm) for the French, German, Japanese, and Simplified Chinese languages.
The ArchestrA user account is a user name and password combination that enables inter-node communication between all computers in an ArchestrA environment. You must specify the same user account on every node when you install the Wonderware System Platform components for the first time on computers that communicate with each other.
WARNING! The ArchestrA user account is a Windows operating system account located on the local computer or on a domain. Do not delete this account with operating system account management tools. If you do, ArchestrA-enabled software may stop functioning properly.
If the ArchestrA user account has not previously been configured, you will be prompted to configure it during the Wonderware System Platform installation. You must specify a user name, password, and domain.
If you choose to use an existing user account, it should meet the following requirements:
After you install a Wonderware System Platform component, you can use the ArchestrA Change Network Account utility to change or re-create the ArchestrA user account. This utility is located in the Common folder after you install InTouch HMI. You must have Administrator privileges on the computer to make changes with the Change Network Account utility. For more information, see the Change Network Account utility help.
Note: If you re-create the user account using the Change Network Account utility, the Microsoft Windows security component on the computer can take several minutes to update this information on the ArchestrA Galaxy node. Until that occurs, the ArchestrA component may not function properly. Restarting the Galaxy node updates this information immediately.
You can upgrade directly to Wonderware System Platform 2017 Update 1 from the following versions of Wonderware System Platform:
Upgrading is defined as installing a newer version of the software when a previous version of the software exists. An upgrade is possible when the system requirements (operating system, SQL Server, .NET Framework) are met. The upgrade process will properly remove or uninstall the previous software version and install the new version. For versions older than the current and previous licensed versions, only the latest service pack or patch versions are tested. For distributed systems, some products must be upgraded in a particular order. For more information, see upgrade information for each product in the Wonderware System Platform Installation Guide.
The earliest versions of Windows that support Wonderware System Platform 2017 Update 1 are:
See the GCS Technology Matrix for complete information about operating system that you can use for Wonderware System Platform 2017 Update 1 products.
IMPORTANT! Back up any relevant application configuration files or databases before you start an upgrade or migration.
Once installed, the Schneider Electric License Manager can be found in the \Schneider Electric folder on the Start menu.
It can also be accessed by pointing your browser to the following URL:
http://<nodename>/SELicenseManager
<Nodename> is the name of the node where Schneider Electric License Manager is installed.
The Schneider Electric License Server can be installed separately from the Schneider Electric License Manager.
Antivirus Software should be implemented as part of a defense-in-depth strategy to secure your Industrial Control Systems.
Please visit https://www.wonderware.com/contact/contact-support/ to get the latest information on Antivirus Software recommendations.
This section documents important resolved issues broadly categorized as Wonderware System Platform-level issues. This list is not comprehensive. Additional resolved issues are documented in the product-specific Readme files.
Original Change Request |
Related Change Requests |
Description |
L00123475 |
|
Two instances of user-configurable ASB services could not be assigned to the same port number. ASB 4.2 allows port sharing; therefore, this issue no longer exists. |
L00140327 |
L00131451 |
SR 52312289: Nuisance warnings related to the communication object were logged from the aaServicesDeployAgentHost. There was no affect on operation. |
L00140756 |
L00140757 L00142296 |
SR 103138526; SR 103137662: Intermittent warnings were logged that stated, "unable to connect to local galaxy server on node: <ip address>." |
L00141009 |
L00141381 |
The memory usage of MxAccess increased each time AuthenticateUser was used. |
L00141385 |
|
After upgrading central galaxy repository nodes from Wonderware System Platform 2012 R2 to Wonderware System Platform 2014 R2, remote GR nodes stopped communicating with the central nodes. |
L00142323 |
|
SR 103139802; SR 103140314: OPC UA clients and ASB services could not reconnect after the OPC UA server had stopped and restarted. |
L00142611 |
L00142612 |
SR 48410358; SR 48410390: In an environment with galaxies running on different, untrusted domains, Config and Browsing Services would hang if the service discovery dialog was launched from the IDE. |
L00143688 |
|
SR 103143440: An OPCUA Client could not read a valid string array from an OPC UA Server and logged an error. |
L00145189 |
|
SR 103145174: The aaSystemAuthenticationService caused a very high level of CPU activity. |
Original Change Request |
Related Change Requests |
Description |
745498 |
L00140609 |
Accessing array-wide properties of an array-type object attribute, without the proper use of the empty subscript syntax sometimes failed when the script’s object and the referenced object were on different engines. |
759366 |
|
Errors were logged stating that the visual element reference list was incomplete or corrupted. This occurred when a symbol was updated in the parent template and changes to the template were saved, but the template was still checked out, |
765642 |
|
A secured write could not be used to change the attribute value of a symbol when the ViewApp's security mode was changed during run time. |
766162 |
|
An Embedded Alarm Client control did not show alarms if the name of the alarm query began with the node name of the computer running an InTouch OMI ViewApp. |
767302 |
|
If a large number of items were deleted from a Graphic Toolbox folder, empty thumbnails of the deleted items remained when the folder was opened in the Layout Editor. |
767601 |
|
An InTouch OMI ViewApp with three or more Embedded Alarm Client controls increased the CPU usage on the computer running the ViewApp to approximately 70 percent. |
772872 |
|
Sending keys for UserInput animation of a symbol resulted in issues, such as the state of a toggle button symbol not returning to the resting state, and sending a Tab key for UserInput animation not moving the focus to the next field in a data entry symbol. |
775165 |
|
In some instances, when an object’s owned graphic was embedded inside another graphic, and the contained name of the object was changed, the Graphic Editor displayed “Graphic not Available”, even though it displayed correctly at run time. |
776083 |
|
The SetCustomPropertyValue method from the button action script did not set a value to DateTime Picker. |
776529 |
|
When a text style Element Style was applied to a symbol and then removed while the ViewApp was running, the symbol's text style did not revert to the default Element Style. |
783216 |
|
An item could be successfully added to and deleted from a listbox, but then if it was re-added, warnings were logged and the item was not added. |
784461 |
|
The display animation showed the default value of a custom property instead of the quality value, if the action script included an integer-type custom property for quality that was referenced by the animation. |
785040 |
|
If a custom property was hidden by a Symbol Wizard option and the hidden property was referenced by a visible (non-hidden) custom property, all animations that referenced the visible custom property were shown as initializing, and the visible custom property's quality status did not update. |
786745 |
|
When a symbol with an action script configured with a null string custom property was saved, a warning was logged in the System Management Console (SMC). |
787432 |
|
The Wonderware Application Manager did not refresh automatically to show the latest edited time. |
789583 |
|
On French language operating systems, element style animations were not applied when a float data type was used in the Truth Table. |
794762 |
|
When a symbol was renamed, its name in the Layout Editor's Action List did not automatically refresh, which caused incorrect information to be displayed in the ViewApp. |
795463 |
|
In a ViewApp with multiple screens, some of the screens went blank if the screen windows were kept open for a period of time, or if they were resized. |
795485 |
|
A ViewApp continued to utilize the CPU for aaServiceHost32.exe and other processes, even after the ViewApp was minimized. |
796192 |
|
An OnHide script in a symbol only set its attribute value correctly the first time the symbol was closed. When the symbol was closed after that initial time, the value was not set. |
796213 |
|
A ViewApp that utilized symbol switching stopped working after running continuously for more than one day. |
796962 |
|
An "System.InvalidOperationException: Queue empty" warning was logged for a ViewApp that used a multiple screens or panes that wrote to the same attribute via different threads. |
798498 |
|
In a multi-galaxy system, the Object Viewer stopped working and a memory leak occurred when the Backward Compatibility checkbox was unchecked in the Service Discovery Configuration dialog. |
799769 |
|
When the MyViewApp.Navigation.CurrentPath attribute was set via a script, interacting with the NavTree caused the ViewApp to stop responding. |
799775 |
|
When a symbol was used in multiple panes, one more of the symbol elements did not always render completely, and warnings related to the Graphics.WPFRender component were displayed in the logger. |
801536 |
|
When a Platform object was stage-deployed with a customized checkpoint directory (not the default path), deployment was not successful and errors were displayed in the logger. |
804504 |
|
A ViewApp would stop working if a touch operation (pinch/zoom) was performed. |
804556 |
|
A ViewApp running in a multi-galaxy environment that required frequent graphic rendering would begin to slow almost immediately after it was opened. |
804939 |
|
A ViewApp with a high Graphics Performance Index (4.3) experienced a memory leak that eventually caused the ViewApp to stop working. |
805378 |
|
Object retentive values were not deleted from the retentive file when a Platform object was deployed with the "preserve runtime changes" option unchecked. |
806849 |
|
After an image was copied and pasted into a symbol and then deployed, an error message was displayed that "Property FillColor is not supported," even though the image element did not have a fill color. |
807215 |
|
Opening an instance that contained a dense graphic in the Object Editor required an excessive amount of time, and could cause the IDE to stop working if a large graphic was then opened. |
809411 |
|
When a graphic is created or edited in a deployed ViewApp derived from the Default.cab, the ViewApp did not get marked for pending changes. |
811275 |
|
An attribute value in a value display animation that had bad quality was shown as NaN with good quality during historical playback. |
921198 |
|
Pressing the backspace key while entering text in the address box no longer causes the WWWebAppControls app to navigate to the previous URL. |
Original Change Request |
Related Change Requests |
Description |
792363 |
|
Dispose and null reference warnings were logged in the System Management Console from the Graphic cache manager component which was being used by MobileAccessTask process. |
799529 |
|
The MapApp.aaVERL file was created in the wrong folder. |
804193 |
|
Occasionally, the MapApp did not load, and a warning that the HTML5 Graphics Web Server failed to start was displayed in the logger. |
806821 |
|
The alarm indicator was always displayed, even if "Show Alarm Indicator" was disabled. |
806859 |
|
When an edit box was added to a symbol and the symbol added to the MapApp, no message was displayed to indicate that the edit box was not supported in the MapApp. |
809052 |
|
Navigating to a different asset in the asset tree at run time caused a complete refresh of the MapApp. |
For additional resolved issues that apply to a specific product, see the applicable product readme.
The following important known issues are listed by their assigned CR or reference number in ascending order. Additional known issues are documented in the product-specific Readme files.
778585 |
After launching a ViewApp from the Runtime Manager, mouse events stop working (the mouse freezes). This is due to an issue in the .NET Framework. Microsoft has issued a patch for .NET 4.5.2 that fixes this issue. Updating to .NET 4.6.1 or a later version also fixes the issue. Workaround: To apply the Microsoft roll-up patch to the .NET 4.5.2 framework, go to: The issue can also be resolved by editing the registry. For details, go to: |
787270 |
On certain systems, and in some situations, the file transfer portion of the Wonderware System Platform 2017 installation may require more time when compared to a similar installation of Wonderware System Platform 2014 R2 SP1. |
796068 |
On a Galaxy Repository, uninstalling Wonderware Application Server results in restoring the ArchestrA User credentials to the registry. |
804308 |
While installing Wonderware System Platform 2017 on a remote node using an RDP session, you may lose your RDP connection if the Windows Firewall Service is stopped and Startup Type=Manual. If you are unable to reconnect, try the following:
|
931629 |
If a Wonderware System Platform component is removed through the Control Panel ("Install/Uninstall Programs" applet), rather than by running the Wonderware System Platform installation program (Setup.exe), errors messages will be logged, exception messages such as "FileNotFound" will be displayed, and Application Server deployment will no longer be successful. Workaround: Use the "Modify" workflow, as described in the Wonderware System Platform Installation Guide.
|
L00123462 |
In a multi-galaxy environment, you can pair galaxies by IP address rather than using a node name (computer machine name). Unpairing galaxies identified by IP address fails when NetBIOS and DNS solutions are unavailable. Where your galaxies are identified by IP address, you must create a temporary host file to map the IP addresses as hostnames for purposes of unpairing.
|
L00123474 |
Writing from InTouch to a remote galaxy using indirect tags can fail for some of the remote references. Object Viewers on two different nodes may show different values for the same reference. You can avoid this issue by deactivating Advanced Communication Management in the IDE. Additionally, if you use the same indirect tag with scripting more than one time, you can modify your scripts to set the indirect tag's name property to an empty string after the loop completes. For example, in the following script snippet, you would add the line highlighted with bold text:
IF bRunScript THEN |
L00133534 |
Undeploying a galaxy with Object Viewer active will cause Object Viewer to shut down with an informational message that requires acknowledgement (click OK) to complete the shutdown. In a multi-galaxy configuration, with Object Viewer open, undeploying a paired Galaxy, then redeploying the galaxy without properly shutting down Object Viewer, can cause ASB services to fail to reconnect to the redeployed galaxy. To avoid this condition, click OK to shut down Object Viewer before redeploying the galaxy. |
L00139918 |
Uninstalling Wonderware InBatch versions 10.2 or 11.0 installed on a Wonderware System Platform 2014R2 SP1 system results in a failure to connect to ArchestrA Service Bus (ASB) services. If you uninstall either of these InBatch versions then cannot connect to ASB services, run a repair on Wonderware System Platform 2014R2 SP1 using Windows' Add/Remove Programs utility. |
L00141660 |
In a system with two GR nodes, attempting to connect from the IDE on one node to a Galaxy on the second GR node does not succeed, and the IDE shuts down. Workaround: Pair the GR nodes before trying to connect to the Galaxy on the other node. See "Working with Multiple Galaxies > Setting Up a Multi-Galaxy Environment" in the Application Server User Guide for information about configuring multi-Galaxy pairing. |
Missing NavTree |
After upgrading or migrating an InTouch OMI ViewApp from 2017 to 2017 Update 1, a warning message states that the NavTree entity could not be found. In 2017 Update 1, this navigation object has changed and is now called “NavTreeControl.” Workaround 1: To replace the NavTree object in a ViewApp or Layout when upgrading to Wonderware System Platform 2017 Update 1:
Workaround 2: To replace references to NavTree when importing packages from Wonderware System Platform 2017:
|
774717 |
When an InTouch OMI application (View.exe) that uses one of the following web controls is run in 4K mode or on multiple 1080p monitors, under certain circumstances the application may stop responding:
Workaround: When running a ViewApp that uses a web control on a 4K monitor, set the monitor resolution to 2560 x1440 or less. When running the ViewApp on 1080p monitors, do not attempt to span multiple monitors. |
777504 |
The GetCPQuality() scripting method is not supported in InTouch OMI. If used in a ViewApp, it always returns quality = 0 (bad quality). |
781006 |
If an invalid custom property is added to a symbol, no warning is logged in the System Management Console, even though no value is displayed for the custom property. |
781620 |
The Height and Width properties of a group with text elements do not change in accordance with changes made to the label font size, and are not rendered correctly. |
784206 |
A Value Display animation with the expression GetItem() or GetItemData() of a Simple ComboBox cannot get a value, when the 'index' parameter for the function is a custom property such as: "GetItem(cp_Index)", cp_Index is valid CP and default value is 0. However, it will work if you use an expression with a constant value such as: "GetItem(1)" |
784344 |
References from a graphic embedded in another graphic may resolve incorrectly when the SetCustomPropertyValue action script is used to change the embedded graphic to a different owning object. |
784470 |
Tooltip animations that contain multiple lines of text with line breaks may not display properly in deployed ViewApp. |
784474 |
A tooltip may partially cover the element with which it is associated in the deployed ViewApp. |
787192 |
When OSGroup security mode is used, the VerifiedWrite dialog is not displayed when you modify the value of a VerfiedWrite attribute from a combobox, if you first attempted to perform the VerifiedWrite without having the correct security credentials. |
789857 |
When an element style animation is configured with both a fill color and a blink color, the blink animation and color remain when an element style override is applied that specifies only a fill color and has the blink check box deselected. Workaround: Set the initial state without blink, then apply overrides as needed with blink enabled. |
789958 |
On some high resolution tablet devices, such as the Surface Pro 4, object names in the System Platform IDE may have insufficient line spacing between items, which can make it harder to read object names. |
794383 |
When a custom property is changed from public to private, the change does not have any affect, and the value of the private custom property is shown at run time (private values should not be shown). Similar situations occur when:
Workaround: Manually validate the outermost symbol and then deploy the ViewApp. |
797816 |
In some cases, Historian Client will cause a View.exe process to continue to run even after all ViewApp windows are closed. Workaround: Use Task Manager to end the View.exe process. |
798264 |
After performing an upgrade or migration on a multi-node system to Wonderware System Platform 2017, and then deploying a ViewApp, the ViewApp does not connect to one or more nodes. Workaround:
|
932024 |
In non-English locales, a comma is always used as the list separator for arrays in an InTouch OMI ViewApp. As a result, an array that contains decimal values can be difficult to read, since the same character will be used for separating values and for the decimal point. |
797198 |
If the unfill color is set to a gradient in an Unfill animation with an animation fill style, and the fill style animation is changed, it changes the unfill color property. |
797226 |
If the expression type is set to string in the truth table for fill color animation, the fill style does not change when the value changes. |
797324 |
If you change the Source type in Map Settings to a type that supports Overlay type maps, and set the map type to Overlay, and if you then switch to a Source type that does not support Overlay, the map type remains set to Overlay and cannot be changed. Workaround: Change the Source type to a type that supports Overlay, and reset the type to Base map. Then, change the Source to the desired source. |
932052 |
In a Multi-Galaxy environment, where one node is running Wonderware System Platform 2017, and another node is upgraded to Wonderware System Platform 2017 Update 1, some ASB services are not immediately deployed after the upgrade. This results in multiple "Failed to connect" warnings in the logger. Workaround: These connection issues can be corrected by deploying the upgraded node one more time, after the initial redeployment.
The same issue can occur when a run-time node is added to the Galaxy Repository, and the node is not detected as online when the attempt is made to deploy ASB services. Workaround: These connection issues can be corrected by deploying the added node one more time, after the initial deployment.
|
933098 |
After importing objects, the imported objects do not always show the complete set of thumbnails for symbols that they link to. When this occurs, the user may see "Graphic Not Available" in place of the thumbnail. Workaround: If thumbnails are not displayed for an object, validate the object (Object > Validate). This will regenerate the symbol thumbnails for the object. |
933752 |
Starting the IDE can take up to a minute if the node on which it is running is not connected to the internet. Root Cause: To enhance security and reliability, Wonderware System Platform will validate certificates. Windows then performs a check to see if the certificate has been revoked. Without an internet connection, Windows waits until the timeout for this check has been reached before allowing the IDE to start. Workaround 1 (preferred): This method changes the default timeout for the certificate check.
Workaround 2: This method disables checks for revoked certificates.
Workaround 3: This method installs the certificates that the operating system is attempting to validate onto the local machine. Once installed locally, the operating system will no longer need to access the network to retrieve them.
|
|
|
The following known issues are in addition to those documented in the InTouch HMI Readme.
L00139557 |
When using a non-default SQL port: In Runtime with multiple EACs configured, database connections may fail with a "Timeout expired" warning (see full text below) appearing in the SMC. Error Message: Open() in DCMConnection failed: 'Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.' Workaround: Perform a manual refresh on the EAC control to re-establish the connection. |
L00139560 |
When using a non-default SQL port: If the primary Historian server is down during a restart of WindowViewer, trend updates are delayed by approximately 25 seconds. This is a one-time delay after WindowViewer restarts. |
L00139681 |
After changing the SQL port of the Historian node and restarting Historian, the ArchestrA Trend Client (RT Trend) does not reconnect to Historian. Workaround: Restart the instance of WindowViewer hosting the Trend client. |
L00139786 |
After switching between default and custom SQL ports for Dual Historian, on a machine where the ArchestrA Trend Client (RT Trend) is used and is configured by scripting, only the real time trend displays, not the Historian trend. Workaround: Delete the servers.xml file typically found at the following location: C:\Users\<user-name>\AppData\Local\Wonderware\ActiveFactory\servers.xml. |
L00139789 |
Connecting to a SQL database in Microsoft Windows 8 or Windows 10 operating systems, when a non-default port is configured for SQL, results in an error message that a connection to the server is not available. Workaround: Disable (shut down) the firewall on Windows 8 and Windows 10 operating system machines. |
L00139813 |
Deploying an InTouchViewApp with a fully qualified file name exceeding 260 characters results in errors logged in the Logger and client controls not copied to the destination location. A fully qualified file name is one that prefixes the file name with the drive letter and directory path. The fully qualified file name must not exceed 260 characters, and the directory name must not exceed 248 characters. These are Windows operating system limitations. |
L00139833 |
Migrating a Galaxy which has an InTouchViewApp with embedded Historian Client controls from Wonderware System Platform 2012R2 or 2014R2 to 2014R2 Service Pack 1, results in errors logged in the Logger. Workaround: Before migrating the InTouch application, delete the previous version Historian Client controls that exist in the Galaxy. Import the newer version controls. |
676670 |
Screen Profiles, which are only for use with InTouch OMI ViewApps, appear in the Galaxy Browser within InTouch WindowMaker. |
783666 |
The ZoomPercent property in Named Script expression box does not get evaluated at runtime when it is used without an element. For example: ZoomPercent >= 200 does not get evaluated at runtime Workaround: Use the ZoomPercent property of an element instead. |
929506 |
Push Button and Slider animations do not work in Internet Explorer. |
929583 |
The textbox element does not show text if the font size is bigger than the boundary of the element. |
930784 |
Most Action Script animations do not work in the InTouch Web Client. The trigger types that work are:
Workaround: Use only the trigger types listed above when configuring an Action Script that will be used in the InTouch Web Client. |
930834 |
The chord primitive is not currently supported in the Web Client. For this reason, the SAL_HeatExchanger_Fan symbol does not render properly in the Web Client, especially when the width of the symbol is increased. Other SAL symbols are similarly affected. Workaround: If you use the SAL_HeatExchanger_Fan symbol or other symbol that uses the chord primitive in the InTouch Web Client, do not resize it to increase its width. |
931231 |
Text on a Button displays only as vertically and horizontally centered regardless of the text alignment settings in the Graphic Editor. |
931235 |
"Blink" is not supported in the Web Client, but the conversion report file does not state that it is not supported if blink is used in the application style library. |
931757 |
Firefox cannot open a Web Client page. Workaround: Configure Firefox as follows:
|
932067 |
Using Microsoft Edge browser version 25, the AnalogMeterRound symbol shows up as a dark color. |
933311 |
As the Web Client does not support application formatting styles, the InTouch Web Client will display only integers instead of real or fixed decimal numbers when advanced formatting properties have been set through Value Display or User Input animation. Workaround: To show decimal values for User Input and Value Display animations, use “Format String” instead of “Real” or “FixedDecimal.” |
934015 |
By default, the InTouch web service runs under a local user. Therefore, if WindowViewer is running on a remote node, the InTouch Web Client will not be able to access the network location and will display a navigation error, "Navigation data file could not be found." Workaround: If the Web Client displays a navigation error:
|
935917 |
When a symbol name includes the special character "#", the Web Client does not load the symbol into the browser and an "Error Loading Symbol" message is displayed. |
The following known issues are in addition to those documented in the InTouch Access Anywhere Readme.
L00144565 |
Installing InTouch Access Anywhere through the Modify workflow can cause various issues related to uninstalling the product at a later time. These include:
Workarounds: For issue #1 (registry keys not created), do the following:
For issue #2 (unable to launch InTouch View.exe application), do the following:
|
924302 |
When installing Historian along with any other component, and the other component requests a system restart, if you restart immediately after closing out the Configurator, a number of warnings may appear in the logger from the Historian services. This is caused by a timing issue. The warning messages can be safely ignored because they do not affect the configuration of the Historian, and do not have any effect on the system during or after the system restart. |
931966 |
When using silent install to upgrade Historian to Wonderware System Platform 2017 Update 1 from a version that set a default password for SQL Server users, warning messages are logged that alert you to set new passwords for various system users after the Configurator runs. Your system will continue to operate normally without resetting the passwords, but changing the passwords will increase system security. |
779958 |
When the same license is acquired on both a local node and in an RDP session that originates from the same node, the License Manager may not show all the licenses that have been acquired. This occurs even though the licenses are counted properly on the license server. The license count that you see applies only to the node you are viewing. Thus, once you reach your maximum number of licenses, you will not be able to acquire additional licenses, even though the license manager may indicate that more licenses are available. |
793643 |
If you have not set a default browser, and you install Wonderware System Platform 2017 with Schneider Electric licensing selected, clicking the Schneider Electric License Manager shortcut does not open the License Manager in the browser as it should. Instead, the shortcut opens in Windows Explorer. From Windows Explorer, you cannot open License Manager (the OK button is inactive). Workaround: Follow the instructions for your operating to set the default browser, and then open the Schneider Electric License Manager from the shortcut, or: Open your browser and copy the shortcut link, http://localhost/SELicenseManager, directly into the browser's address bar. |
If you create a filter for a history block query that results in no matches, "Not Connected" appears in the status bar and a warning is logged to the ArchestrA Logger. The status bar should show "Connected" even though no matches are returned.
The Wonderware System Platform documentation is available Adobe Acrobat .pdf files that are available from the following locations on the Wonderware System Platform DVD:
\Wonderware System Platform\CD-ApplicationServer\UserDocs\English
\Wonderware System Platform\CD-Historian-x64\UserDocs\English
\Wonderware System Platform\CD-HistorianClients\HistorianClient\Docs
\Wonderware System Platform\CD-Intouch\UserDocs\English
\Wonderware System Platform\CD-WIS\UserDocs\English
To view the documentation, you must first download the latest version of Adobe Reader from the Adobe Corporation web site: http://www.adobe.com/products/acrobat/readstep2.html.
You can also access online Help systems from within the software.
Last revision: 11/9/2017
This Readme provides information about Wonderware InTouch Access Anywhere 17.0.
Wonderware® InTouch Access Anywhere™ provides remote access to Wonderware InTouch™ applications with an HTML5 Web browser running on a desktop computer or a mobile device. Any Web browser that supports HTML5 can be used as the client to view InTouch applications running on a remote desktop server. Wonderware InTouch Access Anywhere enables you to select an InTouch application from a list and view it running in WindowViewer.
The InTouch Access Anywhere installation media provides the following:
InTouch Access Anywhere 2017 Version 17.0
New Features and Enhancements:
Note: If you have customized the InTouch Access Anywhere start page, you will need to reapply these customizations. It is recommended to document these customizations before upgrading.
Note: In a mixed product environment in which InTouch applications run on the same computer as Wonderware System Platform 2017 ViewApps, WindowViewer must be started before the ViewApp to be able to view both types of applications with InTouch Access Anywhere.
For a complete list of resolved issues, see the Resolved Issues section of this Readme.
This section summarizes InTouch Access Anywhere installation requirements, supported browsers, and considerations for viewing InTouch applications on mobile devices. For more detailed information, see the Wonderware InTouch Access Anywhere Documentation
The following list describes the prerequisites to install the InTouch Access Anywhere Server or Secure Gateway.
Note: InTouch Access Anywhere Server does not support embedded editions of the Windows Operating System.
Per-Device RDS licenses are not supported.
Important Security Requirement: Securely Deploying InTouch Access Anywhere
Direct access to the InTouch Access Anywhere Secure Gateway over the Internet is not supported. We recommend that you access the Gateway via a VPN tunnel for all remote connections.
Wonderware InTouch Access Anywhere can be accessed from smart phones, tablets, and laptop computers that provide an HTML5-compliant web browser.
Browsers Tested with InTouch Access Anywhere
Browsers verified to work with Wonderware InTouch Access Anywhere include the following:
Important: Please be aware that only the browsers in the above list have been tested in the specified hardware platforms (PCs, tablets and Smart Phones). No testing has been done with HTML5 browsers nor other devices not included in the above list (SmartTVs, eBook Readers, game consoles, etc.).
Functionally Compatible Browsers
Certain versions of the above listed browsers, such as:
are in theory functionally compatible with InTouch Access Anywhere. While you may be able to use them, specific behaviors are unknown as these browser versions have not been tested.
Browsers: Important Notes
Although Wonderware InTouch Access Anywhere supports the listed browsers, you should review the Known Issues and Behaviors section of this Readme for issues specific to each browser.
Run-time interactions with InTouch applications are different on mobile devices than on traditional desktop computers. For example:
When using InTouch Access Anywhere to remotely view and interact with your applications, it is important to be aware of the behavior differences among devices, operating systems, and browsers. For the best user experience, you should become familiar with the touch interfaces in the devices you will use, and factor these differences into the design of your InTouch applications. For example:
This section lists defects resolved with this release.
Defect Number |
Description |
L00132897 |
SR 103131461: Open InTouch Access Anywhere sessions would disconnect and return to the server logon page after short periods of time. |
L00140226 |
SR103138586: When running ITAA Server 11.1 SP1, the system could consume large amounts of system resources, specifically RAM, and the server could become unresponsive. |
L00141682 |
Some program files may not be automatically deleted after uninstalling InTouch Access Anywhere Access Anywhere Server and Secure Gateway. |
L00143602 |
[Documentation] The procedure in the InTouch Access Anywhere Secure Gateway Administrator Manual that described how to configure the Secure Gateway to host one or more Access Anywhere Servers was unclear. The procedure did not clearly state that the list of InTouch applications does not populate in the Server log on page automatically when connecting to the Access Anywhere Server through the Secure Gateway. |
L00143600 |
[Documentation] In the InTouch Access Anywhere Server Administrator Manual, an additional step was listed in the pre-installation procedure for Windows Server 2012/Windows Server 2012 R2 that was not required to configure settings. |
L00142893 |
[Documentation] A statement regarding devices not tested with supported browsers was missing from the InTouch Access Anywhere documentation. |
L00143599 |
[Documentation] In the InTouch Access Anywhere Secure Gateway Administrator Manual, the recommended install location for the Authentication Server was not clearly stated and the accompanying diagram did not provide clarification. |
L00140602 |
SR 103142714: Access Anywhere 2014 R2 SP1 introduced cross-site scripting protection, which was causing an error when Access Anywhere is called from an IFrame. |
This section describes known issues and platform/browser-specific behaviors in Wonderware InTouch Access Anywhere. The issues are grouped by areas affected by the issue. Workarounds are provided when available. You can also refer to the InTouch Access Anywhere user documentation for more information.
Areas Affected |
Issues and Behaviors |
All Operating Systems |
Firefox: Values entered using the InTouch keyboard appear twice. TFS542896. |
|
When connecting to the InTouch Access Anywhere Server through the Secure Gateway, the Tool Box displays icons for both PC and Mobile devices at the same time. TFS 658661 |
|
Internet Explorer 10: When connecting to the InTouch Access Anywhere through the Secure Gateway, the web tab icon displays as the default Internet Explorer icon instead of the green InTouch Access Anywhere icon. TFS 665727 |
|
When connecting to the InTouch Access Anywhere Secure Gateway Configuration Portal, the time format does not display correctly. This behavior only applies to Japanese and Simple Chinese operating systems. L00144578 |
|
When an InTouch application is published in a localized character path, InTouch Access Anywhere will fail to launch the application. This behavior only applies to Japanese and Simple Chinese operating systems. L00144579 |
Internet Explorer 10, Safari 8 |
Internet Explorer 10, Safari 8: Playsound() works with Chrome, Opera, and Firefox, but not with Internet Explorer 10 or Safari 8. L00133687. |
Internet Explorer on Windows RT Operating System |
Internet Explorer: When accessing the InTouch Access Anywhere server through an RDP desktop session, user input animations using the Windows operating system keyboard do not start the keyboard. The recommended workaround is to use the device's built-in keyboard. TFS542851. |
|
Internet Explorer 10 on WinRT in a touch environment: A mouse cursor may disappear after using the Surface keyboard to enter data. As a workaround, use touch gestures in place of mouse inputs. TFS218943. |
Windows 2008 R2 64 bit |
InTouch Access Anywhere Secure Gateway files cannot be repaired by the install program.L00141680 |
|
The "InTouch Access Anywhere Server Configuration" form may extend beyond the bottom the screen and cannot be resized to fit the resolution 1240x768. L00141668 |
Windows Server 2016 |
When WindowViewer is minimized, the minimized window will disappear and cannot be relaunched. L00144577 |
Wonderware InTouch Access Anywhere product documentation is provided as a set of Portable Document Files (PDF):
InTouch Access Anywhere Product Documentation Name |
File Name |
Wonderware InTouch Access Anywhere User Guide |
ITAA_UserManual.pdf |
Wonderware InTouch Access Anywhere Server Administrator Manual |
ITAA_Server_AdminManual.pdf |
Wonderware InTouch Access Anywhere Secure Gateway Administrator Manual |
ITAA_Gateway_AdminManual.pdf |
You need Adobe Reader installed on your computer to view InTouch documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site: http://www.adobe.com/products/acrobat/readstep2.html.
After installing Adobe Reader, double-click a PDF file with your pointing device to view the book with Adobe Reader. You can also open a PDF with the Adobe Reader Open command from the File menu.
As part of the security improvements delivered in this release, InTouch Access Anywhere Secure Gateway is now configured to be secured by default and requires further configuration after the product is installed. You can also configure the security settings back to the same levels as in previous releases (not recommended).
The security settings are described in InTouch Access Anywhere Secure Gateway Administrator Manual (ITAA_Gateway_AdminManual.pdf), in the following sections:
TargetHostWhitelistAllowedIPv4Addresses and certificate trust must be configured before using the InTouch Access Anywhere Secure Gateway. If you do not configure TargetHostWhitelistAllowedIPv4Addresses with the white listed systems, connections to the InTouch Access Anywhere Server through the InTouch Access Anywhere Secure Gateway will fail. You will get the following error message:
"Gateway: Target Host access is not allowed for address <IP Address>."
If you do not configure the certificate trust, you will be prompted with a certificate error if the Access Anywhere Server's certificate is not recognized on the Gateway node.
| Avantis | Industry Software Suites | OASyS | SimSci | SimSuite | Skelta | Wonderware | |
|
Copyright © 2017 Schneider Electric Software, LLC. | Contact Us |