Wonderware InBatch Version 9.0 with SP2

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

Wonderware InBatch Version 9.0 with SP2 Readme

Last revision: 04/08/2011

About This Release

This document contains important information about this Wonderware® InBatch™ 9.0 with SP2 release. Review this document for known issues and changes to the InBatch software and documentation included on this CD.

This Readme includes information about Wonderware InBatch version 9.0 with SP2, InBatch version 9.0 with SP1, and InBatch 9.0. The information is ordered based on when Wonderware InBatch versions were released.

Use the following links to the various sections of this Readme.

Wonderware InBatch 9.0 with SP2 Information

Wonderware InBatch 9.0 with SP1 Information

Wonderware InBatch 9.0 Information

< top of document >

New Features - Wonderware InBatch 9.0 with SP2

The following new features are available in Wonderware InBatch 9.0 with SP2:

  • Added HistoryHook Interface to enable users to integrate the InBatch History with external applications.
  • Updates to the InBatch Batch Hooks to retrieve segment data from the Process Model.
  • Updated Batch Display automatically selects a specified batch by accepting campaign, lot and batch command-line arguments.
  • Consolidates all hotfixes delivered after InBatch 9.0 with SP1.
  • Provides fixes to important issues reported from the field.
  • Consolidates fixes for security vulnerabilities reported in the Raima Lock Manager and Batch GUI controls (SecLF0000054 and SecLF0000051).

    < top of document >

    System Requirements - Wonderware InBatch 9.0 with SP2

    This section describes some of the hardware and software requirements to install Wonderware InBatch 9.0 with SP2.

    For complete details on the operating systems and supported Microsoft SQL Server versions, refer to the InBatch Installation Guide.

    If you are using a dongle device to enable the use of the software, contact Wonderware for the license and the driver.

    Recommended Hardware Requirements

    The following hardware is recommended to support Wonderware InBatch 9.0 with SP2:

    • Processor - 3.0 gigahertz (GHz) or faster processor
    • RAM - 2 gigabyte (GB) of memory
    • Hard disk - At least 4 GB of available disk space
    • Super VGA (1024 × 768) or higher-resolution video adapter and monitor
    • CD-ROM or DVD drive for installation
    • Keyboard
    • Mouse or compatible pointing device

    Software Requirements

    I/A Series, InFusion and Foxboro Control Software configurations are supported only on certain operating systems and platforms. For details, refer to the InBatch Installation Guide.

    We support InBatch run-time client and development client on Windows 7 Professional.

    Restrictions

    • InBatch 9.0 with SP1 and SP2 components are not supported on a single node running on Windows XP SP3. Windows XP SP3 32-bit does not support IIS 6.0, so the InBatch History Server feature cannot be installed.
    • Windows Vista does not support NetDDE. By design, an InBatch application does not serve data on Windows Vista through NetDDE, including InBatch itself.

    Product Compatibility

    • Wonderware Application Server 3.1 SP1, 3.1 SP2, 3.1 SP2 P01, and 3.1 SP3
    • Foxboro Control Software 3.0
    • I/A Series Software 8.4.3, 8.5, and 8.6
    • Wonderware InTouch® 10.1 SP1, 10.1 SP2, 10.1 SP2 P01, and SP3
    • Wonderware Historian 9.0 P02 and 10.0
    • Wonderware Information Server 3.1 and 4.0
    • DIObjects 4.1

    < top of document >

    Installation - Wonderware InBatch 9.0 with SP2

    For installation and upgrade instructions, see the InBatch Installation Guide.

    The upgrade from Wonderware InBatch 9.0 or InBatch 9.0 with SP1 to Wonderware InBatch 9.0 with SP2 is automatic. The upgrade supports Wonderware InBatch 9.0 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.

    For other upgrades, see the InBatch 9.0 Readme.

    After you upgrade Batch Reporting Content, a new report template called BatchJournal_EOB is available. The BatchJournal_EOB template is for an optimized Batch Journal report that is meant to be used with End of Batch report triggers. To schedule this report in Wonderware Information Server, you must manually redeploy the Batch Reports using the Wonderware Information Server Report Deployment tool.

    Note: If IBServ fails to start after being installed on the Windows XP SP3 operating system, you must restart the InBatch Server node.

    < top of document >

    Known Issues - Wonderware InBatch 9.0 with SP2

    Installation Issues

    L00111934:

    IALinker shortcut will be replaced with TagLinker when InBatchRuntimeClient with IA Components are uninstalled.

    To fix this, uninstall both Development and Run-time Clients and then re-install desired functionality.

    < top of document >

    Resolved Issues - Wonderware InBatch 9.0 with SP2

    The following critical issues are resolved in Wonderware InBatch 9.0 with SP2:

    L00111009:

    		 (HotFix 2211) SR 103119128: When upgrading from InBatch 8.1 SP1 to InBatch 9.0, the system could not run since InBatch Clients randomly locked up.

    L00110431:

    		 CR L00109980: The fix for the security vulnerability reported in InBatch 9.0 with SP1 is incorporated in InBatch 9.0 with SP2. See Invensys Operations Management Security Alert LFSEC00000051 rev 1.2: Wonderware InBatch and Foxboro I/A Series Batch Server lm_tcp buffer overflow (LFSEC00000051).
    L00092816: CR L00106622 SR 103115526: In order to get redundancy to work in a workgroup the local security settings on both servers we need to set to "Network access: Shares that can be accessed anonymously”.
    L00103853: HF CR L00100120 (HotFix 1828) SR 1036569: When entering the same CLB name but in a different case caused Batch Manager to crash on a restart due to the warm restart files.
    L00108392: HF CR L00108481 (HotFix 2205) SR 103117545: Randomly caused the target value in Batch Display to be blank. The target value was correct in Object Viewer.
    L00109318: HF CR L00109081 (HotFix 2263) SR 19911598: IBCli is required to handle Read Requests that return a quality of 0x20 (Initializing) better, instead of timing out.
    L00109351: HF CR L00109656 (HotFix 2310) SR 103119739: InTouch or InFusion View was crashing because the InBatch ActiveX controls did not handle connection failures to the Batch Server. This solves issues related to not being able to do a normal Stop All from the environmental display.
    L00110505: HF CR L00108698 (HotFix 2226) SR 103119666: There was a problem with Security Manger crashing randomly. A diagnostic fix was done in the application to sent the TCP packets by retrying 25 times in 300 ms.
    L00111005: HF CR L00110754: A security vulnerability as reported in “Stack Based buffer overflow in the “Label” method, in the InBatch Batch Field ActiveX Control (CR LFSEC00000054)” was addressed.
    L00111076: HF CR L00110876 (HotFix 2394) SR 103120783: When the batch server was rebooted or the InBatch manager stops unexpectedly, all InFusion View Clients freeze for several seconds and then crash.
    L00107951: HF CR L00107387 (HotFix 2151) SR 103119038: Problem when using the Load Unit Procedure option, the correct Process instance and Transfer instance do not get created even though the recipe validates.
    L00108205:

    HF CR L00102627 (HotFix 1875) SR 40210299: Recipe list is empty when recipe button invoked in batch scheduler on runtime client node. This issue occurs after a period of inactivity.
    L00109155: HF CR L00102390 (HotFix 1868) SR 37830938: The InTouch clients could freeze due to the fact that the InBatch Scheduler ActiveX control was getting locked because the server side socket was blocked due to the fact that the client disconnected from server.
    L00109663: HF CR L00108747 (HotFix 2231) SR 19911590: If you have a recipe with only two views setup in Unit procedure and Phase View (no Operation view) then you cannot add any phases now and you will get an error.

    < top of document >

Wonderware InBatch Version 9.0 with SP1 Readme

New Features - Wonderware InBatch 9.0 with SP1

The following new features are available in Wonderware InBatch 9.0 with SP1:

  • InBatch now supports newer versions of Microsoft Windows, Microsoft SQL Server, and the Microsoft .NET Framework.
  • The InBatch installation program will run with the User Account Control (UAC) either enabled or disabled.
  • The InBatch installation program can optionally install I/A components on a computer where I/A Series is installed.
  • InBatch applications will run with the User Account Control either enabled or disabled on Windows Vista and Windows 2008 operating systems.
  • InBatch provides a set of tags to monitor the failover status of I/O Server connections.
  • Operating system based security is supported on InBatch with I/A components.

    < top of document >

    InBatch Demo - Wonderware InBatch 9.0 with SP1

    An InBatch Demo application is provided in the InBatch CD-ROM. It consists of the InBatch configuration files with the Model and Recipe databases and an InTouch Application to interact with batch processing.

    • The InBatch configuration files are located in the following folder on the InBatch CD-ROM: D:\InBatch\cfg\PremierDemo, where D:\ is the drive letter of your CD ROM drive.
    • The InTouch application is located in the following folder on the InBatch CD-ROM: D:\InBatch\InBatchDemoApp, where D:\ is the drive letter of your CD ROM drive.  

    Using the Demo

    The following steps explain how to use the configuration files for the InBatch demo:

    1. Replace the files in the C:\Program Files\Wonderware\InBatch\cfg\Config_A folder with the files in the C:\Program Files\Wonderware\InBatch\cfg\dflt_cfg folder.
    2. Copy the demo configuration files from the C:\Program Files\Wonderware\InBatch\cfg\PremierDemo folder into the C:\Program Files\Wonderware\InBatch\cfg\Config_A folder.
    3. From the Environment Display dialog box, start the Runtime Applications and use the Batch Scheduler and Batch Display to schedule and run batches.
    Note: For a 64-bit operating system, replace Program Files in the path with Program Files(x86).

    Using the InTouch Application

    To use the InTouch demo application, you must follow these steps:

    1. Install RecipeManager from the InTouch CD-ROM.
    2. Copy the files in the WWTSup71.zip file into the InTouch directory.
    3. From the InTouch Application Manager, locate and start the InBatch Demo using WindowViewer.
    4. Use the InTouch application to interact with the InBatch system by scheduling and running batches.

    < top of document >

    System Requirements - Wonderware InBatch 9.0 with SP1

    This section describes some of the hardware and software requirements to install Wonderware InBatch 9.0 with SP1.

    For complete details on the operating systems and Microsoft SQL Server versions supported, refer to the InBatch Installation Guide.

    If you are using a dongle device to enable the use of the software, contact Wonderware for the license and the driver.

    Recommended Hardware Requirements

    The following hardware is recommended to support Wonderware InBatch 9.0 with SP1:

    • Computer with 3.0 gigahertz (GHz) or faster processor
    • 2 gigabyte (GB) of memory
    • At least 4 GB of available disk space
    • Super VGA (1024 × 768) or higher-resolution video adapter and monitor
    • CD-ROM or DVD drive for installation
    • Keyboard
    • Mouse or compatible pointing device

    Software Requirements

    I/A Series and InFusion configurations are supported only on certain operating systems and platforms. For details, refer to the InBatch Installation Guide.

    If IBServ fails to start after being installed on the Windows XP SP3 operating system, you must restart the InBatch Server node.

    We support InBatch Server on Windows XP for both InBatch and IABatch.

    Restrictions

    • InBatch 9.0 with SP1 components are not supported on a single node running on Windows XP SP3. Windows XP SP3 32-bit does not support IIS 6.0, so the InBatch History Server feature cannot be installed.
    • Windows Vista does not support NetDDE. By design, an InBatch application does not serve data on Windows Vista through NetDDE, including InBatch itself.

    Product Compatibility

    • Wonderware Application Server 3.1 SP1, 3.1 SP2, and 3.1 SP2 P01
    • Foxboro Control Software 2.0
    • I/A Series Software 8.4.3, and 8.5
    • Wonderware InTouch® 10.1 SP1, 10.1 SP2, and 10.1 SP2 P01
    • Wonderware Historian 9.0 P02 and 10.0
    • Wonderware Information Server 3.1 and 4.0
    • DIObjects 4.1

    < top of document >

    Installation - Wonderware InBatch 9.0 with SP1

    For installation and upgrade instructions, see the InBatch Installation Guide.

    The upgrade from Wonderware InBatch 9.0 to Wonderware InBatch 9.0 with SP1 is automatic. The upgrade supports Wonderware InBatch 9.0 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.

    For other upgrades see the InBatch 9.0 Readme.

    After you upgrade Batch Reporting Content, a new report template is available, called BatchJournal_EOB. The BatchJournal_EOB template is for an optimized Batch Journal report that is meant to be used with End of Batch report triggers. To schedule this report in Wonderware Information Server, you must manually redeploy the Batch Reports using the Wonderware Information Server Report Deployment tool.

    < top of document >

    Known Issues - Wonderware InBatch 9.0 with SP1

    Installation Issues

    L00104903:

    Upgrading to InBatch 9.0 with SP1 on a computer running Windows 2008 SP2 or later with InBatch 9.0 already installed will fail.

    To fix this, use the UpgradeFix.exe located in the \InBatch Upgrade Tool folder on the InBatch 9.0 with SP1 CD.

    L00106413: If IBServ fails to start after installing on Windows XP SP3, you must restart the InBatch Server node.
    L00106446:

    When installing Batch Server with IA Components on an I/A Series 8.5 system, you should have at a minimum Fox API 4.3.2 with QF1012359.

    After installing this QF, remove the foxapi.dll from the \system32 directory and add D:\opt\fox\ais\bin to the "Path" System Variable in the Environment Variable section of the Computer Properties Advanced tab.

    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).
    4. If it does not exist, create a new DWORD value named SessionViewSize and set it to 30 (hex) or 48 (decimal).

    General Issues

    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.
    L00103853:

    A problem can occur with the BatchMngr warm restart files if you create two batches (in the schedule) with the same CLB, but you use a different case for each. BatchMngr may not start properly if you do this.

    To fix this, remove the warm restart files.
    L00106015:

    An error occurs when you access the Reports link in the Wonderware Information Server Portal after logging in as a system administrator and not as a portal admin of the Wonderware Information Server installed node. To avoid this error, perform any one of the following workarounds:

    • Start Internet Explorer using Run As Administrator command and navigate to the portal using the system administrator credentials.
    • Do the following:
      1. Start Internet Explorer using the Run As Administrator command with the credentials of the user who had configured the Information Server feature and enter the URL: http://localhost/reports/.
      2. Click Properties and then New Role Assignment.
      3. Type the System administrator's user name and grant the roles by selecting the check box for the Content Manager option.
    L00106167:

    If the InBatch Server computer name contains lowercase characters, the development client applications will always get a TAF-lockmgr synchronization error. To fix this issue edit the InBatch Development Client shortcut links in the Start menu to contain the exact case spelling of the InBatch Server name.

    After using the InBatch Configuration Utility to configure the InBatch Development Client, do the following.

    1. On the development client, use the Start menu to navigate to Wonderware\InBatch\InBatch Development Client [Your InBatch Server Name].
    2. Right-click on Material Editor shortcut and then click Properties. In the target box you will see the following string…
      a.–AINBATCHSERVERNAME
    3. Change the spelling of your InBatch Server name to the correct case spelling of your InBatch Server computer. Note: Do not add a space between “-A” and your InBatch Server name.
      1. Do this for each shortcut that has [Your InBatch Server Name] in the name.
    L00106510:

    When you try to print InBatch reports from a Wonderware Information Server client, 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.

    < top of document >

    Resolved Issues - Wonderware InBatch 9.0 with SP1

    The following critical issues are resolved in Wonderware InBatch 9.0 with SP1.

    L00057036: HF CR L00056149 (HotFix 558) SR 1990451: If a Batch Server is placed on the corporate domain with a Windows Server 2003 domain controller, the User name is not being populated into the User Profile table; however, the User ID is.
    L00057092: HF CR L00056151 (HotFix 556) SR 1039380: If a recipe’s phase requires acknowledgement to enter that phase, then the system cannot abort the phase before acknowledgement is received.
    L00062759: HF CR L00062621 (HotFix 626) SR 103110374: The Batch Manager was randomly crashing with an encrypted error log message, which could not be deciphered due to out of sync PDB files.
    L00063411: HF CR L00063125 (HotFix 644) SR 103110535: There was a problem with the Unit Procedure and Operation libraries overwriting the label name with a label number in transitions in Recipe Editor.
    L00063455: HF CR L00063218 (HotFix 645) SR 1039328: Batch Manager shuts down in error when network problems occur between the InBatch Server, the I/O Server, and any Batch Display controls that are used in the InTouch HMI.
    L00063593: HF CR L00062952 (HotFix 646) SR 20112483: After upgrading from InBatch 8.1 to InBatch 8.1 SP1, the message "View_21 is stopping" is shown on the Environment Display if you exit and shut down the InBatch Server while InTouch WindowViewer is still running an application with an InBatch ActiveX control. You must restart the InBatch Server.
    L00072614: HF CR L00071428 (HotFix 783) SR 20112631: Batch Manager was randomly crashing due to expectations thrown during f2remove calls.
    L00075066: HF CR L00075066 (HotFix 874) SR 20112775: You cannot access recipe information using the Automation Server when the recipe is currently opened by the Recipe Manager.
    L00082838: HF CR L00082336 (HotFix 1064) SR 15711225: Running multiple instances of the same phase on the same equipment at the same time causes Batch Manager to crash.
    L00086188: HF CR L00085513 (HotFix 1138) SR 19910702: Running multiple instances of the same phase on the same equipment at the same time causes Batch Manager to crash.
    L00086945: HF CR L00066166 (HotFix 1146) SR 15711031 and SR 23710140: After a security enabled feature is executed for a run-time client InTouch application on a remote node, the username is blank in the UserProfile and AuditEvent tables. The security is configured to be OS Group based.
    L00089211: HF CR L00088817 (HotFix 1258) SR 19910933: The InBatch Recipe Automation server is not creating a unit of measure for a recipe, and when the recipe is synced manually, it uses the defaults in the model.
    L00090284: HF CR L00089356 (HotFix 1292) SR 15711409: The Unilink Manager crashes after running for few weeks because of access violation errors.
    L00090393: HF CR L00090049 (HotFix 1311) SR 103114902: The Batch GUI Config property Message Boxes are not working correctly. If the Range is set to false, no error messages should occur when disconnecting from Batch Manager.
    L00091224: HF CR L00088691 (HotFix 1253) SR 103114779: After a switchover on a new master, the Equipment selection list did not populate with the equipment when the Unit State parameter was enabled in Batch Manager.
    L00091225: HF CR L00090374 (HotFix 1320) SR 103115328: If there are two Campaign Lot Batch names in the Batch Scheduler that are the same except that one has a space in the Batch identifier, Batch view always points to the first Batch.
    L00091281: HF CR L00030115 (HotFix 1349) SR 19911023: IALinker is missing Control block parameters.
    L00092489 & L00103872: HF CR L00100947 (HotFix 1802) SR 103117308: New unit attributes cannot be added to existing recipes because the new unit attributes are not appearing in the equipment requirements. This is preventing the recipe from selecting the correct units when the batch is started.
    L00094053: HF CR L00092157 (HotFix 1401) SR 23517679: The Recipe list is empty when the recipe button is clicked in the batch scheduler on a run-time client node. This issue occurs after a period of inactivity.
    L00094055: HF CR L00092481 (HotFix 1424): When you convert a recipe from a previous version of InBatch, the minus sign (-) in a mathematical expression is converted to a period (.), which leaves the recipe unusable.
    L00094056: HF CR L00092960 (HotFix 1444) SR 103115847: The IA Linker compound block bit parameter was limited to 1 bit on the Windows operating system, whereas on UNIX it is 2 bits.
    L00094057: HF CR L00093150 (HotFix 1458) SR 103115829: For InBatch OS security, if an active directory domain user group has an ampersand (&) in the group name, InBatch security will not authenticate the user and grant access to the application.
    L00094525: HF CR L00092219 (HotFix 1399) SR 15711523: The InBatch Recipe Automation server is not initializing the units of measure for a recipe, and when the recipe is synced manually, it uses the defaults in the model.
    L00096077: HF CR L00094446 (HotFix 1515) SR17132605: When the SFC control is loading a large recipe, the server side is blocked, thus causing the client to disconnect from the Batch Server.
    L00096259: HF CR L00091906 (HotFix 1533): The InTouch HMI is not able to get run-time data from InBatch because the IBServer was not able to parse and resolve the tag name correctly in its database.
    L00096363: HF CR L00094215 (HotFix 1520) SR 103116092: When an IBCLI client is started, the Link and Model databases are opened in shared mode. These databases are closed only when the IBCLI client is closed. Because of this, if you to start around 30 or more IBCLI clients, the database call that opens the Link and Model databases is failing.
    L00096507: HF CR L00092732 (HotFix 1435) SR 17132547: When the InBatch Reporting Content feature is installed, the port number is set to decimal instead of hex decimal. This causes the following error when you try to open the report list within Wonderware Information Server: web server: “The report list is currently not available. There was an error with the sockets while accessing the web server.”
    L00096512: HF CR L00072812 (HotFix 815) SR 23515503: The Batch scheduler is locking up after you schedule a batch with a larger number of recipes defined in the recipe database.
    L00096513: HF CR L00074733 (HotFix 859) SR 15711156: IBCli should validate the OPC quantity prior to sending the value to Batch Manager if the values are associated with a quality of 8 (bad quality).
    L00096514: HF CR L00089353 (HotFix 1289) SR 20113044: InBatch OS Group Based Security is not working. Additional diagnostic logging was added to the batchnativesec.dll to log authentication errors. This logging can be turned on and off.
    L00097727: HF CR L00096541 (HotFix 1607) SR 20113204: PhaseKey ID and BatchKey ID filter parameters are not being passed after an "end of phase" event is triggered.
    L00103208: HF CR L00096293 (HotFix 1593) SR 34230997: Running end of Batch Reports results in the following error: ‘Error ReportQueReader: Could not able to save render and save the file. Details: The operation has timed out’ and the report does not finish.
    L00103758: HF CR L00100010 (HotFix 1813) SR 103116915: If operations are in a branch, the phase parameters are not able to be retrieved using the Recipe Automation Server. If there is no operation branch in a recipe, then retrieval is successful.
    L00103852: HF CR L00103053 (HotFix 1890) SR 15010965: Recipe Editor fails during synchronization and validation if there is mismatch in the phase parameters between the Recipe and Model databases.
    L00103854: HF CR L00101407 (HotFix 1836) SR 103117223: Periodically IBMX was sending response messages that were out of sync with the original requests. These old request responses would get routed to Batch Manager with invalid client data (i.e. memory address), which would cause Batch Manager to exit with a SYS_ERROR.
    L00103868: HF CR L00102627 (HotFix 1875) SR 40210299: The Recipe list is empty when the recipe button is clicked in the batch scheduler on a run-time client node. This issue occurs after a period of inactivity.
    L00103870: HF CR L00103051 (HotFix 1884) SR 103117329: While the logger is logging tags, if it encounters a group of tags in which the first tag does not have a Campaign Lot Batch value, then it will return instead of continuing to check the other tags and write those that have a Campaign Lot Batch value to the historian database.
    L00103871: HF CR L00096463 (HotFix 1604) SR 19911167: The target and set point values were not being written to an InTouch tag or the PLC, if the previous value written to a UDA is the same.
    L00103977: HF CR L00103757 (HotFix 1813) SR 103116915: If operations are in a branch, the value of the parameter retrieved is always the default value as configured in the Model and not the value configured in the Recipe.
    L00106302: HF CR L00100472 (HotFix 1775) SR 19911307: If the BHQ_Host was set to NULL then, the history interface remained active. It should be disabled.
    L00106699: HF CR L00104149 (HotFix 1952) SR: 15711822: Batch Manager stops because of out of sync response messages to queued request messages of the same type (write, advise, etc) for the same tag that are waiting for an ACK.
    L00106702: HF CR L00104929 (HotFix 2006) SR 20113473: In some cases, material identifiers and names were not being updated.
    L00106705: HF CR L00097172 (HotFix 1634) SR 103116579: Terminating the OCXBatch control due to a network disconnection causes the InTouch WindowViewer to stop working.
    L00106709: HF CR L00104184 (HotFix 1973) SR 17132897: When you migrate recipes from InBatch version 7.1 to 9.0, some special characters in the parameters are not converted correctly.
    L00106714: HF CR L00101459 (HotFix 1839) SR 15711817: The IBMX application is leaking memory.

    < top of document >

    Wonderware InBatch Version 9.0 Readme

    New Features - InBatch 9.0

    The following new features are available for InBatch version 9.0.

    InBatch Integration with Wonderware Application Server

    The following changes have been made to integrate InBatch with Application Server.

    Communication with Wonderware Application Server

    The new InBatch Message Exchange (IBMX) component supports MX communications to Application Server. IBMX enables the Batch Manager Service to perform standard, secured, and verified writes to supervisory objects without the need for a user interface. InBatch can more accurately record the date and time stamp of values being collected for the Actuals and Process Data attributes.

    Galaxy as Tag Server

    A Galaxy can now serve as the default tag server for InBatch. IBMX enables you to use Application Server as a tag server. The InBatch tag naming convention has been modified to match the naming conventions used in Application Server. Tags in InBatch have been changed to use a dot (.) as a tag delimiter. The size of unit and phase names have been increased to 16 characters to enable InBatch tag names to map directly to Application Server tag names.

    Security

    InBatch security has been extended to support Application Server (ArchestrA) security. InBatch can obtain the list of valid users from Application Server at configuration time and authenticate users against Application server at run time.

    Reporting Services

    Crystal Reports have been removed from InBatch. All reporting services have been moved to the Wonderware Information Server portal. The new reporting system for InBatch leverages Microsoft Reporting Services.

    Merging InBatch and IABatch

    With this release, IABatch specific components have been added to the InBatch code base. The InBatch installation process has been updated to support components specific to IABatch. Documentation sets have been combined.

    < top of document >

    InBatch Demo - InBatch 9.0

    An InBatch Demo application is provided in the InBatch CD-ROM. It consists of the InBatch configuration files with the Model and Recipe databases and an InTouch Application to interact with batch processing.

    • The InBatch configuration files are located in the following folder on the InBatch CD-ROM: D:\InBatch\cfg\PremierDemo, where D:\ is the drive letter of your CD ROM drive.
    • The InTouch application is located in the following folder on the InBatch CD-ROM: D:\InBatch\InBatchDemoApp, where D:\ is the drive letter of your CD ROM drive.  

    Using the Demo

    The following steps explain how to use the configuration files for the InBatch demo:

    1. Replace the files in the :C\Program Files\Wonderware\InBatch\cfg\Config_A folder with the files in the C:\Program Files\Wonderware\InBatch\cfg\dflt_cfg folder.
    2. Copy the demo configuration files from the C:\Program Files\Wonderware\InBatch\cfg\PremierDemo folder into the C:\Program Files\Wonderware\InBatch\cfg\Config_A folder.
    3. From the Environment Display dialog box, start the Runtime Applications and use the Batch Scheduler and Batch Display to schedule and run batches.

    Using the InTouch Application

    To Use the InTouch demo application, you must follow these steps:

    1. Install RecipeManager from the InTouch CD-ROM.
    2. Copy the files in the WWTSup71.zip file into the InTouch directory.
    3. From the InTouch Application Manager, locate and launch the InBatch Demo using WindowViewer.
    4. Use the InTouch application to interact with the InBatch system by scheduling and running batches.

    < top of document >

    System Requirements - InBatch 9.0

    This section describes the hardware and software requirements to install InBatch version 9.0.

    Recommended Hardware Requirements

    The following hardware is recommended to support InBatch version 9.0:

    • Computer with 3.0 gigahertz (GHz) or faster processor
    • 2 gigabyte (GB) of memory
    • At least 4 GB of available disk space
    • Super VGA (1024 × 768) or higher-resolution video adapter and monitor
    • CD-ROM or DVD drive for installation
    • Keyboard
    • Mouse or compatible pointing device

    Software Requirements

    I/A Series and InFusion configurations are supported only on the operating systems and platforms tested, based on the current technologies that we support. For details, refer to the InBatch User's Guide.

    We support InBatch Server on Windows XP for both InBatch and IABatch.

    Vista Restrictions

    • Vista does not support a traditional InBatch single-node configuration that includes Wonderware Historian (formerly IndustrialSQL Server).
    • Vista does not support NetDDE. By design, an InBatch application does not serve data to any other source, including InBatch itself.
    • Refer to individual product documentation for support of the Vista operating system.

    < top of document >

    Upgrading from a Previous Version - InBatch 9.0

    You can upgrade to InBatch 9.0 from either InBatch 8.0 or InBatch 8.1. Refer to the details that follow.

    Upgrading from InBatch Version 8.0 to InBatch Version 9.0

    You can upgrade InBatch version 8.0 to InBatch version 9.0 by first converting the configuration and then upgrading the InBatch History database.

    To Convert the InBatch Version 8.0 Configuration

    1. If the databases in C:\Program Files\Wonderware\InBatch\cfg\config_A are not empty, delete the contents of C:\Program Files\Wonderware\InBatch\cfg\config_A and copy the contents of \dflt_cfg to \Config_A.
    2. Open the Environment Display.
    3. From the File menu, click Exit and Shutdown.
    4. Close the LogViewer.
    5. From the Start menu, select Run and type C:\Program Files\Wonderware\InBatch\bin\CvtMaster.exe.
    6. Acknowledge the message that informs you to back up your configuration, and ensure that the InBatch History server is operating properly.
    7. Click Configuration to browse and select the location of your configuration.
    8. Click Convert to start the conversion. When the conversion has finished, the conversion program displays information about the databases that were converted, those that failed to be converted or were skipped, and those that were up to date. (You can find a detailed log of the conversion operations is contained in DbCvt.txt.) This file is located in the configuration folder specified in step 5.
    9. Copy the converted configuration files to C:\Program Files\Wonderware\InBatch\cfg\Config_A.
    10. On the Environment Display, on the Update menu, click Runtime.

    The procedure updates CfgLinkDB, EnvDB, RecipeDB, and SecurityDB.

    As part of the upgrade process, you also must upgrade the InBatch 8.0 history database to InBatch 8.1 so that the installation wizard can then upgrade the database to InBatch 9.0.

    To upgrade an InBatch Version 8.0 history database to InBatch Version 8.1

    1. If your Batch archive database is marked read-only, remove this restriction.
    2. Copy \convert\xp_ListReports.dll to C:\Program Files\Microsoft SQL Server\MSSQL\bin.
    3. Copy \convert\xp_SyncReportLog.dll to C:\Program Files\Microsoft SQL Server\MSSQL7\bin.
    4. Run the convert81.bat file that is located in the \convert folder on the InBatch CD. Copy this file to your local drive before you run it. The syntax for running the file is as follows:

    Convert81 <ServNM> <HistDB> <ArchDB>

    where

    <ServNM> is the name of the station where SQL Server resides. This is required. Use the name of the machine being used for the InBatch History Server.

    <HistDB> is the name of the history database. By default, the name is BatchHistory, and the command appears use the default name if it is not provided. Use the name of the history database created by running IB71_SQL_Install.exe.

    <ArchDB> is the name of the archive database. By default, the name is BatchArchive, and the command appears use the default name if it is not provided. Use the name of the archive database created by running IB_SQL_Install.exe

    Example:

    Convert81 InBatch_SQL BatchHistory BatchArchive

    After you have finished upgrading the InBatch version 8.0 History database to InBatch version 8.1, follow the standard upgrading process for the InBatch History server described in the installation instructions.

    Upgrading from InBatch Version 8.1 to InBatch Version 9.0.

    You can upgrade from InBatch version 8.1 by using the installation program. For details, see Chapter 2, "Installation" of the InBatch User's Guide . 

    < top of document >

    Known Issues – InBatch Version 9.0 

    Installation Issues

    L00079361: When the InBatch Development Client is installed, files that cannot be deleted are not listed in a message.

    When you uninstall an InBatch component (server or client), remove all items that may have been left behind, including the \InBatch folder.

    L00079872: In the Feature Selection list of the InBatch Setup dialog box, "1" appears on the icon for the InBatch Development Client.

    The following steps are a workaround for this problem. The final step removes the number 1 and does not produce any changes to the installed state:

    1. Install the InBatch development client and the InBatch run-time clients.
    2. Launch setup.exe.
    3. In the Application Maintenance dialog box, click Modify and then click Next.
    4. Uninstall the InBatch run-time client by deselecting it and install the InBatch PDF documentation. As a result, the InBatch PDF documentation is successfully installed and the In Batch run-time client is successfully uninstalled.
    5. Modify and select the InBatch development client that displays the number 1 and install the InBatch development client.

    L00081166: An error message appears during the installation of InBatch Server with I/A components.

    This message can appear if you select the root directory of the C:\ drive. Respond OK to the message and the installation will continue and complete successfully.

    L00082077: When InBatch cannot find a valid attribute reference in ArchestrA, the batch stops.

    Use the following workaround for this issue:

    1. Start IBMX services in Advise All mode. In the Advise All mode, IBMX advises all Galaxy tags during services startup.
    2. Check the LogViewer for any configuration errors.
    3. If you do not find configuration errors, stop all services.
    4. Remove the Advise All mode.
    5. Start the services.
    6. Schedule and run the batch.

    L00082238: An error dialog box appears when uninstalling InBatch 9.0. This error prevents the uninstall from completing.

    The following steps are a workaround to this problem. Step 6 allows the selection to be uninstalled without any issue when this error occurs.

    1. Install InBatch Server.
    2. Double-click setup.exe, select Modify, and click Next.
    3. From the Select Features list, deselect InBatch Server and select InBatch Development Client (without I/A support).
    4. Continue the installation to completion.
    5. Click Modify.
    6. Select the InBatch Development Client (a 1 appears on the image) and click Next to install the development client.
    7. Perform the uninstall from the Control Panel (select Add/Remove Programs).

    Other Issues

    L00016907: WinXMLExporter does not recognize InBatch 8.1 ActiveX controls as "WONDERWARECONTROL" although they have an entry in the CFGOCX.xml file.

    The workaround is to look in the 3rd Party Controls folder.

    L00030115: A header file that contains all the I/A Batch parameters with their type information has not been updated in the last few releases

    The workaround is to link the tags to an available data type. For a list of available data types, see "Validating Tags" in the Tag Linker chapter of the InBatch User's Guide.

    L00033867: The Batch Manager shuts down unexpectedly with an error during a stress test.

    The disk could be full. Check the disk and clean it.

    L00077400: Editors are not opening on the InBatch development client.

    Use the following workaround:

    1. Open Windows Explorer.
    2. Navigate to C:\Programs\Wonderware\InBatch\cfg\Config_A.
    3. Right-click the file named vista.taf and select Delete.

    L00079313: License detection is inconsistent between the InBatch server and InBatch clients.

    When a valid license is not available on the InBatch Server, a message box with the "Invalid Security Key" message does not appear. The message appears only on the SMC Logger.

    L00079952: [IBMX Component] --- IBMX is crashing when services are stopped after undeploying and deploying Entire Galaxy.

    Stop all the InBatch Services before you undeploy the entire galaxy.

    L00081552: Running InBatch with IA components in a redundant configuration does not fail over when IADriver is shut down.

    The following table shows the redundancy batch status on master/slave 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 Slave Node Status Master Node Status Slave Node Status Master Node Status Slave Node Status
    End process from Task Manager Master failed Master with invalid backup Master failed Master with invalid backup Master failed Master with invalid backup
    Stopped from Runtime Services Master with valid backup Valid backup Master with valid backup Valid backup Master with valid backup Valid backup

    L00082068: An error message does not pop up in InTouch when Batch Manager stops working.

    When you stop all the InBatch services from the Environment Display, the OCxBatch running on the InTouch application does not pop up an error message box.

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

    InBatch uses a dot (.) instead of a hyphen (-) as a delimiter in tagnames. InTouch supports only a hyphen as a delimiter. Before you load the InBatch tagnames 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 being configured and scheduled.

    After the custom reports are populated or deployed to the InBatch > Execute Reports > InBatch list on the Launch Pad, use the following steps to configure and schedule the reports. For example, suppose that a report named "Custom Batch Detail" is populated in the list.

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

    <systemdrive>:\Inetpub\wwroot\Wonderware\InBatchReports\ReportConfig

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

      <Report Name="Custom Batch Detail" />

    3. Save the file.

    Example:

    <Folder>
    <Report Name="Custom Batch Detail: />
    .......
    .......
    .......
    </Folder>

    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.

    < top of document >

    Known Issues – InBatch 9.0 Documentation

    This table lists known issues in the product documentation.

    Item Location of Change Existing Documentation Change
    1 InBatch User's Guide , Section 2: "Installation." In the second table under "Software Requirements," see the entry for I/A Series Batch Station Type of InBatch IDE/IEE Extension. Change the word in italics.

    Wonderware Application Server 3.1 bootstrap and IDE (only when integrating and InFusion)

    Wonderware Application Server 3.1 bootstrap and IDE (only when integrating with InFusion)

    2 InBatch User's Guide, Section 2: "Installation." Instructions for upgrading from InBatch 8.0 to 9.0 are missing.

    Refer to "Upgrading from a Previous Version" in this Readme file.

    3 InBatch User's Guide, Section 4: "Process Modeling." See the table on page 216 (Example - Automatic Tagnames).

    Tag names have dashes for delineators.

    Tag names should have dot delineators.

    4 InBatch User's Guide, Section 12: "Reporting System." In the section "Scheduling Configured Reports," the procedure for scheduling an End of Batch Report has been omitted.

    Missing

    See the procedure immediately following this table.

    5 InBatch User's Guide, Section 24: "System Administration." See the topic "Batch System Configuration Files." In the table entries for CfgIALinkDB and IALinkDB, the file locations are incorrect.

    Location: IASeriesBatch\cfg\Config_A

    Location: InBatch\cfg\Config_A

    To schedule an End of Batch Report

    1. In the Name box, type the name for the scheduled report.
    2. Select the Enabled check box.
    3. From the Report Selection list, select the End of Batch report that you previously configured.
    4. From the Schedule Type list, select End of Batch.
    5. In the Description box, optionally type text that describes the report.

    < top of document >

    InBatch 9.0 Documentation

    The InBatch product library consists of a set of Portable Document Files ( PDF) located in the UserDocs folder of the InBatch installation CD. You need Adobe Reader installed on your computer to view InBatch documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site: http://www.adobe.com/products/acrobat/readstep2.html After installing Adobe Reader, double-click on a PDF file with your pointing device to view the book with Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu. InBatch installation instructions are located in the root folder of the InBatch installation CD as an online help file. You can view these instructions by clicking Help as you complete the InBatch installation procedure.

    Searching InBatch Books with Adobe Reader

    Rewrite the procedure and substitute your product's name. The InBatch version 9 books are delivered as an Adobe PDF package that provides a master index of all books. Using Adobe Reader, you can simultaneously search for a specific topic across all books that belong to the InBatch product library.

    To search for information across all InBatch books simultaneously

    1. Open Adobe Reader.
    2. Press CTRL+SHIFT+F or select Search from the Edit menu. The Search dialog box appears.
    3. Type the word or phrase that you want to search for in the InBatch books.
    4. In the Where would you like to search area, select the option to search all PDF books.
    5. If necessary, locate the InBatch version 9 PDF package located on your Wonderware CD or on a network folder containing copies of the InBatch PDF book files.
    6. Click Search. Adobe Reader lists the InBatch books containing information that matches your search criteria.
    7. Click on the links to open the InBatch book to the topic containing the information that meets your search criteria.

    < top of document >

    © 2011 Invensys Systems, Inc. All Rights Reserved.

    • Источник — «http://archestra.ru/index.php?title=Wonderware_InBatch_Version_9.0_with_SP2&oldid=3713»