Wonderware InBatch 2017 (12)

Материал из archestra.info
Перейти к: навигация, поиск

Batch Management 2017 Readme

Batch Management 2017 Readme

Last revision: 11/14/2018

This document contains important information about Batch Management 2017 (v.12). Review this document for known issues and changes to the Batch Management software and documentation included on this CD.

In This Document

Release Summary

Minimum System Requirements

Product Compatibility

Licensing

Installing Batch Management 2017

Resolved Issues

Known Issues

Known Issues - Documentation

Batch Management Documentation

Resource File

Release Summary

Batch Management 2017 (v.12) offers the following new features and enhancements:

  • New Product Name

    InBatch is now Batch Management. However, in some instances, you may see “InBatch” in upgrade path, batch reports, and so on.

  • Batch Management

    The Batch Management web client provides a read-only web view of all active batches, securely through an SSL certificate.

  • Batch Auto Start

    Support has been added for automatically starting single or multiple initialized batches.

  • Extended .Net Controls to include OcxBatch and BatchSecCtrl
    • Support has been added for OcxBatch control. This control is used for scheduling, monitoring, and controlling batches through ArchestrA scripting.
    • Support has been added for BatchSecCtrl control. This control is used for accessing Batch Management security through ArchestrA scripting.
  • Support for the latest version of Licensing components

    Batch Management leverages the latest Licensing components. For more information, refer to the Licensing section.

  • Support for Historizing Parameter Extensions

    Support has been added for storing HighDeviationValue, LowDeviationValue, HighLimitValue, and LowLimitValue for Process Variables and Material Input.

  • Removed dependency on ArchestrA Network account user

    EnvMngr, SecMngr, and HistQMngr services now use the Service Admin Access credentials provided during configuration, instead of the ArchestrA Network Account user.

  • Extended Stateless APIs

    Support has been added for new Batch Management APIs for Batch, BatchSecurity, Model, Recipe, and Schedule classes.

Minimum System Requirements

This section describes the hardware, software, and operating system required to install the Batch Management software.

  • Hardware Requirements
  • Operating System Requirements
  • Browser Requirements
  • Microsoft SQL Server Requirements
  • Additional Software Requirements
  • Firewall Exceptions Lists

Hardware Requirements

Minimum Hardware Requirements

The following hardware is recommended to support Batch Management:

Hardware 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 Batch Management 2017.

Operating System

Client

Windows OS

Server

Windows OS

.NET Framework

Virtualization

 

8.1

Professional,

Enterprise

(32/64-bit)

10
(Build 1607 +)

Professional and Enterprise (32/64-bit)

2012

Standard,

Data Center (64-bit)

2012 R2

Standard,

Data Center (64-bit)

2016

Standard,

Data Center (64-bit)

3.5.1

4.7.1

Hyper-V

(Based on Supported OS version)

VMWare 6.0 Update 1

(including HA/DR*)

VMWare Workstation 11 and higher

Batch Management Server

N

N

Y

Y

Y

C

Y

Y

Y

Y

Batch Management Clients

Y

Y

Y

Y

Y

C

Y

Y

Y

Y

Batch Management History Server

N

N

Y

Y

Y

C

Y

Y

Y

Y

Batch Management Reporting Content

Y

Y

Y

Y

Y

C

Y

Y

Y

Y

Supported

 

Y

Not Supported

N

Products do not share data directly, but can coexist.

N/A

Notes:
- For software requirements for the "Batch Management Components for ArchestrA IDE" feature, see the software requirements for Application Server.
- For software requirements for the "Batch Management Reporting Content" feature, see the software requirements for Microsoft SQL Server.
- If a supported version of the Microsoft .NET Framework is not installed, the Batch Management installation automatically installs it.

Browser Requirements

Application Name

Supported Version

Internet Explorer

Version 11 or later on the Windows operating system*

Microsoft Edge

Version 20

Google 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 Batch Management Reporting System.

Microsoft SQL Server Requirements

The following table lists the Microsoft SQL Server requirements.

 

2012 Standard, Enterprise
No SP, SP1, and SP2 (32/64 bit)

2012 SP2 Express -
SSMSE -
No SP, SP1, and SP2
(32/64 bit)

2014 Standard, Enterprise No SP, SP1, and SP2 (32/64 bit)

2014 Express-SSMSE No SP, SP1, and SP2 (32/64 bit)

2016 Standard, Enterprise

No SP and SP1
(32/64 bit)

2016 Express-
SSMSE
No SP and SP1
(32/64 bit)

SQL 2017 Standard, Enterprise No SP
(64 bit)

SQL 2017 Express -
SSMSE
No SP
(64 bit)

Batch Management Server

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

Batch Management Clients

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

Batch Management History Server

Y

Y*

Y

Y*

Y

 

Y*

Y*

Y

Batch Management Reporting Content

Y

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 Batch Management station type when the Batch Management software is used with System Platform (SP):

Additional Software Requirements

Batch Management Station Type

 

Server

Run-time Client

Development Client

History Server

Reporting Content

Redundant System

Application Server bootstrap and IDE

Yes*

-

Yes

-

-

Yes*

InTouch

-

Yes

-

-

-

-

*Application Server IDE is required only during Development for GRAccess, and not during Runtime. IDE is required for Tag Linker Editor for browsing the Galaxy by creating an Access Name. Application Server Bootstrap is required only for Batch Management Server and Redundant Server during Runtime.

Batch Management Firewall Exceptions List

Batch Management 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 Batch Management. 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 Batch Management. The following is a list of ports that must be added to the Windows Firewall exceptions list for Batch Management:

  • TCP port numbers for Batch Management: 8199, 9001 to 9012, 9015, and 9016.
  • UDP port numbers for Batch Management: 9013 and 9014.

Product Compatibility

Batch Management 2017 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 Update 2

Y

Y

2017 Update 1

Y

Y

2017

Y

Y

2014 R2 SP1

Y

Y

2014 R2 P01

Y

Y

2014 R2

Y

Y

Wonderware® ASB Framework

 

4.2.2

Y

Y

4.0.0.13000

Y

Y

4.1.0

Y

Y

Wonderware® InTouch® CE

10.1

N

N

Wonderware® Manufacturing Execution System (MES)

 

MES 2017

N/A

Y

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

N

4.0 SP1

N/A

N

Manufacturing Execution Module

1

N/A

N

Wonderware® QI Analyst™

8.0 SP4

N/A

Y

8.0 SP3

N/A

Y

8.0 SP3

N/A

Y

Wonderware® Intelligence

 

2017

Y

Y

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 R2 U1

N/A

Y

2017

N/A

Y

2014 R2 SP2 P01

N/A

Y

2014 R2 SP2

N/A

Y

2014 R2

N/A

Y

2014

N/A

Y

Wonderware® Production Execution Module (PEM)

2.1 SP1

N/A

Y

Foxboro® Control Software

 

7.1

N

N

7.0

N

N

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.4

Y

Y

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)

N

N

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 Batch Management software is supported in newer environments than a compatible product. The Batch Management 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 Batch Management and Foxboro Control Software, contact AVEVA Software Global Customer Support (GCS).

Licensing

Batch Management enforces licensing through the Schneider Electric Licensing system.

Licensing Reservation

  • Device Reservation: Batch Management Connection licenses cannot be reserved to devices as it is not possible to identify the client device name in a deterministic way.
  • User Reservation: The user name format used to reserve a Batch Management Connection in License Manager should match the user name format used to log on to Batch Management.

License Types

  • Server Licensing: This license is requested when a user starts the Batch Management Server.
  • Development Client Licensing: This license is requested when a user starts Batch Management Development Client.
  • Manufacturing Operations Client Connection (MOM Client) Licensing: This license is requested when a user starts a Batch Management Runtime Client.

For more information regarding the Licensing of Batch Management, see the Schneider Electric License Server Guide and Batch Management Installation Guide.

Installing Batch Management 2017

Special Notes

  • Before upgrading, please take note of the known issues in the Installation Issues section of this document.
  • Before installing Batch Management 2017 on a node with WSP 2014 R2 SP1, you must install WSP 2014 R2 SP1 GRAccess HotFix CR L00140512.

    Otherwise, you might encounter the following issues:

    • Error while Galaxy browsing from TagLinker
    • ArchestrA security will not work if enabled in Security editor.

    Note: Prior to upgrading, confirm that your Hist Queue and Error Queue are empty. Because of changes to the Batch Management History database, any data left in the Hist Queue or Error Queue will not be accessible in the upgraded version. Also, ensure that all batches have ended and that all warm restart files have been deleted.

  • Starting with 11.5, Batch Management History Server and Reporting Content no longer integrate with Information Server. These features are now available through Start Menu shortcuts. For more information, see the Batch Management Installation Guide and Batch Management User Guide.
  • While installing Batch Management or upgrading to the latest version, you can select and install the Licensing components. For more information about Licensing, see the Batch Management Installation Guide.
  • Batch Management features can be used for demo purposes in a Standalone Workgroup machine. However, the Batch Management features are not supported in a Distributed Workgroup environment due to Security reasons. For information on configuring the firewall settings in a Distributed Workgroup environment, contact Technical Support.

Installing or Upgrading

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

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

  • Wonderware InBatch 9.0
  • Wonderware InBatch 9.0 with SP1, and SP2
  • Wonderware InBatch 9.5
  • Wonderware InBatch 9.5 with SP1
  • Wonderware InBatch 9.6
  • Wonderware InBatch 2012 R2 (10.0)
  • Wonderware InBatch 2014 (10.1)
  • Wonderware InBatch 2014 R2 (10.2)
  • Wonderware InBatch 2014 R2 SP1 (11)
  • Wonderware InBatch 2014 R3 (11.5)
  • Wonderware InBatch 2014 R3 SP1 (11.5.1)

The process will upgrade all components as required.

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

  • Once the upgrade process is completed, you have to run the CVTMaster.exe utility to upgrade the application databases.
  • When you upgrade from previous versions (11.0 or earlier) of InBatch to Batch Management 2017, all the InBatch links from Information Server database are removed. You can verify the NavNode, NavRole, NavPanelNode tables from where all InBatch related rows must be removed. The .rdl template files are also removed from the ArchestrA\InBatch Reports folder and are now deployed in the InBatch Reports folder in the Reporting service URL.
  • Users can access the reports from the standard Reporting Services URL or the shortcut menu available in the InBatch folder. The reports will not be available from the Information Server. Also, the History Database Administration and Reports Administration web pages now have their own shortcut menu and is available in the InBatch folder.
  • If you have created custom reports (InBatch versions prior to 11.5) and want to convert them to the latest version of Batch Management, no longer rely on Information Server. For more information, see the Batch Management Custom Report Update Guide (BatchManagementCustRepGuide.pdf).
  • The upgrade supports Batch Management with I/A components and without I/A components.
  • To upgrade from a version older than Wonderware InBatch 9.0, first uninstall the previous version and then install Batch Management 2017.
  • When you upgrade InBatch from an earlier version to Batch Management 2017, the .CSV message files available at "C:\Program Files\Wonderware\InBatch\Messages" are backed up and are placed at the same location: "C:\Program Files\Wonderware\InBatch\Messages".

    Any new .CSV files are also added to the following folder: "C:\Program Files\Wonderware\InBatch\Messages\English".

  • You need to manually update or copy the resources files to be able to get the correct messages after upgrade from InBatch 11.0. If you have not manually updated the resource files in InBatch v11.0, then you should copy all the resource files. For more information on the list of updated messages in the resource files, refer to the Resource File section.

    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.

Resolved Issues

This section describes important resolved issues.

L00142598

Material ID: When all numbers are used for Material ID, Batch Display appends ",00" at the end.

L00142082

InBatch GUI .Net Controls do not consider the decimal delimiter set in the Region settings.

L00144030

InBatchResourceAPI provides misleading warnings such as "File doesn't exist... filename.csv", when the permission is denied.

L00144037

RedMngr reports “File: rt.c Line: 167” error while starting the InBatch Server 'Environment Display' in a redundant environment.

L00144285

InBatch Readme contains the information that Wonderware Application Server bootstrap and IDE are required for Batch Server. It should be limited to Development time only.

L00144286

While opening Galaxy Browser, TagLinker crashes; instead of showing the appropriate error. This issue is observed when IDE is removed from the system.

L00144414

Control: Wonderware BatchBotton Class Error: Access is Denied when InBatch ActiveX controls are used in Vijeo Citect.

L00144509

The 'UpdatePhaseParameter' InBatch Stateless API does not raise exception when an invalid value is passed for the enumeration type.

L00145707

[Doc update Note in Install Guide] While configuring the Batch Reports, the "text/html instead of text/xml" error message appears if the report directory already exists. The issue can be fixed by deleting the existing report folder.

L00145990

While the Phase is executed, if the operator entered their credentials to Acknowledge and exit the phase, the Report does not show acknowledgement. This issue is observed when a new operator enters their credentials for the first time in InBatch.

L00146114

The default scripts in the 'InBatchPhase' symbol, which is available under ArchestrA Graphics templates, generates warnings when used with Manual or Data Phases.

This issue is not observed when the symbol is used with Automatic Phases. Therefore, a separate symbol has been created for Manual and Data Phases.

L00146302

InBatch Failed: InBatch Server 'Batch Manager' stopped unexpectedly.

L00146243

InBatch stores the batch events in a wrong order in the History BatchDetail table.

L00146388

InBatch 11.5.1 MaterialSrv.exe throws exception when it is used several times.

L00146712

Fix the SMC logger messages on InBatch Redundancy to include Server Name in the message
"Cannot contact Redundancy Manager on "(null)". Is Batch Server on "(null)" started?".

L00146732

IDE crashes while embedding a graphic into the Batch Unit object.

L00146834

The Batch Cmd 113 does not indicate if the unit failed to allocate or if the unit was already allocated.

L00147000

In the InBatch user guide on page 173 section, remove the note from the 'Performing Runtime Export' topic, since it is still working and supported.

L00147059

After editing recipes, some recipes are corrupted (parameters mismatch, recipes cannot be opened).

L00147125

InBatch configured for ArchestrA Security (OS Group Based). Using InBatch Middleware API calls to execute the secured enabled functions returns invalid UserID/Password.

L00147084

In a redundant environment, Train Editor/Model Editor does not exit gracefully after making changes.

L00147708

While configuring InBatch security with OS users or groups, a popup message states to use \\ between the domain name and user.

L00147497

InBatch security DoneBy/CheckBy e-signatures are missing periodically from BatchHistory.

L00147647

Intermittent Material Automation Server failures are observed when using from multiple sessions (RDS View clients).

L00147806

Warning messages are displayed randomly in the SMC stating that the recipe attempted to execute two instances of the phase.

L00148227

The Recipe Editor crashes while saving a recipe, which contains ingredients that no longer exist.

L00148859

InBatch Batch Alarm Report does not execute successfully, which indicates that it does not respond, memory usage goes up, SQL-DB Log files grows and consumes all the space left in the system.

L00148981

Batch Display and Batch Scheduler display no batches, when Active Transition has assignment operator (:=) that is still executing or failed to execute.

L00149154

The decimal of value in ProcessVar is not handled correctly for value between -1 and 1.

- If the values are greater than 1 or less than -1, trailing 0s are added to achieve 8 significant figures.

- However, in the case of a data values of between -1 and +1 (including 0.*), trailing 0s are added to achieve 9 significant figures.

L00149684

Batch Object Utility failed to update all objects for a very large galaxy.

L00149765

In the AuthSessionId feature, the timestamp of CheckBy in AuditEvent is newer than BatchDetail activity.

L00149753

The Import InBatch model changed default ArchestrA objects (UDO) name and created odd objects.

L00149942

Stream corruption error and Batch Manager crash observed when transition/loop expressions include combinations of functions, tags assignments, and operands.

L00150764

The Security System chapter in the Batch Management User Guide is updated with better screenshots and examples.

L00150625

Batch API should return the correct runtime status.

L00151016

Recipe Editor does not print SFC Procedure in postscript on Batch Development Client.

L00151056

Duplicate AuthSessionId found in the AuditEvent table.

L00148274

BatchDetail events happen with no BatchIdLog created.

Known Issues

This section describes important known issues.

  • Installation Issues
  • Other Issues

Installation Issues

616969

Configuration of the History Server feature fails, when you upgrade InBatch History Server to InBatch version 11.5.1 from versions prior to InBatch 11.0.

 

Before proceeding with the upgrade, ensure that you delete all SQL Jobs related to Archive\Purge\Restore. Prior to InBatch 11.0 version, any SQL Agent jobs (Archive\Purge\Restore jobs) created in InBatch History Server may 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].

    If a registry value named 'SessionViewSize' exists, ensure that 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

1055512

Batch Management web client Icons and images are distorted in Mozilla Firefox browsers.

Workaround: Do the following settings in the Firefox browser:

  1. Open the Firefox browser.
  2. Navigate to Options > General.
  3. Under the Performance option, clear the Use recommended performance settings” and Use hardware acceleration when available check boxes.
  4. Restart the browser.

     

455938

When you access the InBatch Reports using Internet Explorer 11, the user interface fields of the Reports header are not displayed correctly.

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

Ensure that you adjust the 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). The width of other GUI Control lists 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 the Chrome browser.

 

Workaround: 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. Navigate to C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\Styles directory.
  6. Make a copy of 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.

    All the existing reports on this instance of Reporting Services are displayed on all browsers including Chrome and Safari.

     

    Note: The reportserver.config may be overwritten with updates to reporting services. In such cases, add the <HTMLViewerStyleSheet > SafariChromeFix </HTMLViewerStyleSheet> tag into the config file every time.

     

L00077400

Editors are not opening on the Wonderware InBatch development client.

 

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 then 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 the 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

 

 

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 a report named "Custom Batch Detail" is populated in the list.

 

  1. Update the RptServicesConfig.xml file in the following location:

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

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

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

  4. 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. However, the Watchdog tag still functions 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. The tag can be of any data type.
  • Disable pinging using the IBCli Disable Ping option.

L00125348

If you use the Import Utility in the preview mode, warning messages are not shown. This is observed when the utility imports a Wonderware InBatch ModelDB, in which any of the following have duplicate names (case sensitive): processes, transfers, segments, units, connections, or phases. However, warning messages are shown when you perform an actual import.

L00128201

When you run the cvtmaster for a second time, conversion fails.

 

Workaround:

  1. Create a new folder and name it (E.g. Test). Ensure that the folder name is not Config_A.
  2. Copy the contents of the Config_A folder to the new folder.
  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 the SMC logger after you enable the Enhanced security mode using "aaConfigSQL" tool.

 

Workaround: Ensure that the ServiceDB user (configured to run the InBatch ReportQueueReader service) has access to printers and has the privilege to print.

1010526

 

Compatibility issues with Vijeo Citect 2016

 

  • In the Citect Design window, the application crashes when the 'InBatchGUIConfig' control is inserted prior to inserting the 'InBatchSFC' control on the same page.

    Workaround: The 'InBatchSFC' control must be inserted prior to the 'InBatchGUIConfig' control on the page/symbol.

  • Font size cannot be changed on any of the Batch ActiveX controls in Vijeo Citect.
  • An error message is displayed on the Control Area when you hold the InBatch Field ActiveX controls and drag them to a different location on page, during design time.
  • Tooltip does not get displayed on the Batch ActiveX controls at runtime.

1102209

 

The 'History Admin' and the 'Report Web' pages display the following error:

Unable to contact Batch Host to determine if security is enabled. Check Batch Host and restart browser.

 

This error is observed when you:

  1. Install and configure Batch Management Server on Node #1.
  2. Install and configure Batch Management History and Reports on Node #2.
  3. Launch Environment Display on Node #1.
  4. Launch History Admin page or Report Web page on Node #2.

 

Workaround:

  1. Launch Internet Explorer on Node #2.
  2. Under Tools, select Internet Options.

    The Internet Options dialog box appears.

  3. Click the Security tab and then select Trusted sites.
  4. Under Security level for this zone, click Custom level.

    The Security Settings – Local Intranet Zone dialog box appears.

  5. Under User Authentication > Logon, ensure that the Automatic logon with current user name and password option is selected.

     

1105212

Under the Usage Details tab in the Schneider Electric License Manager web page, the Device Name is displayed as:

  • “<<HOSTNAME>>.1” for the consumed Server license.
  • “<<HOSTNAME>>.2" for the Development/Runtime client license.

     

    Workaround:

    In the Schneider Electric License Manager web page, click Sync to synchronize the license server.

     

1105211

License refresh failed, and a valid client license could not be acquired from the license server. A warning message is logged in the SMC logger.

 

Workaround:

Apply the License Server Hot Fix CR L00150512.

 

Known Issues - Documentation

  • Newer operating systems no longer include the WinHlp32.exe Help viewer component, which is required for viewing .hlp files. The Batch Management software includes the following .hlp files:
    • BatchView.hlp
    • IALink.hlp
    • TagView.hlp

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

  • The Help for Batch Management web client is best viewed in Microsoft Edge or Mozilla Firefox browsers.

Batch Management Documentation

The Batch Management documentation set includes the following:

  • ReadMe (This document) - Provides information about software and hardware requirements, known issues, licensing, and documentation updates.
  • Batch Management Installation Guide - Provides information about installation and upgrading from the previous versions.
  • Batch Management Getting Started Guide - Describes the basic components of the Batch Management software and provides a tutorial to help you get started using the product.
  • Batch Management Demo Guide - Describes a demo application that shows you how to use some of the new features in the Batch Management release.
  • Batch Management User's Guide - Describes the components of the Batch Management software and how to use them to create applications.
  • Batch Management Stateless API Online Reference - Provides information about the stateless API supported by the Batch Server.
  • Batch Management COM Technical Reference Guide - Describes using the Batch Management COM technology and provides practical examples of its use.
  • Batch Management Application Object Editor Help - Provides information about the InBatchUnit, InBatchConnection, InBatchPhase, and InBatchSegment objects.
  • Batch Management Custom Report Guide - Provides information about how to convert old (pre 11.5) custom reports to work without Information Server and to have UTC support in Batch Management.
  • Batch Management Help - Describes using the Batch Management Web Client to view batch details.

The Batch Management product library consists of a set of Portable Document Files (PDF) located in the UserDocs folder of the Batch Management installation CD. Install the Adobe Reader on your computer to view the Batch Management 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 Batch Management installation instructions are located in the root folder of the Batch Management installation CD, as a .chm file. You can view these instructions by clicking the Help when you start the Batch Management installation procedure.

Resource File

The following messages are modified in the Batch Management 2017 release:

Resource Name

Message

New/
Modified

Notes

Adminweb.csv

 

HtmlTitle

Batch Management History Server Administration.

Modified

old value: InBatch History Server Administration

HtmlHANavHeader

Batch Management History Administration

Modified

old value: InBatch History Administration

HtmlIBHisServerAdminError

Batch Management History Server Administration Error

Modified

old value: InBatch History Server Administration Error

HtmlCannotDisplayIBHisSerAdminPage

The Batch Management History Server Administration web page cannot be displayed.

Modified

old value: The InBatch History Server Administration web page cannot be displayed.

HtmlIBHisSerAdminErrMsg

Batch Management History Server Administration - Error Message

Modified

old value: InBatch History Server Administration - Error Message

HtmlIBHisSerAdminLogin

Batch Management History Server Administration Login

Modified

old value: InBatch History Server Administration Login

ErrUnableToContactHisServer

Unable to contact History Server. Please check Batch Management Environment Display started and History Server datasource details.

Modified

old value: Unable to contact History Server. Please check InBatch Environment Display started and History Server datasource details.

HtmlAppTitle

Batch Management History Database Administration

Modified

old value: Wonderware InBatch History Database Administration

HtmlSQLExpressEdition

SQL Express edition detected on Batch Management History Server. This operation is not supported as SQL Server Agent is unavailable/not installed.

Modified

old value: SQL Express edition detected on InBatch History Server. This operation is not supported as SQL Server Agent is unavailable/not installed.

BatchDisplay.csv

 

msg12

Enabled

New

 

msg13

Disabled

New

 

lblAutoStart

Auto Start:

New

 

BatchMngr.csv

 

msg313

Cannot find phase!

New

 

msg314

Cannot find parameter!

New

 

msg315

Unit is not available!

New

 

msg316

Batch has invalid status!

New

 

msg317

Instance is not valid!

New

 

msg318

Unit is not valid!

New

 

msg319

Unit is not valid for instance!

New

 

msg400

The batch is not in running state!

New

 

msg401

The batch is not in held state!

New

 

msg402

The phase is not in ready state!

New

 

msg403

The phase is not in running state!

New

 

msg404

The phase is not in held state!

New

 

msg405

The phase cannot be aborted in its current state!

New

 

msg406

The view document operation cannot be performed for the phase in its current state!

New

 

msg407

The acknowledge document operation cannot be performed for the phase in its current state!

New

 

msg408

The acknowledge phase operation cannot be performed for the phase in its current state!

New

 

msg409

The comment cannot be null or empty!

New

 

msg410

The edit comment operation cannot be performed for the phase in its current state!

New

 

msg411

The acknowledge entry operation cannot be performed for the phase in its current state!

New

 

msg412

The acknowledge exit operation cannot be performed for the phase in its current state!

New

 

msg413

The get batch messages operation cannot be performed for the batch in its current state!

New

 

msg414

The batch cannot be initialized as Batch Auto Start is enabled and Batch Auto Start Confirmation Message system parameter is enabled!

New

 

msg415

Batch Auto Start is already enabled!

New

 

msg416

Batch Auto Start is already disabled!

New

 

BatchSched.csv

 

menu&BatchAutoStart

&Batch Auto Start

New

 

rc32815

Starts all initialized batches.\nBatch Auto Start

New

 

msg53

The Batch Auto Start option will automatically start all initialized batches. This will affect existing batches and any new batches added in the future. Are you sure you want to enable the Batch Auto Start option?

New

 

msg54

Disabling Auto Start option will disable the auto start of newly initialized batches. Are you sure you want to disable Batch Auto Start?

New

 

msg55

The Batch Auto Start option is enabled. The selected batch will be initialized and then automatically started. Are you sure you want to continue?

New

 

msg56

The Batch Auto Start option is enabled. All the batches will be initialized and then automatically started. Are you sure you want to continue?

New

 

msg57

Cannot activate Batch Auto Start as the security is enabled for Start Batch.

New

 

msg58

The Batch Auto Start option will be deactivated as the security is enabled for Start Batch.

New

 

BatchView.csv

 

lblAutoStart

Auto Start

New

 

dkerrors.csv

 

 

msg55

The number of units defined in the model exceeds the predefined number of units available in the license!

Modified

old value: Cannot exceed pre-defined number of units!

ImportExportUtil.csv

 

menuAboutIBImpExp

&About Batch Management Model Import Export Utility...

Modified

old value: &About InBatch Model Import Export Utility...

titleLoginDialog

Batch Management Credentials

Modified

old value: InBatch Credentials

titleAboutIBImportExportUtil

About Batch Management Model Import Export Utility

Modified

old value: About InBatch Model Import Export Utility

titleErrDialogIBImportExportUtility

Batch Management Model Import / Export Utility Error

Modified

old value: InBatch Model Import / Export Utility Error

RecipeCompare.csv

 

AboutMenuTitle

About Batch Management Recipe Compare...

Modified

old value: About InBatch Recipe Compare...

HtmlReportTitle

Batch Management Recipe Comparison Report

Modified

old value: InBatch Recipe Comparison Report

ReportWeb.csv

 

HtmlTitle

Batch Management Reports Administration

Modified

old value: InBatch Reports Administration

HtmlInBatchReportsTitle

Batch Management Reports

Modified

old value: InBatch Reports

HtmlErrMsgServerFail

Unable to contact History Server. Please check Batch Management Environment Display started and History Server datasource details.

Modified

old value: Unable to contact History Server. Please check InBatch Environment Display started and History Server datasource details.

HtmlReportWebLogin

Batch Management Reports Administration Login

Modified

old value: InBatch Reports Administration Login

HtmlAppTitle

Batch Management Reports Administration

Modified

old value: Wonderware InBatch Reports Administration

HtmlInBatchReportsAppTitle

Batch Management Reports

Modified

old value: Wonderware InBatch Reports

HtmlSQLExpressEdition

SQL Express edition detected on Batch Management Reporting Server. This operation is not supported as SQL Server Agent is unavailable/not installed.

Modified

old value: SQL Express edition detected on InBatch Reporting Server. This operation is not supported as SQL Server Agent is unavailable/not installed.

HtmlSSRSUnavailable

SQL Express edition detected on Batch Management Reporting Server. This operation is not supported as reporting service is unavailable.

Modified

old value: SQL Express edition detected on InBatch Reporting Server. This operation is not supported as reporting service is unavailable.

SecEdit.csv

 

msg98

Switching security modes only affects the Security Editor until you restart the Security Manager. It leaves all existing users intact. However, users entered for one security mode will not work with another security mode.\n\nA default user may be created for the mode you are switching into, if it doesn't already exist. For standard mode, a user with the ID of 'system' is created. For OS mode, a user with the ID of the current workstations local administrator will be created, as well as the user configured for service admin access. For ArchestrA mode, two users with the IDs of 'DefaultUser' and 'Administrator' will be created. You will need to know the passwords.

Modified

old value: Switching security modes only affects the Security Editor until you restart the Security Manager. It leaves all existing users intact. However, users entered for one security mode will not work with another security mode.\n\nA default user may be created for the mode you are switching into, if it doesn't already exist. For standard mode, a user with the ID of 'system' is created. For OS mode, a user with the ID of the current workstations local administrator will be created, as well as the user ID of the current Wonderware Network Account. For ArchestrA mode, two users with the IDs of 'DefaultUser' and 'Administrator' will be created. You will need to know the passwords.

msg99

When using OS security, the User ID should be of the format domain\userid. The domain can be a Domain or a Workstation.

Modified

old value: When using OS security, the User ID should be of the format domain\\userid. The domain can be a Domain or a Workstation.

msg158

Batch Management security system supports user name length up to %%d characters only. Please select different user.

Modified

old value: InBatch security system supports user name length up to %%d characters only. Please select different user.

msg160

User/Group [%%s] already added in Batch Management [%%s] security mode, delete the user and try again.

Modified

old value: User/Group [%%s] already added in InBatch [%%s] security mode, delete the user and try again.

TagLinker.csv

 

msg1

Batch Management Tag Linker

Modified

old value: InBatch Tag Linker

msg20

<Batch Management Memory Tag>

Modified

old value: <InBatch Memory Tag>

msg152

** GENERATED FROM Batch Management TAGLINKER **\nDO NOT EDIT THIS DATABASE BY HAND!

Modified

old value: ** GENERATED FROM INBATCH TAGLINKER **\nDO NOT EDIT THIS DATABASE BY HAND!

msg300

\n\n*** Batch Management Access Definitions ***\n\n

Modified

old value: \n\n*** InBatch Access Definitions ***\n\n

msg320

\n\n*** Batch Management Export Definitions ***\n\n

Modified

old value: \n\n*** InBatch Export Definitions ***\n\n

msg344

\n\n*** Batch Management %%s ***\n\n

Modified

old value: \n\n*** InBatch %%s ***\n\n

btnInBatchMemoryTag

Batch Management Memory Tag

Modified

old value: InBatch Memory Tag

Copyright © 2018 AVEVA Group plc and its subsidiaries. All rights reserved.   |   Contact Us