Known Issues

2456284

AVEVA Batch Management application messages are not logged in SMC until the node is rebooted after installation.

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 Foxboro DCS 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.

IMS 3609976

The I/O tag write failures may occur when AVEVA Batch Management 2023 R2 is installed on top of System Platform 2023 R2.

Workaround: Apply the Hotfix 3609976.

IMS 3647440

Users will be unable to log in to the System Platform IDE using the AVEVA Connect SSO configuration if Batch Management 2023 R2 is installed on top of System Platform 2023 R2.

Workaround: Upgrade System Platform to 2023 R2 SP1.

IMS 3647457

The InTouch web client does not display the deployed object's tag values at runtime when Batch Management 2023 R2 is installed on top of System Platform 2023 R2.

Workaround: Upgrade System Platform to 2023 R2 SP1.

IMS 3647498

Error "LicAPI.Loader.Core" and warning "vcp.services.onprem.frontdoo'" are logged in the SMC logger when deploying the AVEVA Batch Management 2023 R2 OMI Web View App on System Platform 2023 R2.

Workaround: Upgrade System Platform to 2023 R2 SP1.

IMS 3647528

Configuring "Microsoft Entra ID" as the Federated Identity Provider in the configurator will cause the System Platform IDE to crash when adding new roles, if Batch Management 2023 R2 is installed on top of System Platform 2023 R2.

Workaround: Upgrade System Platform to 2023 R2 SP1.

IMS 3648047

You may observe an exception in the Event Viewer when stopping Batch Management Services (IBServ).

This issue occurs on Windows 2019, 2022, and 2025 but does not affect functionality.

IMS 3650140

If AVEVA Batch Management 2023 R2 is uninstalled from a system that also has other AVEVA products installed, the "System Management Server" and "Federated Identity Provider" features might revert to an unconfigured state.

Workaround: Reconfigure the "System Management Server" and "Federated Identity Provider" features.

IMS 3678006

Uninstalling AVEVA Batch Management 2023 R2 also removes the LicAPI (x64) feature when AVEVA System Platform 2023 R2 SP1 is installed.

Workaround: Reinstall the AVEVA Enterprise Licensing Platform feature.

IMS 3692747

The startup time for the AVEVA Batch Management 2023 R2 (v13.1) IBMX service is longer with System Platform 2023 R2 SP1.

Workaround: Apply the Hotfix 3692747.

IMS 3696628

The startup time for the AVEVA Batch Management 2023 R2 (v13.1) IBMX service is longer with System Platform 2023 R2.

Workaround: Apply the Hotfix 3696628.

IMS 2353338

Unknown Opcode Internal Error dialog box is displayed in AVEVA InTouch 2023 when Batch Management ActiveX application switches to runtime.

Workaround: Apply AVEVA System Platform 2023 P01 Patch.

1055512

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

Workaround: Do the following settings in the Firefox browser:

3. Open the Firefox browser.

4. Navigate to Options > General.

5. Under the Performance option, clear the Use recommended performance settings and Use hardware acceleration when available check boxes.

6. Restart the 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:

7. Browse to the Directory where reporting services is installed.

   For example: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer.

8. Open the file named reportserver.config.

9. Insert the following line in the document:

   <Configuration >

   .......

   <HTMLViewerStyleSheet > SafariChromeFix </HTMLViewerStyleSheet>

   .......

   </Configuration >

10. Save the file.

11. Navigate to C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\Styles directory.

12. Make a copy of the file named SP_Full.css, and name the copy SafariChromeFix.css.

13. Update the following lines to the top in the SafariChromeFix.css file:

    div { overflow: visible !important; }

14. 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 AVEVA Batch Management development client.

Workaround:

15. Open a Microsoft Windows Explorer page.

16. Navigate to C:\Program Files (x86)\AVEVA\Batch Management\cfg\Config_A.

17. Right-click the file vista.taf, and then select Delete.

L00081552

Running Wonderware InBatch with Foxboro DCS components in a redundant configuration does not fail over when FoxDCSDriver is shut down.

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

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.

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

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

19. Open the file RptServicesConfig.xml for editing.

20. Add the following line under the <Reports> node:

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

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

22. Create a new folder and name it (E.g. Test). Ensure that the folder name is not Config_A.

23. Copy the contents of the Config_A folder to the new folder.

24. Run cvtmaster, directing it to the new folder.

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

26. Install and configure Batch Management Server on Node #1.

27. Install and configure Batch Management History and Reports on Node #2.

28. Launch Environment Display on Node #1.

29. Launch History Admin page or Report Web page on Node #2.

Workaround:

30. Launch Internet Explorer on Node #2.

31. Under Tools, select Internet Options.

    The Internet Options dialog box appears.

32. Click the Security tab and then select Trusted sites.

33. Under Security level for this zone, click Custom level.

    The Security Settings – Local Intranet Zone dialog box appears.

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

157908

When the BatchHistory database and Batch Management reports are in distributed nodes, Batch Management reports execution is failing with the error "An error has occurred during report processing. (rsProcessingAborted). Query execution failed for dataset 'BatchDetailData'. (rsErrorExecutingCommand). Login failed for user 'NT Authority\Anonymous Logon' ".

Workaround:

To overcome this error, do the following.

35. On the node where the Batch Management reports are configured, navigate to the SSRS Reports page.

36. Open the Batch Management Reports folder and then click the ibReports data source.

    The ibReports data source Configuration Settings page appears.

37. Select the Credentials stored securely in the report server option for Connect using.

38. Provide the credentials of the user who has access to the "BatchHistory" database.

39. Click Test Connection to check if the provided user details have access.

40. Once the connection succeeds, click Apply to save configuration settings.

41. Execute the Batch Management reports from the Reports node and any other remote node where the Reports feature is not configured.

42. Ensure that reports are executed successfully without any issues.

IMS 1700890

After upgrading Batch Management to the latest version and when you import the Batch model in IDE, the following error gets displayed:

"Error in creating toolsets or templates Method not found".

Workaround:

To overcome this error, do the following.

43. Close IDE.

44. Restart the "ArchestrA GalaxyRepository" service from the System Services window.

45. Launch IDE and import the Batch Management Model.