Archestra License Manager 2014

admin

Last revision: 09/17/2014

About This Readme

Locate and open the CODESOFT 2018 License Manager. Select Activate. Enter your Serial number starting with the last letter of the license (either N or F ) and password and click Next. The preferred application for installing license (s) is ArchestrA License Manager. The application can be accessed via Start - All Programs - Wonderware - Common. If Archestra License Manager is not installed you can go to Start - All Programs - Control Panel - Programs and Features and right-click on InTouch and choose Uninstall/Change.

  1. Wonderware Intouch License Key DOWNLOAD (Mirror #1).
  2. 6) Navigate to Start Programs ArcGIS License Manager (9.x) License Manager Tools. Select the option 'Configuration using services.' Click the Start/Stop/Reread tab. Click Stop Server, Start Server, and Reread License File. It should say that the reread completed successfully. The reconfiguration is now complete.

This Readme provides information about important resolved and known issues for Wonderware® Information Server 2014 R2(version 5.6).

For information about new features, hardware and software requirements, product compatibility, installation and upgrades, and user documentation, see the ArchestrA® System Platform Readme, which is located in the root folder of the ArchestrA System Platform installation media.

Readme files from previous releases of Wonderware Information Server are posted to the Wonderware Developer Network at http://wdn.wonderware.com/Downloads.

This section describes important resolved issues. The following list is not a comprehensive list of all resolved issues.

Wonderware Information Server version 5.6

L00126879:HF CR L00126541: SR 103128503: The ‘&’ (ampersand) character is not supported for node name, URL, and description in the custom link.
L00127104:HF CR L00126589: SR 12612638: When the number of users is quite large, the Wonderware Information Server portal fails to browse the users in the domain.By setting the Server.ScriptTimeout to 600 sec in the ADSIServer.asp page from the {SystemDrive}:inetpubwwwrootWonderwareusengadminconfigure location, the Wonderware Information Server portal will be able to browse the users in the domain.
L00128101:HF CR L00127740: SR 35312334: If you run query with multiple Historians in the Wonderware Information Server, it does not keep all the added Historians after browser is closed and reopened.
L00128175:HF CR L00127873: SR 103128389: If you generate Historian Client Reports using the custom time range, reports might not publish correct result time.
L00131027:SR 48910191: DateTimePicker in Wonderware Information Server reports does not show the correct DateTime for dd-MMM-yy format.
L00131029:SR 45710754: If you access Report through Wonderware Information Server, the report parameter is not displayed correctly as per the language selected in Internet Explorer.
L00131009:HF CR L00130383: SR 15317191 : Single page is printed if you print ArchestrA Report from AppServer script to a printer.

ArchestrA Web Exporter

L00122986:HF CR L00122742: SR 10416892: Some background picture and icons are not available in the Web page if Silverlight 5.0 is installed.To work around this issue, uninstall the Microsoft Silverlight 5 runtime and install the Silverlight 4 runtime, which is available from: http://go.microsoft.com/fwlink/?LinkID=149156&v=4.0
L00123454:HF CR L00123229: SR 42410088 : Crash of the w3wp.exe at regular interval can result in ArchestrA Graphic not getting the live data value.
L00124478:HF CR L00123889: SR 103126851: Shut-down of the InTouch viewer can lead to the following issue:
  1. CPU usage can increase up to 80% because of the LMX Publisher Service.
  2. After restarting the InTouch viewer, the CPU is still high and doesn’t decrease.
  3. After restarting the InTouch viewer, the published Window in Wonderware Information Server doesn’t work (as if it still cannot connect to InTouch node).

The workaround is to end the process LMX Publisher Service in Task manager and restart the service from the Service panel, or reboot the Wonderware Information Server node.

L00124924:HF CR L00124816: SR 103127254:Quality and status indicator displayed in Wonderware Information Server is not the same as in InTouch Viewer.
L00125891:HF CR L00125609: SR 45110038: Accessing URL across a secured connection (HTTPS) produces the following error: “Connection failed…Reconnecting to the data source..”.
L00128046:HF CR L00125560: SR 103127004: Inconsistent Blue Banner/Title/Frame appear around some Windows when they are brought up from another window.
L00128335:HF CR L00128182: SR 45710111: Pipes created using the ArchestrA Graphics are not visible in Wonderware Information Server after export.

This section describes important known issues.

Wonderware Information Server 5.6

L00133366:If you upgrade Microsoft Office 2010 to Microsoft Office 2013 on a computer which already has ActiveFactory Reporting Website feature of the Wonderware Information Server installed on it, the ActiveFactory published excel report does not work.
To workaround this issue, open the Microsoft Excel Application Properties dialog box by running the Component Services > DCOM Config and modify the following:
  • Select Interactive User option in the Identity tab of the Microsoft Excel Application Properties.
  • Select the Used Default option in the Access Permissions section in the Security tab of the Microsoft Excel Application Properties.

Wonderware Information Server 5.5

L00128516:If you install Microsoft Excel on a computer which already has ActiveFactory Reporting Website feature of the Wonderware Information Server installed on it, the Historian Client ribbon will not be available in Microsoft Excel.
To workaround this issue, you must repair the Wonderware Information Server and reconfigure the ActiveFactory Reporting feature.
L00128778:When you export a report using ArchestrA functions from the Historian database, the following error in appears in the ArchestrA Logger: “ReportsFileSaveServer failed: System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.ReportViewer.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The system cannot find the file specified.”The workaround is to install Microsoft Report Viewer Redistributable 2005, which you can download from http://www.microsoft.com/en-us/download/details.aspx?id=21916. After installing this, use the Wonderware Information Server post-install Configurator to re-configure the ArchestrA Reporting feature.
L00129010:On the Windows 8 and Windows Server 2012 operating systems, the HTTP Activation feature under .NET Framework 4.5 must be manually turned on before ArchestrA Web Graphics can get live data.
For Windows 8, the HTTP Activation feature is under .NET Framework 4.5 Advanced ServicesWCF Services. For Windows Server 2012, the HTTP Activation feature is under .NET Framework 4.5 FeaturesWCF Services.

Wonderware Information Server 5.0

L00079240:If you install Microsoft Excel on a computer which already has ActiveFactory Reporting Website feature of the Wonderware Information Server installed on it, the Historian Client ribbon will not be available in Microsoft Excel.
To workaround this issue, you need to repair the Wonderware Information Server and reconfigure ActiveFactory Reporting Website.
L00079240:The ActiveFactory Reporting Website Trend samples do not work when you configure the ActiveFactory reporting feature with a virtual directory other than AFWEB. To make the Trend samples work with any virtual directory, go to Table Weaver Manager -> Query and edit the AFRWS Trend related Queries (AFRWSTrendQuery, AFScatteredPlot, AFTargetRegions and AFTrend_LiveUpdate) and change the URL field from “/AFWEB/Trend.aspx” to “/YOUR AFVIRTUALDIRECTORYNAME>/Trend.aspx”.
L00116108:When you uninstall Wonderware Information Server, the language packs are also uninstalled even if the Wonderware Historian Client is still available on the computer. You can manually install the language packs by running the setup.msi file in the appropriate subfolder of the following folder of the ArchestrA System Platform DVD: …ArchestrA System PlatformCD-HistorianClientsHistorianClientLang.
L00116141, L00121351:If you modify the ArchestrA System Platform installation and select to install the Wonderware Historian Client, the language packs are not installed automatically. A dialog box appears, and you must browse to the folder containing the setup program to install the language packs. You must manually install the language packs by running the setup.msi file in the appropriate subfolder of the following folder of the ArchestrA System Platform DVD: …ArchestrA System PlatformCD-HistorianClientsHistorianClientLang.
L00116553If you are configuring Wonderware Information Server on certain operating systems with ASP.NET 4.0, errors may appear in the SMC Logger.
Workaround: Configure the Information Server again when errors appear in the SMC Logger. The configuration will complete successfully.
L00116895LMX component warning messages stating “Failed to create access manager instance for thread id 4408, hr 0x8007000e” are logged in the ArchestrA Logger if you publish an InTouch HMI window containing Galaxy data references to the Wonderware Information Server portal using the ArchestrA Web Exporter and a WinPlatform is not currently deployed on the Wonderware Information Server portal computer.
Workaround: Deploy the WinPlatform on the Wonderware Information Server computer.
L00117554:Wonderware Information Server does not currently support InTouch indirect tags.
L00119770:The Wonderware Information Server Configurator adds aaTrend mime type to web.config for the default website, which affects 1.1 applications such as the reporting website for Wonderware Intelatrac.

To fix this, configure the mime type not for the entire IIS portal, but only for the ActiveFactory Reporting Website.

L00120350:If a data source contains a UTC DateTime that falls during the hour where clocks are advanced for Daylight Saving Time, the conversion of the DateTime in the OverView client’s time zone will be done incorrectly. OverView will add an extra hour to the local time.By default, the Information Model Server is configured to consider DateTimes as being UTC. However, DST rules are applied to these Date Times as if they were using the data source’s time zone.

For example, if your data source is in the Pacific Time Zone, date times between 03/11/2012 2:00:00 AM and 03/11/2012 3:00:00 AM will be incorrectly interpreted because they do not exist in the Pacific Time Zone.

Here are two examples. Consider that:

  • In the Pacific Time Zone, the Daylight Saving Time began at 03/11/2012 2:00:00 AM
  • In the Central European Time Zone, the Daylight Saving Time began at 03/25/2012 2:00:00 AM
  • The UseSourceTimeZone attribute is not configured. DateTimes in the data source are considered to be UTC.
  • OverView converts DateTimes in its local time zone.
Data Source Time ZoneOverView Time ZoneSource ValueValue that should be displayed in OverviewActual Value displayed in OverView
Pacific Time ZonePacific Time Zone03/11/2012 2:06:26 AM3/10/2012 6:06:26 PM3/10/2012 7:06:26 PM
Central European Time ZonePacific Time Zone03/25/2012 2:06:26 AM3/24/2012 5:06:26 PM3/24/2012 6:06:26 PM
L00121079:When starting the OverView client, you get an error message indicating that the application is already installed from a different location.This normally happens if you have installed OverView by clicking the OverView link in the Information Server Portal and then try to access OverView by starting it using the url directly and the url being used has a different case than the url used during initial installation.

For example:

  1. You click on the OverView link in Information Server Portal, the OverView application is downloaded from http://infoServerNodeName/OverView/OverView.application.
  2. You paste in your web browser (or click a link someone has sent you by email) that reads http://infoServerNodeName/overview/overview.application. (no capital letters)

Another situation exist to generate this issue. After installing OverView from the OverView in Information Server portal, you try to start OverView by directly using the url and you use “localhost” instead of the Information Server node name.

In any case, you can always start OverView by either clicking on the OverView link on the Information Server portal or by starting OverView from the Windows Start menu.

L00121126, L00122742:Some ArchestrA Symbols cannot be loaded by Silverlight 5.To work around this issue, uninstall the Microsoft Silverlight 5 runtime and install the Silverlight 4 runtime, which is available from: http://go.microsoft.com/fwlink/?LinkID=149156&v=4.0
L00121739:Wonderware Information Server cannot be configured on a computer running a Simplified Chinese or Japanese Windows operating system if the installation path includes Asian double-byte characters.
L00122488:Errors occur when the dbo.ReportsFileSave stored procedure is executed within the Historian Runtime database to generate an ArchestrA Report (SSRS).To resolve this issue:
  1. Copy the Micrsoft.ReportViewer.Common.dll file from the Global Assembly Cache (GAC) folder of the SQL Server computer.
  2. Paste the Microsoft.ReportViewer.Common.dll in the C:inetpubwwwrootwonderwareArchestrAReportsbin folder of the SQL Server computer where Wonderware Information Server is installed.
  3. Run the printing.sql on SQL Server computer.

Wonderware Information Server 4.5

If you are using the Windows 7 operating system, the ArchestrA License Server stops responding if you remove the hardware dongle that is associated with a license managed by the License Server. Also, the License Server may intermittently stop responding.

To recover the License Server, reconnect the hardware dongle and then restart the License Server.

L00091440:

The Wonderware Information Server portal and InTouch View.exe are running on the same computer, and that computer is running a Windows Vista or later operating system. In this scenario, the Alarm Manager used by Wonderware Information Server to consume the alarms runs in Session 0, and another instance of the Alarm Manager used by InTouch View.exe to provide the current alarms runs Session 1. Because the SuiteLink Name Service (slssvc.exe) cannot register multiple instances with the same name, “AlarmMgr,” the first instance to be registered is the only one that communicates alarms. Therefore, the portal cannot retrieve current factory alarms that are generated by the InTouch software running on the local node.

To avoid this issue, run InTouch view.exe on a computer that is remote to the Wonderware Information Server portal computer.

L00111700:

On Wonderware Information Server node, if the ClientSide Setup window appears, enable Allow previously unused ActiveX controls to run without prompt option in the Security Settings of Internet Explorer.

By default, the above setting is enabled for the Local intranet and Trusted sites zones and is disabled for the Internet zone. If you face this issue, add this website to your trusted sites list in the Internet Options settings of Internet Explorer.

L00114588:

You must manually install the language packs for the Wonderware Historian Client product by running the setup.msi file in the appropriate subfolder of the following folder of the ArchestrA System Platform DVD: …ArchestrA System PlatformCD-HistorianClientsHistorianClientLang.

L00115377:

The WinXML Exporter may not correctly handle complex conditions for a color animation expression field.

Wonderware Information Server 4.0 with SP1

L00104609:

While working on Japanese or Simplified Chinese operating systems, if you publish a trend from the Wonderware Historian Client to Wonderware Information Server, and then access it through the Wonderware Information Server portal, an error occurs and the resulting trend is empty. This happens when the name of the trend file contains Japanese or Simplified Chinese characters and you are using Internet Explorer version 6. To resolve this issue, upgrade Internet Explorer to version 7 or 8.

L00109491:

After opening a Windowset page by copying its URL and pasting it in a browser window, some of the buttons on that page do not function. An error message is displayed stating access is denied. Such functionality is not supported for this release of Wonderware Information Server.

L00110331:

If you publish an InTouch window (where the window is updating I/O tag data) to a local Wonderware Information Server node on the Windows Server 2008 SP2 operating system where Terminal Services are enabled, and then open the same window in Wonderware Information Server, there are no I/O tag data updates.

To work around this issue, if you intend to have Wonderware Information Server on a Terminal Services enabled system, make sure that the Terminal Services option is enabled and configured before installing Information Server.

Wonderware Information Server 4.0

L00101808:If Microsoft Excel is started on the Wonderware Information Server portal node for viewing a report published from ActiveFactory Workbook, and no license is available, Excel shows a message indicating that license “ActiveFactory of version 10.0” was not found. Installing a valid SVoyager_Portal (version 4.0) license will fix this issue. You do not need to have an ActiveFactory license.
L00102375:If you publish the Workbook report to Wonderware Information Server portal with Long Name and accessing the Scheduled Report link in ActiveFactory Reports Node, it results in an error.
L00102545:The ArchestrA Web Exporter must be installed on a node that has the ArchestrA IDE installed. Additionally, you will need to install Microsoft Silverlight 3.0 or Silverlight 3.0 P1 on each computer that will be used to view the published symbols and windows in Internet Explorer. Microsoft Silverlight can be installed on those computers by clicking the Microsoft Silverlight logo that appears when you select to view a published symbol or window on a computer without Microsoft Silverlight installed. If the client computer does not have an Internet connection, you can download the package from Microsoft, move it to the client computer, and then manually install it. The link to download the package is: http://go.microsoft.com/fwlink/?LinkID=149156

Win-XML Exporter

L00061632:You cannot open the online help for the Win-XML Exporter in a non-English OS. Documentation for the Win-XML Exporter is only available in English. To open the documentation for Win-XML Exporter, double-click C:Program FilesWonderwareSuiteVoyagerWinXMLExporterBooksenglishStartDesign.htm. This starts Internet Explorer and opens the documentation page. (If a popup blocker is installed, disable it.)
L00011415:The Win-XML Exporter installation program does not detect user privileges at the start of the installation. You must be an administrator on the computer on which you are installing the Win-XML Exporter. If you are not an administrator, the Win-XML Exporter installation program fails when it tries to copy files to the computer.

ArchestrA Web Exporter 1.0

L00094337:If you are viewing published symbols across a secure connection (HTTPS), you cannot view live data. To work around this problem, you need to modify the web.config file in the Information Server. To do this:
  1. Open the file C:InetpubwwwrootWonderwareAADataSvcweb.config in a text or XML editor.
  2. In the system.ServiceModel section, locate the entry:
    <endpoint bindingConfiguration=”HttpNTLMBinding”
  3. Change “HttpNTLMBinding” to HttpsNTLMBinding”
  4. Save and close the web.config file.
  5. Restart Internet Information Services (IIS) by doing the following:
    From a command line, type iisreset and press Enter.
  6. Restart the ArchestrA LMX Publisher service.
L00095140:If you open a large number of Information Server sessions in the Internet Explorer at the same time, an Internet Explorer connection error may appear. This is caused by a limitation in the Thread Pool that limits the maximum number of sessions to the default of 350 for each CPU.

Note: We do not recommend increasing the default number of sessions due to the resulting high usage of system resources.

To work around this issue, change the value of MaxThreadPoolSize in the AppSettings section of the web.config file. Do the following:

  1. Open the file C:InetpubwwwrootWonderwareAADataSvcweb.config in a text or XML editor.
  2. In the AppSettings section, locate the entry:
    <add key=”MaxThreadPoolSize” value=”350″>
  3. Set the value parameter to the number of sessions you want per CPU.
  4. Save and close the web.config file.
  5. Restart Internet Information Services (IIS) by doing the following:
    From a command line, type iisreset and press Enter.
  6. Restart the ArchestrA LMX Publisher service.
L00095827:If you configure an element with a Horizontal or Vertical Slider animation, at run time the slider tooltips showing the horizontal and vertical position do not move with the slider. This is caused by a limitation in Microsoft Silverlight 3.0.
L00097077:In published symbols, adjacent elements without boundary line may show a small gap between them. This is caused by a defect in Microsoft Silverlight 3.0.
L00097084:The coordinates of an InTouch popup window are not calculated correctly when opened in Internet Explorer. If the popup window is called from a Show QuickScript, it opens at the top left of the client area. If the popup window is called from a Show Window animation, it opens in the center of the client area. In both cases the configured coordinates are ignored.
L00097624:In published symbols, one pixel wide lines will not completely cover the background on which they are placed. This may effect the visual quality of the published symbol. This is caused by a defect in Microsoft Silverlight 3.0.
L00098489:The input animations of elements in a group (set up as an icon) in ArchestrA Symbols that are then embedded into an InTouch application, configured with InTouch input animation, and then transformed and published, still work in the published displays. Expected behavior is that the InTouch input animations override the input animations of the embedded ArchestrA Symbol, as it does in WindowViewer.
L00098852:If you configure more than one element with a pushbutton animation and different shortcut keys in an ArchestrA symbol, the shortcut keys do not work correctly in the published symbol.
L00098905:The percentage fill animation on ArchestrA Symbol element groups (with TreatAsIcon set as TRUE) follows the behavior of InTouch cell fill and not that of ArchestrA Symbols running in WindowViewer. Specifically, it follows the following rules:
  • Fill Style: Follow the fill style of each individual element in the group.
  • Unfill Style: Follow the unfill style of the group.
  • Fill Percentage: Follow the fill percentage of the group.
  • Fill Direction: Follow the fill direction of the group.
  • Fill Orientation: Follow the fill orientation of the group.
L00098962:If you open the String User Input dialog box of a published symbol at a resolution of 1024 x 768, you may not be able to see the OK, Cancel, Clear buttons, and buttons to move the cursor. To avoid this issue, switch to a higher resolution or view the published symbol in Internet Explorer full screen mode. To switch to full screen, press F11.
L00098968:If you configure a text element with the characters “{” or “}”, any animations except Tooltip or User Input do not work correctly in the published symbol. Avoid using the characters “{” and “}” in your application design and in your set of permitted characters.
L00098979:If you configure a Show Symbol animation with positioning relative to parent in a symbol that is already a popup symbol from another symbol, the positioning does not work correctly in the published symbol. Positioning relative to parent only works correctly for the first popup called from a symbol.
L00099100:You can successfully create a project containing one or more of the following characters: [email protected]#$%^&*()_+
However, you should not be able to. Avoid using any of the characters to prevent unpredictable results.
L00099147:If you install ArchestrA Web Exporter on a computer that has an older version of Microsoft Silverlight 3.0 SDK installed, the installation wizard does not remove the Silverlight SDK installation for you and the installation ends with a message. Uninstall Silverlight SDK from the Control Panel and then start the installation of ArchestrA Web Exporter again.
L00099223:You cannot change the value of a custom property of an embedded symbol with the SetCustomPropertyValue function in the hosting symbol. To work around this problem, create a new custom property in the hosting symbol and override the public custom property of the embedded symbol. You can now use the SetCustomPropertyValue function in the hosting symbol to change the new custom property which then redirects the custom property in the embedded symbol.

Example: Symbol S1 with the custom property CP1 is embedded in the Symbol S2. In Symbol S2, you cannot use the SetCustomPropertyValue function to set S1.CP1 to a value. To work around the problem, in symbol S2 create a custom property CP2 and override S1.CP1 with S2.CP2 in the Properties Editor. You can now use the SetCustomPropertyValue function to change the value of S2.CP2 which then also changes the value of S1.CP1.

L00099399:Elements in published ArchestrA symbols with radial gradients and focus scale values other than zero do not appear correctly. They appear with zero width and height focus scale. This is caused by a limitation in Microsoft Silverlight.
L00100142:ArchestrA Web Exporter does not allow “.” for Local Project Path” field value to store web project files.
L00100145:This release does not support following line cap styles: RoundAnchor, SquareAnchor, DiamondAnchor and ArrowAnchor. These line cap styles will be mapped to the other supported line cap styles. Below is the mapping:
  1. RoundAnchor transforms to Round
  2. SquareAnchor transforms to Square
  3. DiamondAnchor and ArrowAnchor transforms to Triangle

Wonderware Information Server 3.1

L00053415:When you start an ActiveFactory desktop client application or control, it takes 30-60 seconds for the application or control to open.

The computer you are using the control or application on does not have access to the Internet. The problem occurs because of the way Windows validates digital certificates used in code signing, such as that used by ActiveFactory. By default, when a computer is connected to a network, Windows attempts to access the certificate publisher’s “certificate revocation list” (CRL) to see if the certificate being used has been compromised. When the computer has access to the Internet, this check typically takes less than a second. However, when the computer does not have access to the Internet, this check waits on a timeout for the attempt to fail, normally about two minutes. To work around this issue, go to the computer on which the ActiveFactory control or application is installed and configure the Internet Explorer security options so that the Check for publisher’s certificate revocation check box is not selected.

L00058984:A pop-up for upgrading client components to newer version is displayed if your computer has lower version of the Wonderware Information Server Client Components installed. If the ActiveFactory shared component is already installed, the message “Remove the existing version of this product by using the Add/Remove Programs on the Control Panel” is displayed when you access the application. The message may pop-up again if the browser cache is not cleaned. Clean up the browser cache after installing the newer version of the Wonderware Information Server Client Components.
L00062855:Scheduled aaReports are not generating after DST time change in Fall Back settings, that is, from 1:59:59 AM to 1:00:00 AM. This is a known SQL Agent issue, the agent does not trigger during “the second hour,” see: http://support.microsoft.com/kb/931975/en-us. Extract: “…. However, there is a known issue in which scheduled SQL Server Agent jobs cannot run for one hour during the period when the November 2007 DST change occurs. After the clock is changed back from 2:00 A.M. to 1:00 A.M. on November 4, 2007, SQL Server Agent jobs would skip the next hour and wait until 2:00 A.M. to start next run. This is a known issue. This issue occurred even under the pre-2007 DST conventions. This issue does not result from the changes to DST in 2007 ….”
L00063757:The ActiveFactory Reporting Website Manual Data Entry does not save a value to the Historian database if you do not have write permission. Change the user for the Historian data source to wwAdmin or aaAdmin in the SDS Manager. The wwAdmin and aaAdmin user has write permission to enter values in the Historian database. After changing the user, re-configure the ActiveFactory feature and update the Manual Data Entry.
L00077735:Configuring Data Sources and Providers. The User Guide includes complete, specific guidance for configuring the RWS for use over HTTP/HTTPS in a single place. See Tech Note 541 (http://www.wonderware.com/support/mmi/comprehensive/kbcd/html/t002282.htm) for more information.
L00080904:A warning occurs when you configure the Wonderware Information Server with default Windows authentication mode pointing to SQL Server 2008 database. This happens because the user does not have “SYSADMIN” privileges. By default, the ‘BUILTINAdministrators’ security group is not added to ‘sysadmin’ server role. To add this security group to ‘sysadmin’ server role, you need to run the stored procedure ‘SYS.SP_GrantLogin’ as given below:

EXEC SYS.SP_GrantLogin ‘BUILTINAdministrators’.

After executing the stored procedure, you need to open the “BUILTINAdministrators” login properties and add it to the ‘sysadmin’ security role.

L00081067:AFTrendSamples do not work if the ActiveFactory Reporting Website feature is not installed.
L00081275:Exception occurs when Wonderware Information Server is in the repair mode. This is a Microsoft related issue. An exception occurs during the repair mode as some COM+ components run in the background.
L00087936:You cannot see live data in the sample reactor window in Process Graphics on Windows 2008 operating system. This is because InTouch 10.1 is not supported on Windows 2008 operating system.
L00088749:The Factory Alarms will not work properly when you backup and restore the content in the Windows authentication mode. This problem is due to an exception caused by executing the stored procedure getproviderlist_sp in the SuiteVoyager database because of a dependency on the DataSourceTVF(SQL Assembly) which uses the SDS assembly. This problem is documented in Microsoft’s KB article http://support.microsoft.com/kb/918040.

To rectify, use any one of the following workarounds:

  • Change the database ownership to the logged user. Execute the following statement in SQL Query Analyzer after the restore operation.USE <DatabaseName>
    GO
    EXEC sp_changedbowner sqlUserName

    For example:

    USE SuiteVoyager
    GO
    EXEC sp_changedbowner ‘sa’ ;

  • Select the SQL authentication mode to backup and restore the content.
L00089162:An error message appears when you upload a file from the Custom Link configuration page. In IIS 7.0, go to the Wonderware virtual directory, and configure the properties for ASP applications. Edit the property Maximum Requesting Entity Body Limit and set the value as per your file size. By default, the supported file size is 200KB.
L00089810:On a computer with Windows Vista or Windows 7 operating systems, the Wonderware Information Server portal does not display the Alarm Viewer Control and the Tree View Control. As a workaround, customize the following settings in the Internet Explorer.
  1. Start Internet Explorer. On the Tools menu, click Internet Options. The Internet Options dialog box appears.
  2. Click the Security tab.
  3. Click Trusted sites or Local intranet.
  4. Click Custom Level. The Security Settings dialog box appears.
  5. Click the Prompt or Enable option for Download unsigned ActiveX Controls.
  6. Click the Prompt or Enable option for Initialize and script ActiveX controls not marked as safe for scripting.
L00090726:An error is displayed in the Wonderware Information Server Portal when the sample reports for Alarm and Historian are accessed and deployed using the Deploy Reports Utility. This is a limitation of the Tag Picker. The reports that use the Tag Picker, including the sample alarm reports require:
  • A default Historian data source
  • Installation of the Historian samples
L00090847:An error occurs when you access the Alarm Pareto Control in the Wonderware Information Server Portal. To rectify this, launch the Wonderware Information Server Portal using the Run As Administrator command.
L00091048:Custom static reports are not available for deletion in AFReports Manager -> Static Report. To delete the same, open the ReportParameters.xml file and delete the entry along with the source file.
L00091053:An error occurs when you access the Reports link in the Wonderware Information Server Portal after logging in as a system administrator and not as a portal admin of the Wonderware Information Server installed node.

To avoid this error, perform any one of the following workarounds:

  • Start Internet Explorer using Run As Administrator command and navigate to the portal using the system administrator credentials.
  • 1. Start Internet Explorer using Run As Administrator command with the credentials of the user who had configured the Information Server feature and type the URL http://localhost/reports/.
    2. Click Properties -> New Role Assignment.
    3. Type the System administrator’s user name and grant the roles by selecting the check boxes for the Content Manager option.
Archestra License Manager 2014

Versions Prior to Wonderware Information Server 3.1

L00055354:It is not possible to log on to Wonderware Information Server if the account name contains Asian double-byte characters. No workaround is available.
L00056077:SQL Server Reporting Services may fail to generate scheduled report snapshots during the fall Daylight Saving Time switchover. Also, time zone offset information may be wrong for snapshots generated during the switchover time period. This is a general issue with Microsoft SQL Server Reporting Services.
L00058228:Errors may occur in reports after changing a data source to point to a SQL Server that uses a different collation. Errors may occur in reports that use collation-sensitive operations if the SQL Server used as the data source uses a different collation than expected. This may be the case when editing the data source definition to point to a different SQL Server than the one that was used when the report was deployed. One report that is affected by this issue is the “Group Period” sample report.
L00058236:When setting up a data source that uses HTTP to connect to a historian, the Test Connection feature tests a direct SQL Server connection, not an HTTP connection. This behavior is as designed. Only clients use HTTP mode to establish a historian connection. Wonderware Information Server itself still requires a direct SQL Server connection. Therefore, the Test Connection feature tests the direct connection, not the HTTP connection.
L00058401:Preview of content unit crashes when the query is configured for 1000 alarms and display type is SmartSymbol. When you import an InTouch window with 1000 alarm records logged into the database and then configure a content unit with a display type of SmartSymbol, the total number of symbols = 1000, links = binding, and target = contentunit, the preview crashes.
L00058623:Additional steps may be necessary to establish a connection to an Oracle database. To set up a data source to connect to an Oracle database, some additional configuration steps may be necessary. See the following Microsoft article for details: http://support.microsoft.com/kb/255084.
L00058697:When using the Trend or Query controls in Wonderware Information Server from a client running the Microsoft Windows Vista or Windows 7 operating systems, an Internet Explorer security warning appears, requesting permission to run a program outside of protected mode. To work around this issue, allow the program to run in unprotected mode.
L00059073:Accessing drill-through reports may not work when viewing a report from Wonderware Information Server. In certain situations, you may not be able to access a drill-through report (that is, call a detail report from a main report) when viewing a SQL Server Reporting Services report from Wonderware Information Server. Instead, the main report is generated again or an error message appears. This is due to an issue with the Microsoft Report Viewer control. No workaround is available.
L00059809:Wonderware Information Server is not installed properly when specifying a virtual directory name that contains a percent sign (%). Although virtual directories in IIS are not allowed to contain this character, the setup program does not reject the invalid name. The setup procedure subsequently completes without errors, but the resulting installation is corrupted.
L00059947:When exporting an ArchestrA Reporting sample report to a PDF file, Asian double-byte characters don’t appear correctly. To work around this issue, edit the reports to use a font that supports these characters.
L00060022:When viewing a Process Graphics window that contains an InTouch Alarm Viewer control, Internet Explorer hangs or crashes if the InTouch alarm manager (alarmmgr.exe) isn’t running on the client computer. No workaround is available.
L00060330:When using the setup program’s Modify feature to install or uninstall the ActiveFactory Reporting feature, the ActiveFactory language packs are not installed or uninstalled accordingly. To work around this issue, run the ActiveFactory client setup package on the Wonderware Information Server computer. (The client setup is available under the ActiveFactory node in the Launch Pad.)
L00060369:Runtime errors may occur when using a published InTouch symbol display with a Table Weaver query that returns NULL values. If you use a published InTouch symbol that contains a value display tied to a Real tag to display the results of a Table Weaver query, runtime errors occur if the query returns a NULL value for the column that is mapped to the Real tag.
L00060567:The HideSelf() function may not work in nested popup windows. Calling the HideSelf() function to close a published InTouch popup window that was in turn opened from another popup window may not work. To work around this issue, don’t nest popup windows (that is, open one popup window from another).
L00060576:When using the Tag Picker to select tags as report parameters, the server name in the Server pane may not match the computer name in the URL used to access Wonderware Information Server. For example, if the URL uses the server’s IP address, the Tag Picker still shows the computer’s host name.
L00060930:In time zones whose offset from UTC is a fractional number of hours, scheduled hourly ActiveFactory reports are not executed on the full hour. For example, in a time zone with an offset from UTC of 5 hours and 30 minutes, hourly reports are generated at 1:30, 2:30, 3:30 local time and so on. To work around this issue, edit the schedule in the configuration.config file and specify a start time offset of 30 minutes. Assuming, for example, the <STARTTIME> element for the schedule looks as follows: <STARTTIME>*,*,*,0</STARTTIME> Change it to the following: <STARTTIME>*,*,*,30</STARTTIME>
L00061258:Misleading error message may appear when deploying a report that was developed using Report Builder. When you use the Deploy ArchestrA Reports utility to deploy a report that was developed using Report Builder, an error message may appear that the aaReports data source could not be found. You can ignore this message. The report is deployed correctly.
L00061262:Trend and Query controls in Internet Explorer still use the name of the account you logged into the computer, rather than the name you used to log into Wonderware Information Server. If you:
  1. Install Wonderware Information Server with the ActiveFactory features.
  2. Install a license by pointing to a license server without licenses for ActiveFactory and Active Factory Pro, but with ActiveFactory Web and ActiveFactory Pro Web licenses.
  3. Logon on a client node with a user account different than the default Wonderware Information Server user.
  4. Connect to Wonderware Information Server computer from a remote computer with a different user.

The license status on the Wonderware Information Server License Manager page shows the user logged onto the computer rather than the user logged onto the Wonderware Information Server computer. The reason for this is that the name of the user logged into the computer is used when named licensing is enforced.

L00061351:In the ActiveFactory Reporting web site, browsing from the main pane shows the wrong report list. The system has two sets of scheduled published reports: HOURLY and FIFTEENMINUTES. When browsing through the main (right) pane, drilling down to the HOURLY reports shows the FIFTEENMINUTES reports. The workaround is to use the tree but not the right-hand panels.
L00061655:The Publish option on ActiveFactory Trend is disabled. This can occur with a new InSQL Server and/or when the InSQL Server Runtime database has been rebuilt. In such cases, the tables required for publishing are missing until an ActiveFactory desktop client connects to it or Wonderware Information Server is installed and points to that InSQL computer. Once the tables have been created, the tables can be populated manually using this script (modify the computer names and paths to match your configuration): /* insert the report site */
use Runtime insert aaHistClientReportSite
(SiteURL, SitePath, Description, SiteVersion)
values
(‘http://QAINT273/AFWEB’,
‘C:InetpubwwwrootAFWeb’,
NULL,
1) /* Insert the Report Folders */
declare @sitekey int select @sitekey = ReportSiteKey
from aaHistClientReportSite
where SiteURL = ‘http://QAINT273/AFWEB’ insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘Static’, ‘Static Reports’, 1, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘EVENT’, ‘Event’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘FIFTEENMINUTE’, ‘Every 15 minutes’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘HOURLY’, ‘Every hour’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘DAILY’, ‘Every day’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘WEEKLY’, ‘Every week’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘MONTHLY’, ‘Beginning of every month’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘SHIFT’, ‘Every shift’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘OnDemand’, ‘On Demand Reports’, 2, 0, 0)
L00066339:If an old Wonderware product has been installed, then Invensys License Server is installed and later uninstalled, no Invensys License Manager (LicView) is available on that computer anymore. The workaround is to reinstall the Invensys License Manager, aalicview.exe, from the license installation media.
L00010926:The SuiteVoyager alarm consumer query does not return alarms of contained Wonderware Information Server Areas. The query returns only alarms that are in the specific Area. To work around this, specify each alarm group in the alarm query. The only upper-level group that is handled correctly is the $System parent alarm group from the InTouch alarm provider. This group returns all alarms from the provider.
L00011706:If you use the PI(), StringFromTime(), and StringSpace() functions as expressions for display objects in InTouch, the displays do not resolve correctly in published windows. Work around this problem by introducing a tag into the expression so that the expression is updated in the browser. For example:
  1. Define an analog tag “tag0” and assign it a value 0. Replace the expression PI() with PI() + tag0.
  2. Define a message tag “mtag0” and assign it an empty string. Add “mtag0” to the StringFromTime() and StringSpace() expressions.
L00017054:Run-time errors occur when printing a window in a converted InTouch application. After you clear the error dialog boxes, printing resumes and works properly.
L00033125:If you attach an image to a Content Unit and then replace it with another image, you do not see the change unless Internet Explorer is correctly configured. To configure Internet Explorer:
  1. On the Tools menu, click Internet Options. The Internet Options dialog box appears.
  2. In the Temporary Internet Files group, click Settings. The Settings dialog box appears.
  3. Click Every visit to the page.
  4. Click OK to close the Settings dialog box.
  5. Click OK.
L00033464:Large Table Weaver queries may time out, and results may not be shown. Table Weaver is optimized for queries that produce 1,000 rows or less. While Table Weaver can support larger results, there may be a significant performance penalty. In extreme cases with thousands of results, you may need to increase the IIS application script timeout for the query to complete. Microsoft Internet Explorer may also have trouble showing very large result sets.
L00033701:A “Page cannot be displayed” error message occurs when the tabular display “Rows per view” is configured with a numeric value greater than 32767.
L00041235:Excel files contain Auto_Open() macros to perform a variety of functions when the file is opened. When published in AFRWS these macros do not get run and the report is invalid. The following article describes some of the differences between Auto_Open and Workbook_Open:
http://www.dailydoseofexcel.com/archives/2004/08/18/running-macros-when-a-workbook-is-opened Summary: “The Workbook_Open event resides in the ThisWorkbook module. The Auto_Open macro belongs in a standard module. If you have both, the event procedure will fire before the Auto_Open procedure. Other than their location, the primary difference between the two is what happens when you open a workbook via code. The event will still fire, the Auto_Open macro will not. VBA provides a RunAutoMacros method of the workbook object that allows you to run the Auto_Open code when a workbook is opened through VBA.” Suggested workaround: Instead of “Auto_Open”, use the “Workbook_Open” event. For example: Private Sub Workbook_Open()
Worksheets(“Sheet1”).Range(“A1”).Value = Date
Worksheets(“Sheet1”).Range(“B1”).Value = Time
End Sub
L00044583:ActiveX controls do not install even after adding the SuiteVoyager URL as a trusted site. Problem: When you click the Download/Upgrade button on the Process Graphics window, a dialog box appears with the message “This site might require the following ActiveX control: ‘Wonderware SuiteVoyager client cabinet file’ from ‘Invensys Systems, Inc.’. Click here to Install.”. If you click Install, you see a dialog box with the message “Failed to download the client side software.” This could be due to insufficient privileges. Cause: This happens because of the enhanced security settings of Windows Server 2003 and/or Windows XP SP2, if used as a client. ActiveX must be enabled in the Internet Explorer security settings. Solution: In Internet Explorer click on Tools, Internet Options, Security and select Internet. Click on Custom Level and select Enable for Script ActiveX Controls marked as safe for scripting.
L00046228:To be able to use Backup and Restore capabilities of SuiteVoyager that uses a remote SQL Server as its database, the MSSQLServer and SQLServerAgent services on the remote computer should be running under a network domain account and not a local system account.
L00047046:Backup process times out when backing up a large amount of configuration data. Problem: When you backup a Wonderware Information Server configuration that contains a large amount of data (for example a large published InTouch application) the backup process may time out. Solution: Click Start, Programs, Administrative Tools, Internet Information Services (IIS) Manager. In IIS Manager do the following:
  1. Expand the Internet Information Services node.
  2. Expand your computer name node.
  3. Expand the Web Sites node.
  4. Expand the Default Web Site node.
  5. Right click the SuiteVoyager web site and choose Properties.
  6. On the Virtual Directory tab click Configuration. The Application Configuration dialog appears.
  7. Click the Options tab.
  8. Increase the ASP script timeout value, for example 300 seconds.
L00047233:Adding and removing domain users to user roles with the SuiteVoyager User Manager fails. Solution: Make sure that the users in the SuiteVoyager Administrators role are also in local system Administrators group in the computer where SuiteVoyager server is running in order to add/delete users from the User Managers page.
L00005386:If you upload a file to the Custom Links area of the portal, make changes to the file, and then upload the file again, Internet Explorer may not recognize the change. You can force Internet Explorer to reload the file by changing the cache settings. To configure Internet Explorer:
  1. On the Tools menu, click Internet Options. The Internet Options dialog box appears.
  2. In the Temporary Internet Files group, click Settings. The Settings dialog box appears.
  3. Click Every visit to the page.
  4. Click OK to close the Settings dialog box.
  5. Click OK.
MEDU00000981:The ActiveFactory Reporting Website does not detect language variants when determining the client language to show. Four languages are supported for the ActiveFactory Reporting Website: French, German, Japanese, and Simplified Chinese. The countries supported are France, Germany, Japan, and China. If one of the supported languages is set for Internet Explorer, but a non-supported country is specified, then the ActiveFactory Reporting Website shows the English version. For example, if German(Austria)[de-at] is set for Internet Explorer, the website shows the English version instead of the German version. To work around this problem, add the appropriate supported language/country combination to the Internet Explorer configuration. To add the language/country combination:
  1. Start Internet Explorer.
  2. On the Tools menu, click Internet Options. The Internet Options dialog box appears.
  3. Click Languages. The Language Preference dialog box appears.
  4. Click Add. The Add Language dialog box appears.
  5. Select the appropriate supported language/country entry for the language you want to show: Chinese(China)[zh-cn], French(France)[fr], German(Germany)[de] or Japanese(Japan)[ja].
  6. Click OK.
  7. In the Add Language dialog box, move the selected language to the top of the Language list.
  8. Click OK.
  9. Click OK to close the Internet Options dialog box.
  10. Restart Internet Explorer.

© 2014 Invensys Systems, Inc. All Rights Reserved.

INSTALLATION GUIDE

Description

Step by Step Installation of Wonderware's InTouch version 2014 (11.0)

Author

Jimmy McGlaughlin

Publish Date01/14//2014

Applies to Software

InTouch Classic

Applies to Version

11.0

Applies to System/Module

n/a

Article Version

01.01.01

************************************************************************************************************************************************************

Pre-Requisites

Important!

FactorySuite Gateway (FS Gateway) 3.0 SP1 is installed as a hidden feature of InTouch HMI 2014 (v11.0) in an Wonderware System Platform (ASP) 2014 installation.

  • If you previously installed FS Gateway 2.0 SP1 without any other InTouch products, then installing ASP 2014 will upgrade FSGateway to version 3.0 SP1.
  • If you previously installed FS Gateway 2.0 SP1 as part of ASP 2012 with InTouch 10.5, you must uninstall FS Gateway before upgrading to ASP 2014.

For more information about FS Gateway installation, upgrade, and uninstall, see the Wonderware System Platform Installation Guide, 'InTouch HMI Requirements and Prerequisites' section, 'Installing FS Gateway and Modifying FS Gateway Installations' topic.

System Requirements

Introduction

This section describes the hardware and software requirements to support Wonderware System Platform 2014 products, including InTouch HMI 2014.

Hardware Requirements

Hardware Requirements by Installation Type

The following table lists the hardware requirements of different types of Wonderware System Platform 2014 installations based on the expected number of I/O operations per node.

Hardware Requirements Notes:

Windows 7 and Windows Server 2008 R2 operating systems and SQL Server versions impose hardware requirements that may exceed the minimum requirements for Wonderware Application Server 2014 (v4.0). If you intend to install Wonderware System Platform 2014 on a computer running Windows Server 2008 R2, Windows 8, Windows Essentials 2012, or SQL Server 2012, see the following Microsoft Web sites for a complete list of hardware requirements:

  • www.microsoft.com/windowsserver2008/en/us/system-requirements.aspx
  • www.microsoft.com/windows/windows-8/get/system-requirements.aspx
  • msdn.microsoft.com/en-us/library/ms143506.aspx#EE32

Auxiliary Hardware Requirements

This section describes any optional hardware requirements beyond the specific hardware requirements discussed earlier in this ReadMe.

Alternative Authentication Using Smart Cards

  • Smart Card: Raak Technologies C2-40 Mini Driver Smart Card
  • Smart Card Reader: OK 3021 USB Smart Card Readers

Using Multiple Network Interface Cards

If you are using multiple network interface cards (NICs), you must configure certain settings for the firewall or else a remote node cannot connect to the Galaxy Repository node.

A connection is a term used to define a network interface card (NIC), its settings and the settings of whatever the NIC is connected to. Under certain circumstances, the connection on your computer can change if, for example, the IP address on your network card changes. Your computer's connection can be affected by external factors. During computer startup, and each time a connection changes, the operating system goes through an 'Identifying' process to determine which profile should be assigned to the connection.

A profile is a collection of firewall settings that can be applied to a connection. There are three profiles currently defined in the operating system: Domain, Public, and Private.

  • The Domain profile is active only when the computer can authenticate with a domain controller on all active interfaces such as LAN, wireless, and VPN. The domain profile may be more or less restrictive than the other two profiles depending on network security policies.
  • The Private profile is active whenever the network type for all active network connections on the computer are identified as private networks. The private profile typically is used in a more trusted environment and is less restrictive than the public profile to allow for network discovery.
  • The Public profile is active in all other circumstances. The public profile typically is more restrictive than the private profile because the computer often is connected to the Internet in an insecure location. Network discovery and remote access are disabled rather than explicitly blocking specific traffic. Firewall exceptions and rules can be created on any or all of these profiles.

This is important because the OS Configuration utility and the Firewall utility apply their firewall exceptions to the Domain and Private profiles only.

As previously noted, you can specify which profile you want assigned to a connection as long as that connection is not a Domain connection. This is done through the 'Network and Sharing Center'. Click the Network icon located on the right side of the task bar and then click one of the networks that are shown. You can change a connection from a Public profile to a Private profile. The firewall calls these settings 'Profiles' but the network calls them 'Location types.'

On computers using dual NICs, the first NIC is normally connected to the domain and is assigned the Domain profile automatically. Windows typically assigns the second NIC the Public profile.

The first issue is that your entire computer (all connections) is restricted to the most restrictive of the profiles assigned to any connection. So if the second connection was assigned a profile of Public, none of the firewall exceptions set by the OS Configuration or Firewall utilities will be allowed. The exceptions were set for Domain and Private only, not Public. You must set the second connection to the Private profile for any of the firewall exceptions to work. You want the active profile on the message exchange (MX) NIC to be the profile opened by OS Configuration.

The second issue is that it appears that a restart of your computer, or even a restart of a computer to which you are connected, can change your connection back to the Public profile. Once again the firewall exceptions will not be effective. You'll have to change the connection back to the Private profile after each restart or a restart of the connected computer.

To avoid these NIC issues and prevent the “Identifying” process from taking place on a connection and changing the assigned profile, certain items must be present in the definition of the connection. Follow these rules and procedures:

  • If you have only one NIC, no action is required. The profiles and firewall rules are automatic.
  • To configure two NICs, do the following:

1. If the second NIC is not physically connected to anything (that means no wire in it), no action is required. The profiles and firewall rules are automatic.

2. If the second NIC is connected, it MUST be configured. Follow the rules for configuring a normal redundancy setup provided in the Wonderware Application Server User's Guide and the accompanying online help.

  • Assign the NIC an IP address, subnet mask and gateway address. Typically, these addresses are internal, non-routable addresses. For example, 192.168.1.xx and 10.x.x.x are common addresses of this type.
  • A NIC acting as Redundancy Message Channel (RMC) does not require a default gateway. Otherwise, the gateway can be the same as the IP address. Vista and Windows Server 2008 will identify this NIC and assign it a Private profile.

If you do not configure the second NIC, Windows 7 and Windows Server 2008 will assign a profile of Public to this NIC and cause all of the Wonderware product firewall exceptions to be deactivated on all NICs.

3. Set a security policy so that Windows 7 and Windows Server 2008 do not re-set the RMC NIC to a Public profile on rebooting the system or changing the IP address. To make the Private profile setting persistent, do the following:

  • On the Windows Start menu, click Run.
  • Enter and run this command: SECPOL.MSC. The Local Security Settings menu appears.
  • Select Network List Manager Policies on the menu tree.
  • Select Unidentified Network from the Network Names displayed.
  • Right-click, then select Properties, and then change the Location type from Not configured to Private.
  • Exit the menu and return to Windows.

4. If you have more than two NICs, make sure all connected NICs are configured with an IP address.

Operating System, .NET Framework, and Virtualization Requirements

Summary of Software Requirements for InTouch HMI Version 11

The following table lists the operating system, .NET Framework, and virtualization requirements for the suite of Wonderware System Platform products, including InTouch HMI Version 11.

Note: Only those Windows and SQL versions and service packs shown in the following tables are supported for Wonderware System Platform 2014 components.

Software Requirement Notes:

  • The entry for Application Server applies to the ArchestrA IDE (Development Node) and ArchestrA Run time (Application Node).
  • The Galaxy Repository (GR Node) can run on a client Windows operating system only in a single-node configuration.
  • Development and application nodes are considered to be clients of the server GR node.
  • Other .NET Framework versions can coexist except .NET 4.0. But, all scripts in objects run in .NET Framework 4.5. For more information about .NET Framework requirements and compatibility, see .NET Framework Requirements and Compatibility
  • .NET 3.5 is installed by System Platform only because the supported SQL Server versions require it. No other dependencies to .NET 3.5 must exist.

Operating System Notes Common to Wonderware Products

ActiveX Controls Behavior on Windows 7, Windows 2008 R2, and Windows 8 Operating Systems

Due to the Data Execution Prevention (DEP) feature of Windows 7, Windows 2008 R2, or Windows 8 operating systems, any ActiveX control built with ATL version 7.1 or earlier will fail to host or will have unpredictable behaviors in InTouch HMI 11.0 either in WindowMaker or WindowViewer running on supported versions of Windows. For more information, contact Wonderware Technical Support.

Configuring Remote Alarm Retrieval Queries When Running Windows 7, Windows 8, or Windows Server 2008 R2

The process to configure remote alarm retrieval queries has changed for interactive applications such as InTouch HMI when running on Windows 7, Windows 8, and Windows Server 2008 R2.

When InTouch WindowViewer is started and generates alarms from an interactive Windows 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

1. After starting InTouch WindowViewer (alarm provider) on the Windows 7, Windows 8, or Windows Server 2008 R2 node, open the SMC Logger and look for the most recent string generated by AlarmMgr. For example: 'Registering AlarmMgr with SLSSVC as AlarmMgr 253.127.148.120'. The indicated IP address will be unique to your alarm-providing node. Note the IP address.

2. In the Alarm Query tab of the AlarmViewer control on the remote computer, configure the alarm query as follows, substituting your nodename of the alarm providing InTouch HMI for 'nodename' below and substituting your IP address noted in the previous step:

nodename:ip_addressintouch!$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.

3. Test to validate that the alarms generated from the alarm-providing node are shown accurately in the AlarmViewer control.

Wonderware InTouch HMI and Alarm DB Logger

In earlier releases of InTouch HMI that supported Windows Vista, Windows 7, or Windows Server 2008, the Alarm DB Logger could not be enabled to run as a service. The Alarm DB Logger now runs as a Service in Windows Vista and later operating systems primarily to support Galaxy Alarms and InTouch HMI Alarms from Terminal sessions. However, there is a limitation in that the combination of Alarm DB Logger configured as a service and InTouch HMI running locally as a console application is still not supported. If InTouch HMI needs to run in the Console session, the Alarm DB Logger must be configured in the Alarm DB Logger Manager as a 'Normal Application' instead of a 'Windows Service'.

Also, if you are running the Alarm DB Logger as a console application, you cannot run it in the Terminal session until you close the one that is running in as a console application.

Refer to the updated Tech Note 725, 'Running InTouch HMI and AlarmDBLogger Services on Vista and Later Operating Systems,' for full details of the supported scenarios and applicable alarm query syntax.

Terminal Services Behavior in Windows Server 2008 and Later Operating Systems

In a change from Windows Server 2003, Windows Server 2008 and later Windows versions 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 or later, Session 0 is no longer an interactive session, and is reserved only for Windows services. From Windows Server 2008 and later, all remote connections are treated 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.

In another aspect of Terminal Services behavior, InTouch HMI functions such as TSEGetClientID() can return a null value when running on Windows 2008 SP2 and Windows 2008 R2 operating systems with InTouch running in a remote desktop (RDP) client session. The cause of this behavior is that the relevant roles are not installed on the Terminal Server. You must install the 'Terminal Server' role for Windows 2008 SP2 or the 'Remote Desktop Host' role for Windows 2008 R2 in order for TSEGetClientId() and other related functions to work properly.

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.

Wonderware Application Server and InTouch HMI detect when the application is running in the console. In Windows Server 2008 R2 and later, it implies that the application was started by a user physically at the machine. However, this behavior requires that you disable Fast User Switching in both Windows 7 and Windows Server 2008 operating systems.

When running Windows Server 2008 or later versions of Windows, you must modify the terminal services behavior for the Wonderware software to operate properly.

Wonderware software detects when an application is running in the console. From Windows Server 2008 and later versions of Windows, all remote connections are treated as a remote RDP session regardless of /console or /admin switches in the mstsc connection.

To disable fast user switching through the Group Policy interface

1. Click Start and then Run. The Run dialog box appears.

2. Enter gpedit.msc and click OK. The Group Policy dialog box appears.

3. Go to the following location: Local Computer Policy > Administrative Templates > System > Logon.

4. Set Hide Entry Points for Fast User Switching to Enabled. Enabling this policy hides the SwitchUser option in the Logon interface, the Start menu, and the TaskManager.

5. On the File menu, click Exit to close the Group Policy dialog box.

By enabling the policy, Administrators hide the Switch User button in Windows logon, in the Start menu, and in the Task Manager.

Certain editions of Windows Vista do not have the Group Policy editor. So, alternatively, you can configure the Switch User settings through the registry.

To disable fast user switching through the Registry Editor

1. Click Start and then Run. The Run dialog box appears.

2. Enter regedit.exe and click OK. The Registry Editor dialog box appears.

3. Go to the following location: HKEY_LOCAL_MACHINE > SOFTWARE > Policies > Microsoft > Windows > CurrentVersion > Policies > System.

4. Right-click and select DWORD (32-bit) Value. Name it HideFastUserSwitching.

5. Set the HideFastUserSwitching data value to 1.

6. On the File menu, click Exit to close the Registry Editor.

In a Terminal Server environment that has a managed application deployed to it, the following behavior applies to references in the InTouch HMI application to the InTouchViewApp object:

ArchestrA Symbols referencing InTouchViewApp_001.Tag1:

Running on the Console - Refers to the tag value of the application running on the console.

Running in a Session - Refers to the tag value of the application running on the console.

Restarting the Window Viewer application running on the console causes references from the terminal session to disconnect and then reconnect.

InTouch Graphic referencing Tag1:

Running on the Console - Refers to the tag value of the application running on the console.

Running in a Session - Refers to the tag value of the application running in the session.

ArchestrA Graphic referencing InTouch:Tag1:

Running on the Console - Refers to the tag value of the application running on the console.

Running in a Session - Refers to the tag value of the application running in the session.

InTouch Graphic referencing Galaxy:InTouchViewApp_001.Tag1:

Running on the Console - Refers to the tag value of the application running on the console.

Running in a Session - Refers to the tag value of the application running on the console.

Wonderware InTouch HMI 2014 (v11.0) Operating System Notes

The following table lists the supported operating systems that can be installed on computers that run InTouch HMI server and client components.

Notes:

2014
  • The recommended operating system for a Galaxy Repository is Windows Server 2008 R2 SP1.
  • Microsoft Windows 7 SP1(32-bit or 64-bit) is the recommended operating system to run InTouch HMI client components.
  • Microsoft Windows Server 2008 R2 SP1 is the recommended operating system to run InTouch HMI server components.
  • The recommended operating system for InTouch HMI development is Windows Server 2008 R2 SP1 or Windows 7 SP1.
  • The recommended operating system for run-time nodes is Windows 7 SP1.
  • Window 7 SP1 Embedded is supported on compact systems only.

Wonderware InTouch HMI 2014 (v11.0) with Windows 7 and Later Versions of Windows

  • The following InTouch legacy script functions do not operate on 64-bit versions of Windows: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and SendKeys().
  • If Recipe Manager is started using the path StartProgramWonderwareInTouchRecipe, then select Run as Administrator on Windows 7 or later operating systems.
  • The InTouch Extensibility Toolkit might need to be started by right-clicking and selecting Run As Administrator on Windows 7 or later operating systems to function properly.
  • The onscreen keyboard options have changed for the Windows 7 and Windows Server 2008 R2 operating systems.
  • Hovering to select from the Windows keyboard does not work in the Windows 7 Professional and Windows Server 2008 R2 Standard operating systems.

Wonderware InTouch HMI 2014 (v11.0) View Applications and DDE Support

Windows 7 and Windows Server 2008 do not support NetDDE 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.

Windows Server 2003 and Windows XP Pro still support NetDDE.

In ArchestrA Symbols, InTouch:‹tagname› is still a valid method of referring to an InTouch tag on a local node.

Wonderware InTouch HMI 2014 (v11.0) Support for Windows User Account Control

Wonderware System Platform 2014 with InTouch HMI v11.0 supports User Account Control-enabled operations on run-time nodes. You must disable User Account Control (UAC) before installing Wonderware System Platform 2014 and before performing Configurator operations. UAC also must be disabled on IDE and GR nodes.

.NET Framework Requirements and Compatibility

IMPORTANT: We strongly recommended that prior to upgrading your existing applications to Wonderware System Platform 2014, that you back up your applications, become familiar with the changes introduced by Microsoft in .NET 4.5, and that you review your .NET scripts and .NET controls for any required changes. We also recommend you test the upgrade in a staging system prior to upgrading your production system.

Wonderware System Platform 2014 leverages Microsoft .NET Framework 4.5. The Wonderware System Platform installation program will install .NET 4.5 if it is not already present in your system. If .NET 4.0 is your current .NET version, note that it is possible for .NET 4.0 and .NET 4.5 to coexist in the same machine. In this scenario, ASP 2014 will use .NET 4.5. Other applications you may have on the same machine with dependencies on .NET 4.0 will access .NET 4.5.

Although .NET Framework 4.5 is highly compatible with applications that are built with earlier .NET Framework versions, Microsoft has introduced changes in .NET 4.5 to improve security, standards compliance, correctness, reliability, and performance that may require changes to .NET scripts you may have created with Wonderware System Platform 2012 and earlier versions of Application Server, InTouch HMI, the Historian, Historian Client, and Wonderware Information Server. These changes may also affect .NET controls developed with .NET 4.0.

Virtualization Support

Wonderware System Platform 2014 supports the following virtualization environments:

  • Microsoft Hyper-V: based on the supported operating system version
  • VMware 5.0: basic virtualization without High Availability and Disaster Recovery
  • VMware VSphere 5

SQL Server Requirements for All Wonderware Components

The following table lists the SQL Server requirements for Wonderware System Platform 2014 components, including InTouch HMI 2014. The recommended environment is a 64-bit operating system and SQL Server 2008 R2 SP2, Standard, Enterprise, 32/64-bit.

Note: SQL 2012 SP1 Express is installed automatically if no other version of SQL Server is installed on the computer where InTouch HMI 2014 will be installed.

SQL Server Notes Common to All Wonderware Products

SQL Server Rights Requirements

SQL Server 2008 does not automatically create the BUILTINAdministrators role delivered in SQL Server 2005. Because of this change to SQL Server, the Wonderware Application Server 2014 (v4.0) installation process will create the necessary operating system user group (aaAdministrators) as well as the necessary SQL Server role. This automated process will provide the rights required to allow operations within the Galaxy Repository without the need for blanket BUILTINAdministrator rights. The aaAdministrators group must be present and enabled. If you accidentally delete the aaAdministrators group from the Windows operating system, you can run either of two options to restore it:

  • Run the Change Network Utility from the Windows Start menu.
  • Run the aaConfig SQL Utility from the Windows Start menu.

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.

Alarm Client and Trend Client Prerequisites

The Trend Client is compatible with the following Wonderware products:

  • Wonderware InTouch HMI 10.1, 10.1 SP2, 10.2, 10.5, 10.6, and 11.0
  • Wonderware Application Server 3.1, 3.1 SP1, 3.2, 3.5, 3.6, and 4.0
  • Wonderware Historian 9.0, 10.0, 10.5, and 11.5
  • Wonderware Historian Client 10.0 SP1/SP2, 10.1, 10.2, and 10.5
  • ActiveFactory 9.2
  • QI Analyst 8.0 SP2

InTouch Access Anywhere Requirements

The following sections describe the requirements to run Wonderware InTouch Access Anywhere Server and supported browsers. For detailed information, see the Wonderware InTouch Access Anywhere documentation.

Requirements

The InTouch Access Anywhere Server can be installed as a Wonderware System Platform installation option. The InTouch Access Anywhere Secure Gateway is an optional component installed on a separate computer within a DMZ.

The following requirements must be met before you install the InTouch Access Anywhere Server or a Secure Gateway.

  • Wonderware InTouch Access Anywhere must be installed on the same RDP Server computer as Wonderware InTouch HMI 2012 R2 (version 10.6) or later.
  • Remote Desktop (RDP) must be enabled and properly configured on the host computer. For information and guidance, see Tech Note 782, 'Installing Remote Desktop Services on Windows 2008 Server R2 for Wonderware Products'. You also can refer to http://technet.microsoft.com/en-us/l.../dd883253.aspx.
  • You must install an InTouch 2012 R2 TSE Concurrent License on the same computer as your Wonderware InTouch and InTouch Access Anywhere Server installations.

Supported InTouch Access Anywhere Browsers

Wonderware InTouch Access Anywhere can run on smart phones, tablets, laptop computers, or any other device that supports an HTML5-compliant web browser. Browsers supported by Wonderware InTouch Access Anywhere include the following:

Browsers Tested with InTouch WindowViewer

  • Internet Explorer 11
  • Internet Explorer 10
  • Firefox 22
  • Safari 7
  • Chrome 28
  • Opera 15

Functionally Compatible Browsers

Certain versions of the following browsers may be functionally compatible with InTouch Access Anywhere, but have not been tested running InTouch HMI.

  • Firefox 4-21
  • Safari 5, 6
  • Chrome 11-27
  • Opera 11-14

You are strongly recommended to upgrade to one of the supported browser versions listed in Browsers Tested with WindowViewer. For a complete list of considerations to run an InTouch application with InTouch Access Anywhere on a portable device, see the InTouch Access Anywhere User Guide.

Wonderware InTouch HMI 2014 (v11.0) Component Compatibility

In a single-node environment, if you need to combine multiple components delivered within Wonderware System Platform 2014, all components need to be at the versions delivered in Wonderware System Platform 2014.
In a node-to-node environment, components are compatible between the current licensed version and one licensed version back.

The following table lists Wonderware component products and their compatibility with InTouch HMI 2014 (v11.0).

In some cases, the Wonderware InTouch HMI is supported in newer environments than a compatible product. Wonderware InTouch HMI has been tested for compatibility with a listed product only in the environments that are supported by that particular product.

Detailed Steps

Performing the InTouch HMI Installation

Before you start installing InTouch HMI, you should have a clear idea whether you want to develop, deploy, and publish your own applications, or require only the InTouch run time, to run applications already created and deployed.

The following procedure will guide you through the installation, with information specific to the InTouch HMI.

To install the InTouch HMI

  1. Insert the installation DVD into the computer’s DVD drive.
  2. Using Windows Explorer, manually start the installation by double-clicking setup.exe on the DVD.
  3. Follow the prompts to commence the installation and to install system prerequisites, as necessary.
  4. The installation program prompts you to select an installation type: either product-based selection or installation by computer roles. As you are installing a single product—InTouch HMI—click the product-based selection as your installation type
  5. Choose the components you want to install.
    1. If you choose InTouch Run Time Only, the following will be installed:
      • InTouch Run Time
      • InTouch documentation
      • Alarm DB Logger
      • FS Gateway (as a silent installation)
      • Application Server Bootstrap
      • InTouch Supplemental Components: InTouch Recipe Manager, InTouch SQL Access, and Symbol Factory
        Note: The 16 Pen Trend supplementary component is not installed by default. You must select the Customize Installation option and select 16 Pen Trend from the product list to install it as part of the InTouch HMI installation procedure.
    2. If you choose InTouch Development and Run Time, the following will be installed:
      • All items listed under step a in these instructions.
      • Application Server Bootstrap, IDE, Galaxy Repository, SQL Server 2012 Express with SSMSE, and Application Server documentation
      • InTouch sample applications
  6. When the installation prompts you to verify your selection, you have the opportunity to customize your installation.
    1. If you choose InTouch Run Time Only, you can add the following components:
      • InTouch sample applications
      • InTouch 16 Pen Trend Supplementary Component:
    2. If you chose InTouch Development and Run Time, you can add the following components:
      • InTouch 16 pen trend
      • InTouch Access Anywhere
  7. After you verify and customize your selection, you are prompted to select the language you want to install. English is selected by default, but you can choose another language.
  8. Follow the subsequent installation steps to:
    1. Accept the End User License Agreement.
    2. Create a new ArchestrA user account, or specify an existing account.
    3. Install any prerequisite software components not yet installed on the computer.
  9. The installation proceeds to completion. You must restart the computer after completing the installation.

Installing Your Invensys Product License

Wonderware enforces the use of its products with a software license. After you install a Wonderware product, you must install a single license file, ARCHESTRA.LIC, which contains your customer information, product data, and software features. Until you apply your Wonderware license, you can only run the InTouch HMI in demonstration mode.

You use the Invensys License Manager to install the contents of the ARCHESTRA.LIC file on the computer where InTouch HMI has been installed. The Invensys License Manager is included as an Invensys component when you install the InTouch HMI.

To install your Wonderware product license

  1. Start the Invensys License Manager by doing the following:
    1. Place the installation DVD in the computer's DVD drive.
    2. Click Start from the Windows desktop, and then click All Programs to show the Invensys folder.
    3. Click the Invensys folder, and then click the Invensys License Manager folder.
    4. Click Invensys License Manager.
  2. Click File, and then Install License File. The Choose a License File to Install dialog box appears.
  3. Browse the installation DVD, select the ARCHESTRA.LIC file, and click Open.
  4. The Destination Computer for Installation dialog box appears. Type the domain and computer names.

  5. The Invensys License Manager copies the ARCHESTRA.LIC file to the C:Program FilesCommon FilesArchestrALicense folder on the selected computer.

Antivirus Software Exclusions

After installing Wonderware InTouch HMI Version 11.0, configure your antivirus software to avoid scanning archive files.

Antivirus software should not scan files in the following ArchestrA folders for 32-bit operating systems:

  • C:Program FilesArchestrA
  • C:Program FilesCommon filesArchestrA
  • C:Program FilesFactorySuite (The FactorySuite directory may not exist in newer installations)
  • C:Program FilesWonderware
  • C:InSQLData
  • C:Documents and SettingsAll UsersApplication DataArchestrA
  • C:HistorianData

For 64-bit operating systems, the exclusion must reflect the (x86) program files directory instead:

  • C:Program Files (x86)ArchestrA
  • C:Program Files (x86)Common filesArchestrA
  • C:Program Files (x86)FactorySuite (The FactorySuite directory may not exist in newer installations)
  • C:Program Files (x86)Wonderware

From Application Server Platform objects:

  • History Store Forward directory: (if not default)

From Application Server Engine objects:

  • Checkpoint directory location (if not default)

<InTouch Application folder path> including:
C:Documents and SettingsAll UsersApplication DataArchestrA

<SMCLoggerStoragefilepath>. The default is:
C:Documents and SettingsAll UsersApplication DataArchestrALogFiles

SQL Server database files of type:

  • .mdf
  • .ldf

Note: Ensure that the subfolders of the listed directories are also excluded. Specify folder names accordingly if you are using a 64-bit operating system. For example, the program file's root directory in a 64-bit operating system is C:Program Files (x86)... and the application data root directory in a 32-bit operating system is C:ProgramData...

Modifying, Repairing, or Removing the InTouch HMI

To modify, repair, or remove an installation

Archestra License Manager 2014 Free

  1. Insert the installation DVD into the computer’s DVD drive.
  2. Click the Programs and Features option in Windows Control Panel. The list of software installed on your computer appears.
  3. Select the InTouch component, and then click the Uninstall/Change button. The Modify, Repair or Remove Installation dialog box appears.
  4. Follow the prompts to modify, repair, or remove the installation.

Note: The name of the Uninstall/Change button varies depending on the Windows operating system installed on your computer.

Upgrading to Version 11.0 from an Earlier Version of the InTouch HMI

Upgrading InTouch HMI installs Version 11.0 on a computer that has a previous version currently installed. An upgrade removes or uninstalls the previous version of InTouch HMI and installs Version 11.0.

After the hardware and software requirements are met, including the proper operating system, SQL server and other prerequisites, you can upgrade to Wonderware InTouch HMI Version 11.0 from the following versions of the InTouch HMI:

  • Version 10.0 SP2
  • Version 10.1 (All service packs and patches)
    • 10.1
    • 10.1 SP2
    • 10.1 SP2 P01
    • 10.1 SP3
    • 10.1 SP3 P01
  • Version 10.6

You can only upgrade Wonderware System Platform products that are already installed and you will not be able to install new products within the Wonderware System Platform that have an upgrade process. The installed components that need to be upgraded are selected and disabled. You can neither clear these check boxes nor select more components during the upgrade.

To upgrade from a previous version of the InTouch HMI

  1. Insert the DVD into your DVD-ROM drive. Run setup.exe to start the set-up program.
    The upgrade feature dialog box appears.
  2. Follow the prompts to complete the upgrade.

Migrating Applications to Wonderware InTouch HMI Version 11.0

Migration converts applications created with earlier versions of InTouch HMI to the current version. You can migrate applications to version 11.0 that were developed with the following versions of InTouch HMI:

  • Version 7.11 P07
  • Version 8.0 SP2 P04
  • Version 9.0 P03
  • Version 9.5 SP1
  • Version 10.0 SP2
  • Version 10.1 (All service packs and patches)
    • 10.1
    • 10.1 SP2
    • 10.1 SP2 P01
    • 10.1 SP3
    • 10.1 SP3 P01
  • Version 10.6

Licensing

For General System Platform 2014 Licensing click HERE

Archestra License Manager 2014 Torrent

Related Videos