Wonderware InBatch 2014 R3 (11.5)

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

Wonderware InBatch 2014 R3 (v.11.5) Readme

Last revision:04/27/2016

About This Readme

This document contains important information about Wonderware® InBatch 2014 R3 (v.11.5). 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 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 (v.11.5) offers the following new features and enhancements:

  • InBatch Reports are now independent of Wonderware Information Server.
  • InBatch Reports are made available through Microsoft SQL Server Reporting Services (SSRS).
  • Provides support for SQL Named Instances on supported SQL versions.
  • Provides support for SQL Express Edition on supported SQL versions (For application development only).
  • Provides support for Phase tagname delimiter that allows the Alarm report to work with A2ALMDB and WWALMDB.
  • New and enhanced look and feel for the InBatch Reporting content.
  • Fixes to several issues reported by customers.

< top of document >

Minimum System Requirements

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

Hardware Requirements

The following hardware is recommended to support Wonderware InBatch 2014 R3 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.


  Client
Windows OS
Server
Windows OS
.NET
Framework
Virtualization
7 SP1
Professional,
Enterprise,
Ultimate
(32/64-bit)
8
Professional,
Enterprise
(32/64-bit)
8.1
Professional,
Enterprise
(32/64-bit)
10 Professional and Enterprise
Standard,
Enterprise
(64-bit)
2008 R2 SP1
Standard,
Enterprise
(64-bit)
2012
Standard,
Data Center
(64-bit)
2012 R2
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 N N N Y Y Y C Y Y Y Y
Wonderware InBatch Clients Y Y Y Y Y Y Y C Y Y Y Y
Wonderware InBatch History Server N N N N Y Y Y C Y Y Y Y
Wonderware InBatch Reporting Content Y Y Y Y Y Y Y C Y Y Y Y

 

Supported Y
Not Supported N
Coexist C

 

Notes:

  • For software requirements for the "Wonderware InBatch Components for ArchestrA IDE/IEE" feature, see the software requirements for Wonderware Application Server.
  • For software requirements for the "Wonderware InBatch Reporting Content" feature, see the software requirements for Microsoft SQL Server.
  • If a supported version of the Microsoft .NET Framework is not installed, the Wonderware InBatch installation automatically installs it.

Browser Requirements

Browser Version
Internet Explorer Version 10 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:

  2008 R2 SP1 (32/64 bit) 2008 R2 SP2 Standard, Enterprise (32/64 bit) 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)
Wonderware InBatch Server

N/A 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 N/A
Wonderware InBatch History Server Y Y Y Y* Y Y Y Y*
Wonderware InBatch 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 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

The following table lists the application names and ports that must be added in the Windows Firewall exceptions list for Wonderware InBatch:

Application Name
Port Number
BatchMngr
9008
EnvMngr
9002
InfoMngr
9012
HistQMngrvista
9015
HisQReader
9016
Wonderware InBatch Middleware Access
8199
OLE Recipe Automation
5001
OLE Recipe Automation
5002
OLE Recipe Automation
5003
OLE Recipe Automation
5004
OLE Recipe Automation
5005
RedMngr
9006
RedMngrX
9013
RedMngrX2
9014
SecMngr
9004
UnilinkMngr
9007

< top of document >

Product Compatibility

Wonderware InBatch 2014 R3 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*
2014 R2 SP1 Y Y
2014 R2 P01 Y Y
2014 R2 Y Y
ArchestrA® System Platform
2012 R2 N N
2012 N N
Wonderware® ASB Framework
4.0.0.13000 Y Y
Wonderware® InTouch® CE 10.1 N N
Wonderware® Manufacturing Execution System
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® Manufacturing Execution Module 1.0 N/A N
Wonderware® QI Analyst™
8.0 SP3 N/A Y
8.0 SP2 N/A Y
8.0 SP1 P01 N/A N
Wonderware® Intelligence™
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™
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® Evo 2014 Y Y
Foxboro® Control System
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.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 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 supports Archestra.lic license files. Archestra.lic format licenses work with Wonderware InBatch 2012 R2 and later.

< top of document >


Installing Wonderware InBatch 2014 R3

Special Notes

  • Before upgrading, please take note of the known issues in the Installation Issues section of this document.
  • Before installing InBatch 2014 R3 (v 11.5) 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 Wonderware InBatch 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, InBatch History Server and Reporting Content no longer integrate with Wonderware Information Server. These features are now available through Start Menu shortcuts. See the install and user guides for more details.
  • Follow this installation order if you are installing System Platform 2012 or later on the Batch Server node with a custom Wonderware Application Server installation location:
    1. Install Application Server
    2. Install Wonderware InBatch
    If you do not install in this order, the BatchEvent feature may not work properly.

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:

  • 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)

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 of InBatch to InBatch 2014 R3 , all the InBatch links from Wonderware 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 Wonderware 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 and want to convert them to InBatch v11.5, no longer rely on Wonderware Information Server. For more information, see the Wonderware InBatch Custom Report Update Guide (InBatchCustRepGuide.pdf).

  • The upgrade supports Wonderware InBatch 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 Wonderware InBatch 2014 R3.

  • When you upgrade InBatch from an earlier version to InBatch v11.5, 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.

< top of document >

Resolved Issues

This section describes important resolved issues.

L00137252: Random BatchMngr issues are encountered and the BatchMngr is crashing. To prevent BatchMngr from crashing, the system now catches the exception and display a message in the SMC logger.
L00137542: (HotFix L00140389): When you migrated from InBatch Premier 8.1 to InBatch 10.2 (2014 R2), expressions used for Group defined in Process Logger Group editor are not converted correctly. The expressions still have dash(-) in place of dot(.). The issue is resolved.
L00137575: IADriver needs extended logging added to so that customer can see the Tag read writes in the SMC like IBCLI and IBMX for debugging when the phase control bit get out of sync with InBatch. To view the Tag updates trace messages, click to select the Trace log flag option available in SMC Logger for IADriver by navigating Action -> LogFlags -> IADriver -> Trace .
L00137581: Error encountered while configuring the InBatch History Server.
L00138508: When user uses Czech Republic region and language settings while working with the the Archive, Purge and Restore jobs in Windows server 2012R2. Date validation logic fails and an error message is displayed. The default date display space after the date separator. This issue is resolved.
L00138620: InBatch GUI .Net List Controls crashes if keyboard arrows is used to move up/down in the list.
L00138628: Issue related to Tooltips in the InBatch GUI .Net Controls is resolved.
L00138854: Sync Validate and Phase sync button in Recipe Editor over writing values and displays UOM error. The issue is resolved.
L00138966: Opening multiple Batch views from Batch Scheduler crashes the Batch View after you reach a limit.
L00138979: Working with the Recipe Compare feature when using the Recipe Compare API throws errors when executed.
L00139154: Recipe with long names are not displayed correctly in the Recipe Editor.
L00139745, L00138604: Editing parameters values in Phase Parameters tab of Recipe Editor sometime affects the non-edited Phase Parameters after saving the changes. This issue is resolved.
L00139858: When the batch is running and if the parameter target value is manually edited, then this change will be logged in the BatchHistory database even if the old target and the new target values are the same.
L00140007: Valid administrative account on domain fails in Configurator while working access the InBatch Reporting Content - Service DB Access Account. This issue is resolved now.
L00140021: (HotFix L00140222): BatchNativeSec is not working if UAC is enabled in Registry.
L00140139: (HotFix L00139985): UnilinkMngr crashes when you start/stop quickly and also not all the data response/update does not come into unilinkMngr (from IBMX, IBCli, etc.). This issue is resloved now.
L00140153: InBatch User ID Timeout option for retaining ID in security prompt does not work in Operating System and ArchestrA security modes.
L00140379: Issue is resolved for Recipe Editor crash when trying to save a recipe with the following error: BatchNativeSec "Native Get User Name failed. The RPC server is unavailable. [1722].
L00140386: InBatch StatelessAPI, InBatchCommon.BatchRuntimeStatusTypes. AllRuntimeServicesExceptInBatchTag Enumeration is working without any issues. A new sample example is added in the Stateless API help file.
L00140387: RecipeEditor crashes while launching it from Environment Display.
L00140674: Working with the OcxBatch.ScheduleSchedGetItem & BatchSchedGetItem and AllocQueueGetItem methods caused errors when processing the data. This issue is resolved now.
L00140690: Recipe validate not working when the parameter value is updated to 0.

< top of document >

Known Issues

This section describes important known issues.

Installation Issues

616969: Configuration of History feature fails when you upgrade InBatch History Server to InBatch version 11.5 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:

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

< top of document >

Wonderware InBatch Documentation

The Wonderware InBatch documentation set includes the following:

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

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 messages are modified in the Wonderware InBatch v11.5:

Resource Name Message New/Modified Notes
AdminWeb.csv
JsBadUserIDPwdUnknown user name and/or password.Modifiedold value: Unknown userid and/or password.","Unknown userid and/or password.
HtmlEnterUserIDPasswordPlease enter user name and passwordModifiedold value: Enter User ID & Password","Enter User ID & Password
HtmlUserIDUser nameModifiedold value: User ID
ErrLoginBadUIDPwdLogin Error - Unknown user name and/or password.Modifiedold value: Login Error - Unknown userid and/or password.","Login Error - Unknown userid and/or password.
HtmlAppTitleWonderware InBatch History Database AdministrationNew
HtmlSQLExpressEditionSQL Express edition detected on InBatch History Server. This operation is not supported as SQL Server Agent is unavailable/not installed.New
ErrSQLDoesNotExistIncorrectPwdSpecified SQL server UserID does not exists or incorrect Password.New
ErrFailedToConnectHSFailed connecting to History Server.New
ReportWeb.csv
HtmlTitleInBatch Reports AdministrationModifiedold value: InBatch Reporting
HtmlInBatchReportsTitleInBatch ReportsNew
HtmlViewReportsView ReportsNew
HtmlExecuteReportsExecute ReportsNew
ErrLoginBadUIDPwdLogin Error - Unknown user name and/or password.Modifiedold value: Login Error - Unknown userid and/or password.
HtmlReportWebLoginInBatch Reports Administration LoginModifiedold value: InBatch Reporting Login
HtmlEnterUserIDPasswordPlease enter user name and passwordModifiedold value: Enter User ID & Password
HtmlUserIDUser nameModifiedold value: User ID
JsBadUserIDPwdUnknown user name and/or password.Modifiedold value: Unknown userid and/or password.
HtmlAppTitleWonderware InBatch Reports AdministrationNew
HtmlInBatchReportsAppTitleWonderware InBatch ReportsNew
HtmlExportedReportsDetailsDetails of exported report:New
HtmlSQLExpressEditionSQL Express edition detected on InBatch Reporting Server. This operation is not supported as SQL Server Agent is unavailable/not installed.New
HtmlAboutAboutNew
HtmlVersionVersionNew
dkerrors.csv
msg16Redundancy Manager not registered in services file! Re-configure Batch Server feature to register the Redundancy Manager in services file.Modifiedold value: Redundancy Manager not registered in services file!
msg19Cannot connect to master Redundancy Manager! Check if runtime services are running on the Master node.Modifiedold value: Cannot connect to master Redundancy Manager!
msg48Redundancy configuration file is invalid! Delete the existing redcfg file present under Config_A folder and re-configure Batch Server feature to get a valid redcfg file.Modifiedold value: Redundancy configuration file is invalid!
dklib.csv
msg84Warning: Lost connection to master %%s! Check if runtime services are running on the Master node.Modifiedold value: Warning: Lost connection to master %%s!
msg87System backup is no longer valid! Check if runtime services are running correctly on the Master node.Modifiedold value: System backup is no longer valid!

< top of document >

Use of Material Design Lite

The product uses Google's Material Design Lite library for portions of the user interface: Copyright 2015 Google Inc

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.

You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

All code in any directories or sub-directories that end with *.html or *.css is licensed under the Creative Commons Attribution International 4.0 License, which full text can be found here: https://creativecommons.org/licenses/by/4.0/legalcode.

As an exception to this license, all html or css that is generated by the software at the direction of the user is copyright the user. The user has full ownership and control over such content, including whether and how they wish to license it.

< top of document >


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