Review these minimum and recommended system requirements for installing, configuring, and running FactoryTalk Batch version 15.00. Unless noted, these requirements assume that no other applications are installed on the computer. Preferred operating systems and software applications are prioritized for support, testing, and post-release patch qualifications.

Hardware requirements

• Server requirements
  • 8 -GB of RAM memory
  • 100-GB free hard disk space
  • Intel® Core™ i5 standard power processor or greater
• Client requirements
  • 4-GB of RAM memory
  • 30-GB free hard disk space
  • Intel Core i5 standard power processor or greater

Supported operating systems

• Windows Server®
  • Windows Server 2019 Standard Edition (preferred)
  • Windows Server 2016 Standard Edition (preferred)
  • Windows Server 2019 DataCenter Edition
  • Windows Server 2016 DataCenter Edition
  • Windows Server 2012 R2 Standard Edition or DataCenter
  • Windows Server 2012 Standard Edition or DataCenter
• Windows®
  • Windows 10 Professional (64-bit) Build 1909 or later (preferred)
  • Windows 10 Enterprise (64-bit) Build 1909 or later

Supported database applications

(for storing recipes, materials, reports, and journal archives)

• SQL Server®
  • SQL Server 2019 (English version only)
  • SQL Server 2017 (English version only)
  • SQL Server 2016 Service Pack 1 (English version only)
  • SQL Server 2014 Service Pack 3 (32-bit and 64-bit, English version only)
  • SQL Server 2012 Service Pack 4 (32-bit and 64-bit, English version only)

Web browsers

(for FactoryTalk Batch View only)

• Google® Chrome™ browser (preferred)
• Microsoft Edge™ based on Chromium version: 80.0.361.50 or higher
• Apple® Safari®
• Firefox®

Logix firmware requirements

(for FactoryTalk Batch only)

• Firmware version 18 or later on ControlLogix 5570 and CompactLogix 5370 family of controllers – for integration of PhaseManager with FactoryTalk Batch
• Firmware version 32 or later on ControlLogix 5580 and CompactLogix 5380 family of controllers – for integration of PhaseManager with FactoryTalk Batch
• Firmware version 29 or later on ControlLogix 5570 and CompactLogix 5370 family of controllers - for integration of SequenceManager with FactoryTalk Batch

Logix Designer Application requirements

(for FactoryTalk Batch only)

• Studio 5000 Logix Designer version 18 or later - for synchronization of PhaseManager with FactoryTalk Batch Equipment Editor

FactoryTalk View SE requirements

(for integration of FactoryTalk Batch View HMI Controls)

• FactoryTalk View SE version 13.0 (preferred)
• FactoryTalk View SE version 12.0

FactoryTalk Services requirements

• FactoryTalk Services Platform version 6.30 (CPR 9 SR 13) or later
• FactoryTalk Linx version 6.30 (CPR 9 SR 13) or later
• FactoryTalk Activation Manager version 4.06 or later

Rockwell Automation Test Environment

Rockwell Automation tests software products under a standard configuration of operating systems and antivirus software. For additional information, see the Knowledgebase Document ID: PN24 - Rockwell Software Products and Antivirus Software.

Warranty

The warranty does not cover systems that do not meet the minimum requirements for the version of software.

• The FactoryTalk Batch Server computer cannot be configured as a:
  • Domain controller
  • DHCP server
  • WINS server
  • RAS server
  • DNS server
  • Master Browser
• The FactoryTalk Batch Server computer does not support replication.
• Install FactoryTalk Batch software on an NTFS formatted hard disk drive, as Windows security features are available only for drives that are formatted to use NTFS.
• Warranty does not cover systems with modified DCOM configuration settings. Configuring settings using DCOMCNFG may stop the FactoryTalk Batch Server and prevent the FactoryTalk Batch Service Manager from functioning correctly.

FactoryTalk Batch version 15.00 has the following new and enhanced features:

New features

FactoryTalk Batch

• Controller program name property

  FactoryTalk Batch version 15.00 adds a property that specifies the controller program name of the Equipment Phase or Equipment Sequence for phases and operation sequences when connected to a a Logix5000 CIP data server. This enables modular design concepts, promotes the reuse of code and simplifies the integration of skids into a common system.

• Increased tag count

  The FactoryTalk Batch Server in version 15.00 supports area models that contain up to 210,000 total tags. This provides better support for OPC/Live Data tags.

Enhanced features

• Runtime area model editing

  FactoryTalk Batch version 15.00 supports deleting objects from an area model while the batch is running. This feature makes the FactoryTalk Batch system more flexible and easier to adapt to changing requirements while still improving the amount of system uptime and overall productivity. Changes made to the area model are saved, but only applied to the runtime system when explicitly deployed to the runtime server. Deployment is conditional based on verification of both the changes to the area model and the impact to runtime system.

• Install improvements

  FactoryTalk Batch View and FactoryTalk Batch View HMI Controls can be installed using the same installation program as the other FactoryTalk Batch software.

Deprecated features

The FactoryTalk eProcedure Client, legacy FactoryTalk Batch View Client, and the FactoryTalk Batch ActiveX Controls are not included nor supported by FactoryTalk Batch 15.00. If your production system has dependencies on these products, transition to the modern FactoryTalk Batch View and FactoryTalk Batch View HMI Controls before upgrading to FactoryTalk Batch 15.00.

The following list identifies the anomalies corrected in FactoryTalk Batch version 15.00. Use the identification information provided in the brackets [] to track the anomaly in future releases or if you need assistance from Customer Support with a related issue.

BatchIDCreation project update needed for Batch Server [914495]

Custom BatchIDCreation project in .Net format is needed. Current version is out of date with modern development tools.
In FactoryTalk Batch 15.00 a new BatchIDCreate project is provided.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

Recipe Editor allows the use of reserved words in expressions [914545]

In FactoryTalk Batch 15.00 the Recipe Editor will provide Recipe Verification Warnings for step collisions where the name of a Parameter or Report collides with a step attribute (such as ERROR, MODE, FAILURE, OWNER, and so on).  The Transition Expression Editor Dialog will display an error message if name collision warnings are detected.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

Master Recipe List slow to populate [914551]

In FactoryTalk Batch 15.00 the Recipe Object Model processing was improved to provide a faster load time.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 13.02

Recipe Editor terminates when saving formulation to SQL database [982003, 1369929]

When using the SQL storage format attempting to save or validate a recipe that contains one or more formulations, the Recipe Editor crashes and the changes to the recipe are lost. In FactoryTalk Batch 15.00 the recipes are saved and validated without issue.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

Batch View Server Product Policies missing on remote FactoryTalk Directory [1063952]

In FactoryTalk Batch 15.00 the Batch View Server Product Policies are installed as part of FactoryTalk Services Platform 6.30.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

FactoryTalk Batch View Server fails to provide eProcedure instructions for multiple recipes [1064202]

When FactoryTalk Batch View does a getInstruction or getState call to the eProcedure Server it provides the set of createIDs for the Batches that correspond the the eProcedure instructions. If the client requests multiple createIDs and one of them is wrong the eProcedure server returns an error saying: "Unable to retrieve recipe step information for the specified procedure" and none of the instructions are provided. In FactoryTalk Batch 15.00 each createID is evaluated individually and the relevant instructions are provided.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch View 1.02

FactoryTalk Event Archiver Installation failure when using SQL Server on a named instance [1105890]

In FactoryTalk Batch 15.00 the installation program has been updated to use a different method of determining if SQL Server is installed.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

Recipe Editor is slow to open when first started [1144064]

When using RDB recipe format, with approval workflows enabled, the Recipe Editor may take a long time to open and may appear to be stuck. It may also take longer than expected to launch and display the Open Recipe dialog.  These performance issues are especially noticeable when using a large number of recipes. FactoryTalk Batch 15.00 improves the performance of the Recipe Editor when using RDB recipe format with approval workflow enabled.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

Recipe Editor open file dialog delayed response [1146906]

When using SQL recipe storage format, the Open File dialog would take a long time to to open. FactoryTalk Batch 15.00 improves the performance of the Open Dialog when using SQL storage format.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

Batch Server service unexpectedly terminates when logging error information [1172391]

The Batch Server service terminates when handling a small number of uncommon errors. In FactoryTalk Batch 15.00 the error handling was updated so that the Batch Server responds appropriately.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

Batch Server service terminates when a batch created from a UPC recipe is remove from the Batch List [1176902]

In FactoryTalk Batch 14.00 the removal of a unit procedure from the batchlist could randomly cause the Batch Server service to unexpectedly terminate. In FactoryTalk Batch 15.00 the removal logic was revised to allow removing of the batch. 

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

Batch Server Memory growth when using formulations [1194413]

When reading formulation data, the BatchSvr.exe memory usage grows. This memory growth may lead to performance issues with the FactoryTalk Batch system and may lead to termination of the Batch Server service. This can occur when using any the FactoryTalk Batch Client applications, or by using the INFO_TRIMMED, FOMULATION_DATA, and FORMULATIONS_INFO API calls directly. The memory growth is especially fast when using large recipes with a large number of formulation sets. In FactoryTalk Batch 15.00 the system correctly handles allocation and deallocation of memory for the API calls.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

eProcedure Step Verification Signature does not include the full user name [1302092]

In FactoryTalk Batch 15.00 a new way to configure the step verification signature was implemented. This method made changes to the following:

• eProcedure Server:
  • Updated to include the FactoryTalk UserId information when providing signature data
  • Updated to provide a configuration option that can be set by the user to indicate how the signature information should be displayed by a client to the user (Usename, UserId, or Username and UserId)
• Batch View server
  • Updated html display and parsing logic to handle the configured eProcedure display option: Username, UserId, or Username and UserId
• FactoryTalk Batch View
  • Updated to display the correct signature information (Username only – default, UserId, or Username and UserId) based on the configured eProcedure display option.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 13.00.02

No indication when the Batch server has issues writing entries to the Batch event journal [1325957]

In FactoryTalk Batch 13.00.02 there is no indication if the Batch server has issues writing entries to the Batch event journal. In FactoryTalk Batch 15.00, if the Batch server has issues writing entries to an event journal, it will attempt to log a message to the FactoryTalk Diagnostics log, and when possible, will include the details of the errant journal event in that message.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 13.00.02

FactoryTalk Batch installation does not set the correct service account for eProcedure Server [914598]

When adding FactoryTalk eProcedure and Material Manager Editor to an existing FactoryTalk Batch install, the installer will incorrectly set the service account used to run the eProcedure Server. It also does not configure the computer name of the Material Manager Server. The installer for FactoryTalk Batch 15.00 now prompts the user for the required information.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

Unsupported integer datatypes result in error [914582] 

Tags with USINT, SINT, UINT, INT, and UDINT datatypes in the controller are not supported by FactoryTalk Batch. Attempting to read or write to these tag types may result in a phase failure. 

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

Upgrade failure when installing FactoryTalk Batch with FactoryTalk Event Archiver [914577] 

Upgrade may fail unexpectedly when installing FactoryTalk Batch with FactoryTalk Event Archiver. In this situation, the install does not complete and system becomes unresponsive. This situation occurs because previous versions of the FactoryTalk Batch uninstall program do not always successfully remove the existing ODBC DSN entry for the Batch Event Archiver data source. The FactoryTalk Batch 15.00 installer checks for an existing "FactoryTalk Batch Events" DSN during the install process. If there is, it will remove the existing DSN and create a new one.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

Area model updates: When deploying runtime area model updates the system does not check for activations [00369234]

The system only checks for licenses when the Batch Server is started. If the area model modifications require more activations than are available, a restart of the Batch Server will fail during the license check.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

FactoryTalk Batch View

FactoryTalk Batch 14.00 included FactoryTalk Batch View 2.00. FactoryTalk Batch 15.00 includes FactoryTalk Batch View 2.01. Anomalies corrected in patches released subsequent to the release of FactoryTalk Batch 14.00 are included in the list of anomalies corrected in this release.

Using "textarea" tag in eProcedure html file causes a command error in Batch View [990743]

If an eProcedure html instruction file uses a "textarea" tag for a phase report parameter it will prevent the instruction from completing, when you select the OK button after filling in the text box you get the error "Control Step was already responded to by another client". In <FTBV 2.01 the FactoryTalk Batch View client and server were updated to properly handle textarea tags

Corrected Anomaly with FactoryTalk Batch View 2.01
Known Anomaly First Identified in FactoryTalk Batch View 2.00

Batch Reports not working in FactoryTalk Batch View HMI Control [1277219]

Selecting the Reports control in the FactoryTalk Batch View HMI User Controls results in a white display. In FactoryTalk Batch View 2.01 the HMI User Controls open the Reports view as expected.

Corrected Anomaly with FactoryTalk Batch View 2.01
Known Anomaly First Identified in FactoryTalk Batch View 2.00

Signature cancellation causes issues with future steps [1430586]

Completing a sign-off of a manual instruction signature request generated after a cancellation of a manual instruction signature causes FactoryTalk Batch View to become unresponsive.

Corrected Anomaly with FactoryTalk Batch View 2.00.11
Known Anomaly First Identified in FactoryTalk Batch View 2.00

Modern FactoryTalk Batch View client only allows scaling up to 1000% [1327777]

The legacy FactoryTalk Batch View client had a limit of 3.40282³⁸ on the Batch Scale setting. The modern FactoryTalk Batch View client was designed to place an upper limit of 1000% on the Batch Scale setting. Patch 2.00.10 replaces this limit with the previous limit of 3.40282³⁸ returning the Batch View functionality to parity with the legacy client.

Corrected Anomaly with FactoryTalk Batch View 2.00.10
Known Anomaly First Identified in FactoryTalk Batch View 2.09

User ID is blank in FactoryTalk Batch journal when eProcedure instructions are completed using FactoryTalk Batch View [1302090]

Event Signatures from the eProcedure server did not include the User ID (also referred to as user login name and user name), making it difficult to validate the signatures. This release updates the FactoryTalk Batch View Server to provide the option to store the User ID of the user that completes the eProcedure instruction in the event journal.

Corrected Anomaly with FactoryTalk Batch View 2.00.09 and FactoryTalk Batch 14.00.00.309
Known Anomaly First Identified in FactoryTalk Batch 2.00.08 and FactoryTalk Batch 14.00

FactoryTalk eProcedure instructions result in unresponsive client [1072655]

When requesting FactoryTalk eProcedure instruction information for multiple recipes, the request will fail for all recipes if there is an issue with any of the recipes in the request. This can lead to performance issues with FactoryTalk eProcedure instructions, and a potentially unresponsive client.

With FactoryTalk Batch View 2.00.08, FactoryTalk eProcedure Instruction information requests for recipes that do not have errors will be processed, regardless of whether other recipes have errors or not.

Corrected Anomaly with FactoryTalk Batch View 2.00.08
Known Anomaly First Identified in FactoryTalk Batch 2.00.07

FactoryTalk Batch View resubmitting completed instructions [1064081]

FactoryTalk Batch View submits the completion of an instruction multiple times, which can result in the next instance of an eProcedure phase being skipped.

Corrected Anomaly with FactoryTalk Batch View 2.00.07
Known Anomaly First Identified in FactoryTalk Batch 1.02.66

Batch View Server stops responding after FactoryTalk Batch View error [1064112]

FactoryTalk Batch View encounters an error while processing an expression, which may cause the Batch View Server to stop responding.

Corrected Anomaly with FactoryTalk Batch View 2.00.07
Known Anomaly First Identified in FactoryTalk Batch View1.02.60

UserID is blank in FactoryTalk Batch journal when eProcedure instructions are completed using FactoryTalk Batch View [1064092]

In FactoryTalk Batch View 2.00.07 the UserID of the user that completes the eProcedure instruction is passed to the Batch Server and included in the event journal.

Corrected Anomaly with FactoryTalk Batch View 2.00.07
Known Anomaly First Identified in FactoryTalk Batch View 1.02.66

FactoryTalk users have read-only access when using FactoryTalk Batch View  [CLM 5101]

Product policies for FactoryTalk Batch View were not installed. Product policies now install correctly.

Corrected Anomaly with FactoryTalk Batch View 2.00.05
Known Anomaly First Identified in FactoryTalk Batch View 1.01

Batch View Security: The Batch View 1.02 policies and 2.00 policies do not coexist in a FactoryTalk directory [899076]

Security granularity has changed from FactoryTalk Batch View 1.02 to 2.0. New security policies were added for FactoryTalk Batch View and FactoryTalk Batch View HMI controls. In the initial release of FactoryTalk Batch View version 2.00 the policies that were used by FactoryTalk Batch View 1.02 and FactoryTalk Batch View HMI Controls 1.02 were no longer available.

In FactoryTalk Batch View version 2.00.05 the FactoryTalk Batch View 1.02 security policies were restored and disambiguated from the FactoryTalk Batch View version 2.00 security policies so that they could coexist in the FactoryTalk Directory and both clients can be supported.

Corrected Anomaly with FactoryTalk Batch View 2.00.05
Known Anomaly First Identified in FactoryTalk Batch View 1.01

FactoryTalk Batch Material Manager

Material Server not able to access the material database remotely [925005]

The installation program for the Material Server was not setting the RemoteAccessEnabled key for remote access to the material database.

Corrected Anomaly with FactoryTalk Batch 15.00
Known Anomaly First Identified in FactoryTalk Batch 14.00

The following list identifies the anomalies that were identified during testing of FactoryTalk Batch version 15.00. Use the identification information provided in the brackets [] to track the anomaly in future releases or if you need assistance from Customer Support with a related issue.

FactoryTalk Batch View

Port conflict when using HTTPS [1536376]

FactoryTalk View SE, FactoryTalk Services Platform and FactoryTalk Batch View support secure communication using HTTPS and use the default HTTPS port 443. There are two situations in which this port conflict could impact FactoryTalk Batch View.

1. FactoryTalk Batch View is installed before FactoryTalk View SE
   The FactoryTalk View SE installation processes does not check for port conflicts when installing with the option Secure communication with TLS and does not provide the option to select a different port. If FactoryTalk Batch View is installed first and assigns port 443 to its secure communication and then FactoryTalk View SE is installed and the option Secure communication with TLS is selected the installation will fail with communications errors due to the port being unavailable. The FactoryTalk Batch View installation process does detect the port conflict and provides the option to select a different secure communications port. First identified in FactoryTalk Batch View 2.01.

   To work around this issue, install FactoryTalk Batch View after FactoryTalk View SE.

2. Installing new FactoryTalk-enabled software that uses HTTPS communication after installing FactoryTalk Batch View
   Because the other FactoryTalk software do not check communication during install a port conflict (port 443) will be created. As a result, FactoryTalk Batch View client and HMI user controls cannot communicate with the FactoryTalk Batch View server. First identified in FactoryTalk Services Platform version 6.30.00.

   Use one of these workarounds to resolve this issue:

• If you installed FactoryTalk Reverse Proxy:
1. On the computer hosting a FactoryTalk-enabled software server, open FactoryTalk Administration Console.
2. In the Explorer pane, go to localhost > System > Policies > System Policies > Security Policy.
3. Change Reverse Proxy Port to other available ports instead of 443.
4. If Reverse Proxy Port is changed, the system will make changes to Site Bindings in Internet Information Services (IIS) Default Web Site.
5. You may need to remove port 443 in IIS to ensure that the software works appropriately.
6. You may also need to configure Product Policies for the FactoryTalk-enabled software to ensure that its HTTPS port in use is the same as Reverse Proxy Port.
7. Select Apply, and then select OK.
• If you did not install FactoryTalk Reverse Proxy:
  1. On the computer hosting a FactoryTalk-enabled software server, open FactoryTalk Administration Console.
  2. Go to localhost > System > Policies > Product Policies > FactoryTalk-enabled software> HTTPS Protocol.
  3. Change the port to other available ports instead of 443.
  4. Select Apply, and then select OK.
  5. Open Internet Information Services (IIS) Manager.
  6. In the Connections pane, select the server and site for the FactoryTalk-enabled software.
  7. In the Actions pane, click Bindings.
  8. In the Site Bindings dialog box, select the HTTPS site binding, and then click Edit.
  9. Change the port number to the one you configured in Step 3.
  10. Click OK.

Videos are not displayed correctly in manual instruction content served from Batch View Server (1503087)

• The relative path for an image would be:  <img src=”image01.jpg”>
• The relative path for a video would be:  <video><source src=”eprocedure/video01.webm” /></video>
• The relative path for a script would be:  <script src=”eprocedure/script01.js”></script>

Installing FactoryTalk Batch version 14.00 and later updates FactoryTalk Services Platform to version 6.20 [00369202]

There is a known anomaly in FactoryTalk Services Platform 6.11 and 6.20 that impacts FactoryTalk Event Archiver components. When FactoryTalk Diagnostics version 6.11 or 6.20 and Microsoft SQL Server Reporting Services 2017 or 2019 are installed on the same computer, Microsoft SQL Server Reporting Services fails to work. This anomaly was first identified in FactoryTalk Services Platform version 6.11.00.

To avoid this problem, change the default port used by Microsoft SQL Server Reporting Services from 8082 to another port.
For steps to address the issue after installation is complete, see Knowledgebase Document ID: BF25929 - SQL Server Reporting Services stops working after installing FactoryTalk Diagnostics.

FactoryTalk Batch Material Manager

Material Editor cannot access the material database after upgrading FactoryTalk Batch [929120]

The MTUser account is not in the correct database. Anomaly first identified in FactoryTalk Batch 14.00.

To work around this issue use these steps:

1. Open the SQL Server Management Console.
2. Navigate to the database Logins and delete the MachineName\MTUser login.
3. Navigate to the material database and open the list of users: delete the user account MTUser.
4. Run the script MaterialTrack_DBSecurity.sql on the material database. This will recreate the MTUser user account under the database.
   The script is located in the C:\Program Files(x86)\Rockwell Software\Batch\Scripts folder.
   Access to the material database should now be restored.

FactoryTalk eProcedure

Cannot create HMI Server on a computer with FactoryTalk eProcedure and FactoryTalk View SE [00369237]

After adding eProcedure to a FactoryTalk Batch and FactoryTalk View SE install, an HMI Server cannot be created.

To work around this issue, restart the computer after installing eProcedure, then create the HMI Server. 

 FactoryTalk Batch View 2.00

Pop-up notifications are persistent [519919, 519912]

For example: When an invalid login is used, a pop-up notification is displayed, indicating that the login is invalid. The notification is not cleared even after a successful login is completed.

Anomaly first identified in FactoryTalk Batch View 2.00.

To work around this issue, the user must close the notification.

Unintended actions from Arbitration Summary page [98187]

On the Arbitration Summary page, when the More menu is open and a user selects Enter, the first item in the More menu is executed, resulting in possible unintended actions.

Anomaly first identified in FactoryTalk Batch View 2.00.

To avoid this issue, in FactoryTalk Security, enable confirmation messages, which prompt to confirm before actions are performed in FactoryTalk Batch View.

Spurious "No master recipes are released to production" message [263925]

When adding a batch to the batch list, the client may display a "No master recipes are released to production" message while the system is gathering the control recipe data.

Anomaly first identified in FactoryTalk Batch View 2.00.

To work around this issue, wait for the recipes to load. The message disappears after the recipes are loaded.

Spurious client reports of control recipe removal [471548]

During the runtime area model update, the control recipe may be inaccessible to the client, causing the client to report that the control recipe has been removed.

Anomaly first identified in FactoryTalk Batch View 2.00.

The control recipe is not actually removed, so you can ignore this message

Filters not functioning on Arbitration Summary page [760902]

On the Arbitration Summary page, when performing a warm restart or applying a run-time area model update, applied filters may not function as expected.

Anomaly first identified in FactoryTalk Batch View 2.00.

To work around this issue, reapply filters.

Filter values are not cleared automatically [98193]

When a user sets filter values on a phase while on the Equipment page and then restarts the FactoryTalk Batch View Server, the filter values are not cleared automatically.

Anomaly first identified in FactoryTalk Batch View 2.00.

To work around this issue, after restarting the FactoryTalk Batch View Server, manually clear the filter values.

FactoryTalk Batch View HMI Controls 1.00

FactoryTalk View SE Client process lock [360350]

When a Display Client is closed while running a FactoryTalk View SE display that contains the FactoryTalk Batch HMI Controls, the Display Client process keeps running as a background process. This may prevent the ability to launch subsequent instances of the Display Client.

Anomaly first identified in FactoryTalk Batch View HMI Controls 1.00

To work around this issue, reboot the machine on which the FactoryTalk View SE Display Client is executing.

FactoryTalk View Batch server authorization changes only reflected in FactoryTalk View SE user interface only after login [362225]

If a change is made to the FactoryTalk Batch View authorization policies when a FactoryTalk View SE display containing an HMI Control is in runtime, the change is not reflected in the user interface.

The user is required to log out and then login with valid credentials for the new authorization policy changes to be reflected in the user interface.

Removed BaseFilter batch remains on batch list [CLM 4578]

If a BaseFilter batch state is applied (such as State:Running) and the state changes for a currently visible batch on the Batch List, the batch is visibly removed from the list and the message: Control Recipe <name> has been removed appears.

Even though the applied BaseFilter removes visibility to the batch, the batch is actually still on the batch list and can be viewed from other clients or HMI Controls that do not filter based on the batch state.

FactoryTalk Batch version 15.00 has the following functional changes:

Change in operating system support

Beginning in this release, the product installer prevents installation on all 32-bit versions of Windows operating systems (for example, Windows 10, 32-bit) and any Windows 7 operating system (for example, Windows 7 Professional, 64-bit).

Installation

• The install wizard for FactoryTalk Batch has been revised for improved usability.
• System requirements have changed. Review the System requirements topic for the list of operating systems, SQL Server versions, and Rockwell software applications supported in this release.

eProcedure

• The eProcedure server will check the FactoryTalk Batch server status at startup. If the FactoryTalk Batch server is not running, the eProcedure server will not start.
• eProcedure instructions no longer support embedded COM objects nor vbscript. Any Visual Basic® scripting instructions should be converted to JavaScript.
  Browsers such as Microsoft Edge, Google Chrome browser, Mozilla Firefox, and Apple Safari, do not support Visual Basic scripting. In these browsers, Visual Basic scripting actions are ignored and no error message is displayed.

The FactoryTalk Batch version 15.00 release has the following application notes.

Impact of Microsoft deprecating VBScript

Microsoft announced the phased deprecation of VBScript in 2024. VBScript is now an optional feature beginning in Windows 11 24H2 and Windows Server 2025. Many FactoryTalk software products released before September 1, 2026, use VBScript during installation.

FactoryTalk Batch versions 18.00.00 and earlier require VBScript for installation. Installation will fail if VBScript is not enabled.

To mitigate the problem, enable VBScript manually. For more information, see the Knowledgebase Document ID: IN41397 - Impact of Microsoft deprecating VBScript. FactoryTalk software products released after September 1, 2026, no longer rely on VBScript.

Mitigation for Microsoft DCOM Hardening patch

In response to Microsoft Distributed Component Object Model (DCOM) Hardening patch (MS KB5004442), the minimum DCOM authentication level used by Rockwell Automation products was raised to Packet Integrity.

Microsoft releases the DCOM Hardening patch in response to CVE-2021-26414. This patch elevates the minimum DCOM authentication level that is required to establish a DCOM connection. DCOM is used by many Rockwell Automation products and may be affected by the change that is made by the Microsoft patch. For additional information about the affected Rockwell Automation products, see the Knowledgebase Document ID: PN1581 - Product Notification 2022-01-001 - Rockwell Automation products unable to establish proper DCOM connection after installing Microsoft DCOM Hardening patch (MS KB5004442).

Upgrade

• Before upgrading to FactoryTalk Batch version 15.00 you must uninstall the previous release and then delete the Batch View Server folder located at C:\Program Files (x86)\Rockwell Software\Batch View Server. Failure to do so will result in the inability to start the FactoryTalk Batch Server.
• Upgrading from RSLinx CIP communication to FactoryTalk Linx CIP communication is a manual operation. Use these steps:
1. Open the FactoryTalk Administration Console and then navigate to FactoryTalk Linx.
2. Create FactoryTalk Linx shortcuts to the controllers that have the Phase Manager phases or Sequence Manager sequences.
3. Open the area model in the Equipment Editor and navigate to the Data Servers.
4. Edit each Data Server that is the type Logix5000 CIP, changing the FactoryTalk Linx Controller Shortcut to shortcuts created in step 2.

• Security granularity was changed between FactoryTalk Batch View 1.02 to 2.0. New security policies were added for FactoryTalk Batch View and FactoryTalk Batch View HMI controls. In the initial release of FactoryTalk Batch View version 2.00 the policies that were used by FactoryTalk Batch View 1.02 and FactoryTalk Batch View HMI Controls 1.02 were no longer available. In FactoryTalk Batch View version 2.00.05 the FactoryTalk Batch View 1.02 security policies were restored and disambiguated from the FactoryTalk Batch View version 2.00 security policies so that they could coexist in the FactoryTalk Directory and both clients can be supported. However, if you restore a backup version of the FactoryTalk Diagnostics that was taken before installation of FactoryTalk Batch View 2.00.05 the policy structure will revert and not have the correct policies available for FactoryTalk Batch View Server. In this situation, reinstall FactoryTalk Batch View 2.00.05 or later to reconstruct the policies int he FactoryTalk Diagnostics.

FactoryTalk Batch

• The FactoryTalk Batch version 15.00 installation requires that the Remote Registry service is set to Automatic and Running. Due to changes in the Windows operating systems, this service only runs for 10 minutes before stopping.

  Immediately start the installation of FactoryTalk Batch 15.00 after the Remote Registry service is started.

• Logix5000 CIP Data servers must use the first instance of a FactoryTalk Linx service.

  FactoryTalk Linx version 6.20 installs two instances of the FactoryTalk Linx data server. Only the first instance named FactoryTalk Linx Instance01 Server supports the necessary communication interfaces to connect to PhaseManager and SequenceManager on a Logix controller.

  When configuring a Logix5000 CIP data server for communications with PhaseManager or SequenceManager, be sure to select the data server that is using the first instance of the FactoryTalk Linx service.

  Use these steps to identify which instance of FactoryTalk Linx is assigned to a data server:

  1. Start FactoryTalk Administration Console.
  2. In the Explorer pane, browse to the data server
  3. Right-click the data server name and select Properties.
  4. On the General tab, verify that the entry under Server Type is FactoryTalk Linx Instance01 Server.
     Tip: For more information, see the FactoryTalk Linx Help topic What's FactoryTalk Linx instance02 service?

• FactoryTalk Batch Service Manager does not use Single Sign-On credentials.

  You must log in to FactoryTalk before using the FactoryTalk Batch Service Manager.

  This is because performing a deployment to a runtime server is treated as an elevated privileges operation when launched from the FactoryTalk Batch Service Manager. To run with elevated privilege the FactoryTalk Batch Service Manager must:

  • Always prompt for a username and password.
  • Not use the Single Sign-on User.
  • Not set the Single Sign-on User.

Command-line parameters

Use command-line parameters to perform an unattended or silent installation of the software.

The following table identifies the installation command-line parameters. Command-line parameters are case-insensitive. However, if a specified value includes a space, be sure to enclose the value in quotation marks (for example, "value with spaces").

Common Rockwell Automation parameters

These parameters are applicable for all Rockwell Automation software that are available in the installation package.

FactoryTalk Batch-specific command line parameters

The command-line install of FactoryTalk Batch performs a full install of FactoryTalk Batch. To install FactoryTalk Batch, FactoryTalk <EA>, FactoryTalk Batch Material Manager, or FactoryTalk Batch View HMI Controls separately use the installation wizard instead of the command-line.

These options are specific to installing FactoryTalk Batch software:

Example

The following example shows how to use the installation commands.

• To install the software with no user interface specifying a custom HTTPS port and copying custom content during the installation process.

Setup.exe /Q /IAcceptAllLicenseTerms /DomainWorkgroup=Domain /BatchDomain=MyDomain /BatchUserName=User1 /BatchPassword=s3cretp@ssw0rd! /Product=FTBatch /BatchServerName=BatchServer1 /HTTPS_PORT_USER=8443 /CopyCustomerContentSelected=Yes

Error codes

The following table identifies the error codes that can be returned by an installation.

FactoryTalk Batch Material Manager

• The installation program requires TLS 1.0 be enabled so that the SQL server scripts can create and update the Material Manager database. TLS 1.0 is not used by the application and can be disabled after installation is complete.
• Material Editor is a COM+ application. If another service starts or logs in using the same identity before the Material Server is started, stopping that service logs off the user account. If the Material Editor is connected before the other service is stopped, it will still have access to the Material Server, but if it disconnects from the Material Server it will not be able to reconnect until the server is rebooted or the previous service is restarted. For more information and potential workarounds, see the information about COM+ applications on the Microsoft web site.

FactoryTalk Batch Enterprise Integration Server

• Install the FactoryTalk Batch Enterprise Integration Server after completing the FactoryTalk Batch installation to add support for developing enterprise integration features using the provided API.

  The FactoryTalk Batch EI Server.msi file is in the EIServer folder of your FactoryTalk Batch 15.00 installation media.