Wonderware InBatch 2014 R3 SP1 (v.11.5.1) Readme

Last revision:07/24/2017

About This Readme

This document contains important information about Wonderware® InBatch™ 2014 R3 SP1 (v.11.5.1). Review this document for known issues and changes to the Wonderware InBatch software and documentation included on this CD.

Important! Before upgrading your system, review the Installing Wonderware InBatch 2014 R3 SP1 section.

NOTE: Readme files from previous releases of Wonderware InBatch software are posted to the Wonderware Knowledge & Support Center at https://softwaresupportsp.invensys.com/Pages/ProductHub.aspx.

Release Summary

Wonderware InBatch 2014 R3 SP1(v.11.5.1) offers the following new features and enhancements:

< top of document >

Minimum System Requirements

This section describes the hardware, software, and operating system required to install Wonderware InBatch 2014 R3 SP1 software.

Hardware Requirements

The following hardware is recommended to support Wonderware InBatch 2014 R3 SP1 Client and Server installations:

Requirement Client Server
Processor 1.8 gigahertz (GHz) 2.8 gigahertz (GHz)
Processor Cores 2 4
RAM 2 gigabytes (GB) 8 gigabytes (GB)
Hard Disk 30 GB available 500 GB available
Video Adapter / Monitor Capability 1280 x 1024 resolution 1024 x 768 resolution
Network Speed (MBps) 1000 1000
Input Devices
  • CD-ROM or DVD-ROM drive for installation
  • Keyboard
  • Mouse or compatible pointing device

Hardware Requirements - Operating System

See your specific Microsoft operating system hardware requirements for details.


Operating System Requirements

The following table lists the operating system, .NET Framework, and virtualization requirements for Wonderware InBatch 2014 R3 SP1.


  Client
Windows OS		 Server
Windows OS		 .NET
Framework		 Virtualization
8.1
Professional,
Enterprise
(32/64-bit)		 10 Professional and Enterprise
Standard,
Enterprise
(64-bit)		 2012
Standard,
Data Center
(64-bit)		 2012 R2
Standard,
Data Center
(64-bit)		 2016
Standard,
Data Center
(64-bit)		 3.5 SP1 4.5.2 Hyper-V
(Based on
Supported
OS version)		 VMWare 6.0 Update 1
(including HA/DR*)		 VMWare
Workstation 7.x, 8.x
Wonderware InBatch Server

 N Y Y Y Y C Y Y Y Y
Wonderware InBatch Clients Y Y Y Y Y C Y Y Y Y
Wonderware InBatch History Server N Y Y Y Y C Y Y Y Y
Wonderware InBatch Reporting Content Y Y Y Y Y C Y Y Y Y

 

Supported Y
Not Supported N
Coexist C

 

Notes:

Browser Requirements

Browser Version
Internet Explorer Version 11 or later on the Windows operating system*
Microsoft Edge Version 20
Chrome Version 47 or later on the Windows operating system*
Firefox Version 44 or later on the Windows operating system*

* Unless later versions of browsers deprecate the user interfaces used by InBatch Reporting system.

Microsoft SQL Server Requirements

The following table lists the SQL Server requirements:

  2012 Standard, Enterprise (32/64 bit) 2012 SP2 Express-SSMSE (32/64 bit) 2012 SP1 Standard, Enterprise (32/64 bit) 2012 SP2 Standard, Enterprise (32/64 bit) 2014 Standard, Enterprise (32/64 bit) 2014 SP1 Express-SSME (32/64 bit) 2016 Standard, Enterprise (32/64 bit)
Wonderware InBatch Server

 N/A N/A N/A N/A N/A N/A N/A
Wonderware InBatch Clients N/A N/A N/A N/A N/A N/A N/A
Wonderware InBatch History Server Y Y* Y Y Y Y* Y
Wonderware InBatch Reporting Content Y Y* Y Y Y Y* Y

 

Supported Y
Not Supported N

 

* History Archive, Purge, and Restore will not work with SQL Express. Reporting only works with Express with Advanced Services and Reporting Scheduling Capabilities will not be available.

Additional Software Requirements

The following table lists the additional typical software requirements for each Wonderware InBatch station type when the Wonderware InBatch software is used with Wonderware System Platform:

Additional Software Requirements
Wonderware InBatch Station Type
Server
Run-time
Client
Development
Client
History
Server
Reporting
Content
Redundant
System

Wonderware Application Server bootstrap and IDE
Yes
-
Yes
-
-
Yes
Wonderware InTouch
-
Yes
-
-
-
-

Wonderware InBatch Firewall Exceptions List

Wonderware InBatch requires certain network ports to be opened in the Windows Firewall to establish communication with other components and services on the network. Usually, this is automatically done during the installation and configuration process of Wonderware InBatch. However, if the Windows firewall is not enabled at the time of installation or if an alternative firewall is in use during installation, you need to open the appropriate network ports in the firewall manually for proper functioning of InBatch. The following is a list of ports that must be added to the Windows Firewall exceptions list for Wonderware InBatch:

< top of document >

Product Compatibility

Wonderware InBatch 2014 R3 SP1 is compatible and can co-exist with the following components. Compatibility means that the products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer.

Component Version Compatibility Co-existence
Wonderware® System Platform*
2017 Y Y
2014 R2 SP1 Y Y
2014 R2 P01 Y Y
2014 R2 Y Y
Wonderware® ASB Framework
4.0.0.13000 Y Y
4.1.0 Y Y
Wonderware® InTouch® CE 10.1 N N
Wonderware® MES
2014 R3 N/A Y
2014 R2 N/A Y
2014 SP1 (v5.0.1) N/A Y
2014 (v5.0) N/A Y
2012 P01 (4.5 P01) N/A Y
4.0 SP2 N/A Y
4.0 SP1 N/A N
Wonderware® QI Analyst™
8.0 SP4 N/A Y
8.0 SP3 N/A Y
8.0 SP2 N/A Y
Wonderware® Intelligence™
2014 R3 Y Y
2014 R2 P1 (v2.0 P1) Y Y
2012 (v1.5.100) Y Y
1.5 N N
ArchestrA® Workflow™ 2012 R2 SP1 N/A Y
Wonderware® Skelta BPM™
2017 N/A Y
2014 R2 SP2 P01 N/A Y
2014 R2 SP2 (v4.3) N/A Y
2014 R2 (v4.1) N/A Y
2014 (v4.0) N/A Y
Wonderware® Production Execution Module 2.1 SP1 N/A Y
Foxboro® Control Software
6.0 (and all Quick Fixes) N N
5.0 (and all Quick Fixes) N N
4.0 (and all Quick Fixes) N N
Foxboro® Evo Control Core Services
9.3 Y Y
9.2 Y Y
9.1 Y Y
9.0 Y Y
Foxboro® I/A Series Software
8.8 Y Y
8.7 (Windows XP, Windows 2003) Y Y

 

Supported Y
Not Supported N
Products do not share data directly, but can coexist. N/A

 

* Previously called ArchestrA System Platform

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

For compatibility information regarding Wonderware InBatch 2014 R3 SP1 and Foxboro Control Software 6.0, contact your Schneider Electric sales representative.

< top of document >

Licensing

Wonderware Component Licensing

Please contact your local Schneider Electric Distributor or Sales representative for details about the licensing requirements for Wonderware components.

Wonderware InBatch 2014 R3 SP1 supports Archestra.lic license files. Archestra.lic format licenses work with Wonderware InBatch 2012 R2 and later.

Note: You need a separate MXAccess_Runtime entitlement license file to access the MxAccess Toolkit for IBMX to work when using Wonderware System Platform 2017.

< top of document >

Installing Wonderware InBatch 2014 R3 SP1

Special Notes

Installing or Upgrading

For installation and upgrade instructions, see the Wonderware InBatch Installation Guide and the Installation Issues section of this document.


Upgrading the software from the versions listed below only requires running the Setup.exe:

The process will upgrade all components as required.

The following is a list of important points that you must note during the upgrade process.

Note: If you are using the InBatch GUI Controls and upgrading from 10.2 or earlier, you may need to adjust some of your InTouch application layouts. Some of the controls have been increased in size to better accommodate larger values. Also, a new "Formula" column was added to several list controls.

< top of document >

Resolved Issues

This section describes important resolved issues.

L00141388: InBatch Operator Comments are not stored correctly in the database when the user uses Czech Republic region and language settings. This issue is resolved.
L00142067: User can now configure InBatch Redundancy settings through the silent install.
L00142157: InBatch GUI Controls displays access denied error if the font information is not fetched from the container. This issue is resolved by modifying the InBatch GUI controls to set a default font.
L00142813: The Model Import/Export utility sometimes corrupt a CfgModelDB if you copy a Process or Transfer Phase that has System tags linked to Phase Parameters. This issue is resolved by fixing the limitations that were the cause of corruption.
L00142093: Exiting of the Security Manager, Environment Manager, and Information Manager due to unknown data in their TCP/IP connections is now fixed. The fix allows the system to continue running and even prints available diagnostics.
L00142683: Import process used to get skipped if renamed Process/Transfer Template was already present in the Galaxy. This issue is now fixed.
L00142673: When "graphicInfo.WindowType = aaGraphic.WindowType.Modal" is used in the script for display of BatchList Control, the font for ListControl in the GuiControls module is set and reloads the columns of the control only for the first time. This was creating abnormal behavior in the Batch field control. The problem is now fixed by changing the logic that reloads the columns on each click.
L00143474: Issue related to IBMX crash is now resolved.
L00143522: Scheduled reports failed to execute because default Parameter ReportingTimeZone is missing for some Reports(BatchList, Batch Questions, Batches By Material and Document View Events). This issue is resolved now by adding the default value for "ReportingTimeZone."
L00143560: MaterialSrv initialization did not get completed by the time remote procedure calls were made. Hence it resulted in the error. This issue is resolved now by modifying the MaterialSrv Init method to finish initialization before any procedure calls happen.
L00143121: InBatch Security now allows the use of "&" character in the User ID and User Name while logging on to the InBatch application.
L00144314: Recipe Editor encountered initialization issues and crashed. This issue is resolved now.
L00144517: Description and Unit of Measures are now created as extension attributes for all the phase parameter type tags.
L00144886: Report name now displays with diacritics in InBatch Report Administrator and Phase properties - Report window.

< top of document >

Known Issues

This section describes important known issues.

Installation Issues

837279: Change Network Account utility crashes when user tries to change the Account ID after uninstalling Wonderware System Platform 2017 on a node where InBatch is installed.

To resolve this error, user should reinstall the "Application Server and InTouch OMI Runtime" component of Wonderware System Platform 2017 and then change the Network account again.

Note: Application Server and InTouch OMI Runtime component is the minimum requirement for this workaround. However, user may install other components of Wonderware System Platform 2017 along with this component.
616969: Configuration of History Server feature fails when you upgrade InBatch History Server to InBatch version 11.5.1 from versions prior to InBatch 11.0.

Make sure that you delete all SQL Jobs related to Archive\Purge\Restore before proceeding with the upgrade. Prior to InBatch 11.0 version, any SQL Agent jobs (Archive\Purge\Restore jobs) created in InBatch History Server might have been associated with BatchAdminUser, BatchReportAdmin or BatchUser role. These user roles have been removed in 11.0 release.

L00107356: Due to the large number of services running on IA Series platforms, the installation program should check the value of the SessionViewSize registry setting. It is likely that this registry value does not exist and will need to be created. If you ever notice that services unexpectedly fail to start, the value of this setting may be too small. Follow these steps:
  1. Open the Registry Editor.
  2. Navigate down to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management].
  3. If a registry value named SessionViewSize exists, make sure it is at least 30 (hex) or 48 (decimal).

If it does not exist, create a new DWORD value named SessionViewSize and set it to 30 (hex) or 48 (decimal).
L00127339: Machine names in redundant systems must be 12 characters or less.

Other Issues

455938: Reports header user interface fields are not displayed correctly if you access the InBatch Reports using Internet Explorer 11. Note This issue is reported only on a system with SQL Server 2012.

Workaround: To resolve this issue, add the target site to Compatibility View Settings in Internet Explorer browser.
459424: Make sure to adjust your InTouch application layouts to account for the new Formula column in the lists if you are using GuiControl lists (ScheduleEdit.Schedule, BatchView.Batch, and BatchView.AllocationQueue). Other GUI Control list widths may have also been increased to support better presentation of longer values.
614956: SSRS report execution (i.e. when you open the report and click 'View Report') displays a blank page in Chrome browser.

To resolve this error, do the following:

  1. Browse to the Directory where reporting services is installed. For example: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer.
  2. Open the file named reportserver.config.
  3. Insert the following line in the document:

    <Configuration >
    .......
    <HTMLViewerStyleSheet > SafariChromeFix </HTMLViewerStyleSheet>
    .......
    </Configuration >

  4. Save the file.
  5. Next, navigate to the C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\Styles directory.
  6. Now, make a copy the file named SP_Full.css and name the copy SafariChromeFix.css.
  7. Update the following lines to the top in the SafariChromeFix.css file:

    div { overflow: visible !important; }

  8. Save and close the file.
Once this is saved, all of the existing reports on this instance of Reporting Services will render on all browsers including Chrome and Safari.

Note: It is possible that the reportserver.config will be overwritten with updates to reporting services and you may have to add the <HTMLViewerStyleSheet > SafariChromeFix </HTMLViewerStyleSheet> tag into the config file every time.
L00077400: Editors are not opening on the Wonderware InBatch development client.

Use the following workaround:

  1. Open a Microsoft Windows Explorer page.
  2. Navigate to C:\Programs\Wonderware\Wonderware InBatch\cfg\Config_A.
  3. Right-click the file vista.taf and select Delete.
L00081552: Running Wonderware InBatch with IA components in a redundant configuration does not fail over when IADriver is shut down.

The following table shows the redundancy status on master/backup nodes when IBMX, IBCli, and IADriver are stopped from the Runtime Services dialog box or when you end the process from Task Manager.

 
IBMX
IBCli
IADriver
Action on the master node Master Node Status Backup Node Status Master Node Status Backup Node Status Master Node Status Backup Node Status
End process from Task Manager
(Correct Failover)		 Master failed Master with invalid backup Master failed Master with invalid backup Master failed Master with invalid backup
Stopped from Runtime Services
(Non-Failover)		 Master with valid backup Valid backup Master with valid backup Valid backup Master with valid backup Valid backup

 
L00082366: Unable to import Wonderware InBatch tags to InTouch using DBload.exe.

Wonderware InBatch uses a dot (.) instead of a hyphen (-) as a delimiter in tag names. InTouch supports only a hyphen as a delimiter. Before you load the Wonderware InBatch tag names into InTouch, edit the .CSV file and replace the dot delimiters with hyphens.
L00082612: Custom-created reports that are populated to the batch report directory are not available for configuration and scheduling.

Use the following steps to configure and schedule the custom reports. For example, suppose that a report named "Custom Batch Detail" is populated in the list.

You must update the RptServicesConfig.xml file in the following location:

<systemdrive>:\Inetpub\wwwroot\ReportWeb\ReportConfig

  1. Open the file RptServicesConfig.xml for editing.
  2. Add the following line under the <Reports> node:

    <Report Name="Custom Batch Detail" file="CustomBatchDetail.rdl" description="My Custom Report" />

  3. Save the file.

Now the report named Custom Batch Detail is available for configuring and scheduling. Add a similar line for each custom report that is populated in the Execute Reports list.
L00098867: When using the IBCli application, some I/O Servers or DAServers (including FS Gateway) may report an error about an "Unknown Watchdog" tag. This error is only reported when IBCli starts, but the Watchdog tag will still function as expected.

If you get the following errors from IBCli:

  • Too many ping timeouts (NOTE: only if you get this error repeatedly).
  • Failed to register 'Watchdog' ping tag - pinging is disabled.

Do one of the following:

  • Try to upgrade to a newer I/O Server or DAServer version.
  • Create a tag called Watchdog in the I/O or DAServer. It can be any data type.
  • Disable pinging using the IBCli Disable Ping option.
L00106510: When you try to print Wonderware InBatch reports, the following error appears: "Unable to load client print control".

For instructions about how to resolve this issue, see Tech Note 648, "Troubleshooting ArchestrA Reports Printing Problems," that is available from the Wonderware Technical Support website.
L00125348: If you use the import utility in preview mode, no warning messages are shown if the utility imports a Wonderware InBatch ModelDB in which any of the following have duplicate names (case sensitive): processes, transfers, segments, units, connections, phases. However, the import utility does show a warning when you do the actual import.
L00126972: Users do not need to be an Administrator for DoneBy/CheckBy to work. However, they do need the "Impersonate a user after authentication" permission set in the Local security policies.
L00128201: Running the cvtmaster a second time results in conversion failure.

Use the following workaround:

  1. Create a new folder, and name it something other than Config_A (e.g. test).
  2. Copy the contents of the Config_A folder to the folder you just created.
  3. Run cvtmaster, directing it to the new folder.
  4. Copy the database from the new folder to the Config_A folder.
L00139186: Error and warning messages related to ReportQueueReader are logged in SMC logger after you enable the Enhanced security mode using "aaConfigSQL" tool.

To resolve this error, make sure that the ServiceDB user configured to run InBatch ReportQueueReader service have access to printers and can print.

< top of document >

Known Issues – Documentation

Newer operating systems no longer include the WinHlp32.exe Help viewer component, which is required for viewing .hlp files. The Wonderware InBatch software includes the following .hlp files:

To view these Help files, download and install the viewer component from Microsoft at http://support.microsoft.com/kb/917607.

< top of document >

Wonderware InBatch Documentation

The Wonderware InBatch documentation set includes the following:

The Wonderware InBatch product library consists of a set of Portable Document Files (PDF) located in the UserDocs folder of the Wonderware InBatch installation CD. Install the Adobe Reader on your computer to view the Wonderware InBatch documentation. You can download the latest version of the Adobe Reader from the Adobe Corporation web site:

www.adobe.com/products/acrobat/readstep2.htm

After installing the Adobe Reader, double-click a PDF file to view the book. Click the Open command on the File menu to open a book in the Adobe Reader.

The Wonderware InBatch installation instructions are located in the root folder of the Wonderware InBatch installation CD, as a .chm file. You can view these instructions by clicking the Help when you start the Wonderware InBatch installation procedure.

< top of document >

Resource File

The following list of message is modified in the Wonderware InBatch v11.5.1:

Resource Name Message New/Modified Notes
Common.csv
lblCommentsComments.New

< top of document >

© 2017 Schneider Electric Software, LLC. All rights reserved.