Release Notes

FactoryTalk View Site Edition is HMI software for monitoring and controlling applications of any size, from single computer, single user station applications to distributed server-client, multiple user applications. FACTORYTALK VIEW SE SHOULD BE DOWNLOADED USING A SERVER OR STATION SERIAL NUMBER; CLIENT SERIAL NUMBERS MAY NOT PROVIDE ACCESS TO ALL VERSIONS.
Version 14.00.00 (released 11/2023)

Catalog Number FactoryTalk View Site Edition 

These release notes describe version information for FactoryTalk View Site Edition, version 14.00.00 (released 11/2023).

Requirements

This release has the following requirements.

The following are the system requirements for FactoryTalk View SE version 14.00.00 (CPR 9 SR 14).

Hardware requirements

The hardware required with FactoryTalk View SE depends on the demands an application places on the system. Factors that affect the demands include whether a computer hosts application servers such as FactoryTalk View SE server, FactoryTalk Alarms and Events, FactoryTalk Linx, and FactoryTalk Directory, the number of tags logging at the same time, the number of display clients and related components. The greater the demand, the more powerful system is required. In any application, faster processors and more memory will result in better performance. In addition, you should specify a hard drive that has enough disk space to provide virtual memory that is at least twice the size of the physical RAM.

The following is a sample specification of computer hardware to run FactoryTalk View SE applications aligned with the hardware used in product development testing.

Type
Description
Hardware Requirements
Operator Workstation
FactoryTalk View SE Client
or
FactoryTalk View SE Station
Minimum
  • CPU: 2 cores
  • RAM: 4 GB
Recommended
  • CPU: 4 cores or more
  • RAM: 8 GB or more
Engineering Workstation
FactoryTalk View Studio Enterprise
FactoryTalk Linx
Studio 5000
Minimum
  • CPU: 4 cores
  • RAM: 8 GB
Recommended
  • CPU: 8 cores or more
  • RAM: 16 GB or more
Application Server
FactoryTalk View SE server
FactoryTalk View Studio Enterprise
FactoryTalk Alarms and Events tag-based server
FactoryTalk Linx data server with FactoryTalk Alarms and Events enabled
Smaller systems:
Minimum
  • CPU: 4 cores
  • RAM: 4 GB
Recommended
  • CPU: 8 cores or more
  • RAM: 8 GB or more
Medium to larger systems:
Minimum
  • CPU: 4 cores
  • RAM: 8 GB
Recommended
  • CPU: 8 cores or more
  • RAM: 16 GB or more


Software requirements

Operating systems

FactoryTalk View SE is tested on the following operating systems:

* For more information, see Rockwell Automation Knowledgebase Document ID: IN4493 - Windows 10 Support for the FactoryTalk Suite of Rockwell Software products.

Domain controller requirements

The following operating systems are supported for use as domain controllers for FactoryTalk View SE client computers. Using a domain is recommended for applications that include more than 10 computers. If your application includes 10 or fewer computers, they can be organized in a workgroup.

High-resolution display support

Windows 10 v1803 or later is the recommended operating system if running this software with a 2K, 4K, or 8K high-resolution display with scaling up to 125%. For optimal user experiences, use the Windows recommended scaling rate for 2K, 4K, or 8K displays.

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.

Supported browsers

The following web browsers have been tested and are supported for use with this release:

Security requirements

To help meet secure system design requirements, review these publications:

To learn about implementing CIP Security, see CIP Security with Rockwell Automation Products Application Technique (publication SECURE-AT001).

Features

This release includes the following system features.

FactoryTalk View SE version 14.00.00 has the following new and enhanced features.

New features

Enhanced features

Corrected Anomalies in This Release

This release corrects the following anomalies.

The following list identifies the anomalies corrected in FactoryTalk View SE version 14.00.00.

Known Anomalies in This Release

This release has the following known anomalies.

Known Anomalies from Previous Releases

These anomalies are from previous releases but are still known in this release.

Functional Changes

This release has the following functional changes from the previous release.

FactoryTalk View SE version 14.00.00 has the following changes in functionality since the last release.

Restoring data log models within different FactoryTalk Directory

Starting from FactoryTalk View SE version 14.00, the data log configuration for the ODBC database is bound with a specific FactoryTalk Directory. As a result, when importing data log MDF files or restoring an HMI server with data logs within a different FactoryTalk Directory, you must enter a username and password on the Setup tab of the Data Log Models editor to connect to the ODBC database.

Default high DPI settings

To better support the FactoryTalk View SE Client and FactoryTalk View Studio on high-DPI monitors, the high DPI settings of DisplayClient.exe and VStudio.exe are updated by default upon installation with these check boxes selected:

Client Install Portal removed

It's no longer supported to install SE clients through the web browser.

Application Notes

This release has the following application notes.

The following are the application notes for FactoryTalk View SE version 14.00.00.

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 View SE versions 16.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.

System sizing recommendations

When you design and set up a FactoryTalk system, we recommend using the following guidelines. If you find that your system needs to expand beyond these guidelines, contact your Rockwell Automation sales or distributor representative to discuss your application design.

Component
Recommended guidelines
FactoryTalk Alarms and Events
 
FactoryTalk Alarms and Events servers per FactoryTalk Directory
10 non-redundant servers or 10 redundant server pairs* (1)
FactoryTalk tag-based alarms per server
20,000* (2)
Logix device-based alarms per server
10,000* (3)
Total alarms per FactoryTalk Directory
100,000* (4)
FactoryTalk Linx
 
FactoryTalk Linx data servers per FactoryTalk Directory
10 non-redundant servers or 10 redundant server pairs* (1)
Total device tags per FactoryTalk Directory
1,000,000* (5)
Tags per FactoryTalk Linx data server
100,000* (5)
FactoryTalk View SE
 
HMI servers per FactoryTalk Directory
10 non-redundant servers or 10 redundant server pairs* (1)
HMI tags per HMI server
40,000* (6)
Total data logged tags per HMI server (1 second scan rate)
DataLogPro 50,000 or data log model 5,000
Note: If you want to run both DataLogPro and data log model on the same HMI server, reduce the number of tags because the greater the number, the more powerful system is required.
FactoryTalk View SE client sessions simultaneously connected to the application
120* (5)
FactoryTalk ViewPoint SE servers per application
4
FactoryTalk ViewPoint SE concurrent clients per ViewPoint server
50
  1. Because multiple applications can run simultaneously within the same FactoryTalk Directory, the recommended number refers to the sum of servers across applications in one FactoryTalk Directory.
  2. The number of alarm backing tags influences the maximum number of available alarms because they increase the resource requirements of the alarm server. When using backing tags for status and control, a good rule of thumb is to multiply the total number of backing tags by the total number of alarms, and ensure the result is less than 20,000. PlantPAx® users should refer to the PlantPAx Reference Manual PROCES-RM001 for alarm server sizing guidance for a PlantPAx application.
  3. This number is the sum of both instruction alarms and Logix tag-based alarms across all the controller shortcuts in each FactoryTalk Linx server.
  4. The total number of alarms per FactoryTalk Directory includes all FactoryTalk Alarms and Events tag-based and device-based alarms in the directory.
  5. Refer to Knowledgebase Document ID: IN7377 - Amounts of device tags that may have in FactoryTalk View SE application for detailed information to determine system scalability for the total device tags per FactoryTalk Directory.
  6. The maximum number of HMI tags that can be created on a single HMI server is 175,000. Extensive use of HMI tags has a significant performance impact on an HMI server, so Rockwell Automation recommends minimizing their use, and instead using direct-reference tags as much as possible.

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

Installing this product’s latest version with earlier unpatched versions of other FactoryTalk products or products using Classic OPC DA connections may cause a loss of connectivity due to the difference in DCOM authentication level used. For additional information, see the Knowledgebase Document ID: IN39461 - Microsoft DCOM Hardening Information TOC.

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

Unattended installation

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

Command-line parameters

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").

Parameter
Description
/?
Displays the usage options for installation parameters.
/Q
Silent Install, install runs in a quiet mode without any user interface.
This parameter is recommended when deploying the software installation using an IT tool or script, and don’t expect any error or restart messages. When using this parameter, check the error codes, and respond as needed. For example, if the installation returns error code 1641, then the IT tool or script should restart the computer and relaunch the installation after restart.
This parameter is required if /QS is not specified.
/QS
Unattended Install, install runs in a quiet simple mode and shows progress through the UI, it does not accept any input but still shows error or restart messages.
When using this parameter, the installation will stop and display a prompt if there are error or restart messages. For example, if an immediate restart is required to complete the install, a restart message will be displayed to confirm the restart. Installation resumes automatically from the point of interruption after restart.
This parameter is required if /Q is not specified.
/IAcceptAllLicenseTerms
Acknowledges acceptance of the license terms.
This parameter is required for /Q or /QS parameters.
/AutoRestart
Automatically restarts the computer after the installation is complete. Used when a restart is required to complete the installation.
This parameter is optional. If this parameter is not used, silent install (/Q) will return either error code 1641 or 3010 if a restart is required, and unattended install (/QS) will result in a confirmation prompt that must be agreed to before the installation is completed.
/SetupLanguage="value"
Specifies which language will be displayed during the install process.
The value must be the one of the following:
  • ENU
  • CHS
  • DEU
  • ESP
  • FRA
  • ITA
  • JPN
  • KOR
  • PTB
This parameter is optional. If this parameter is not used, the default language is the current user or operating system user interface language.
/Record
Records the installation options chosen to a recording file.
This parameter is optional.
/Playback
Plays back a recording file to specify the installation options.
This parameter is optional.
/IgnoreWarning
Specifies that the setup ignores warnings and continues.
This parameter is optional. If it is not specified, the setup exits when a warning occurs.
/Product="value"
Specifies which sub-products will be installed.
This parameter is required.
For FactoryTalk View ME, the value must be one of the following:
  • Studio for Machine Edition
  • Machine Edition Station for Windows
  • Stand-alone ME Transfer Utility
For FactoryTalk View SE, the value must be one of the following:
  • Studio Enterprise
  • Site Edition Server
  • Site Edition Client
  • Site Edition Station
  • FactoryTalk ViewPoint SE
  • Stand-alone FactoryTalk Linx Server
  • Stand-alone FactoryTalk Directory Server
/DirectoryServer="value"
Specifies the FactoryTalk network directory if you are using a distributed system.
This parameter is optional. If it is not specified, the software will use its current computer as the FactoryTalk Directory server.
The value must be the host name of the FactoryTalk Directory server.
/SystemStatusPortal="value"
Specifies that the installation includes the FactoryTalk System Status Portal.
This parameter is optional.
The value must be one of the following:
  • Yes
The FactoryTalk System Status Portal will be installed.
  • No
The FactoryTalk System Status Portal will not be installed.
/NoHTTPS
Specifies that the setup turns off HTTPS.
This parameter is optional. If it is not specified, the setup turns on HTTPS for communication, and a TLS certificate must be configured after installation.
/IISCommPort
Specifies the IIS server communication port for HTTPS. The default port for HTTPS is 443.
If the HTTPS port was previously configured using FactoryTalk Services Platform, like port 4356, then the existing HTTPS port setting is retained.
This parameter is optional.
/Uninstall
Uninstalls the product.
/Repair
Runs a repair operation on the installed products.
This parameter is optional.
/InstallDrive="value"
Specifies the installation drive.
This parameter is optional. If this parameter is not used, the default install drive is C:.
/SerialNumber="value"
Specifies the serial number of the software being installed. This is used to activate the software during installation.
This parameter is optional. If it is not specified, the software must be activated manually after installation if activation is required.
Some software does not require activation. If activation is not required, this parameter is not available.
/ProductKey="value"
Specifies the product key used to get activation keys during installation.
This parameter is optional. If it is not specified, the software must be activated manually after installation if activation is required.
Some software does not require activation. If activation is not required, this parameter is not available.
/Version="value"
Specifies the version of the software to activate, which corresponds to the product version associated with the SerialNumber and ProductKey.
This parameter is optional. If it is not specified, the installer will use the most recent product version available.
Some software does not require activation. If activation is not required, this parameter is not available.
/RemoveApp
Deletes the application files when uninstalling the product.


Error codes

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

Error Code
Value
Description
ERROR_SUCCESS
0
The installation completed successfully.
ERROR_INVALID_PARAMETER
87
One of the parameters was invalid.
ERROR_INSTALL_USEREXIT
1602
The installation was canceled by the user.
ERROR_INSTALL_FAILURE
1603
A fatal error occurred during installation.
ERROR_BAD_CONFIGURATION
1610
The configuration data for this product is corrupt. Contact your support personnel.
ERROR_SUCCESS_REBOOT_INITIATED
1641
The installer has initiated a restart. After restart, the installation will continue.
ERROR_SUCCESS_REBOOT_REQUIRED
3010
A restart is required to complete the installation. After restart, the product is successfully installed.
ERROR_REBOOT_PENDING
3012
Restart pending. Restart the computer for the installation to continue.
ERROR_SUCCESS_NOT_APPLICABLE
3013
The installation cannot proceed because the products are already installed.
ERROR_SUCCESS_WARNING_REBOOT
3014
The installation succeeded with warnings. Check the installation log file for details. To complete the installation, restart the computer.

HTTPS enabled by default

If you install Studio Enterprise, Site Edition Server, or FactoryTalk ViewPoint SE on a computer with no FactoryTalk View component installed, the installation enables HTTPS by default.

If HTTPS is enabled, you must configure a TLS certificate after installation. If you do not configure the certificate, there will be unexpected errors when operating FactoryTalk View SE components. For details on configuring a TLS certificate, see FactoryTalk View Site Edition Installation Guide.

Security requirements

For information on the security considerations when using Rockwell Automation products, including

CIS Benchmarks test results

Rockwell Automation conducts tests using domain-joined computers configured according to CIS Benchmarks to help assure that software products perform as expected on computers that are hardened to industry best practices.

For more information about the guidelines, see the Knowledgebase Document ID: QA63609 - Recommended guidelines for hardening software, computer, device, and network systems and infrastructure (CIS Benchmarks).

FactoryTalk View SE version 14.00.00 has been tested on CIS Microsoft Windows 10 Enterprise Benchmark v2.0.0, CIS Microsoft Windows Server 2019 Standard Benchmark v2.0.0, CIS Microsoft Windows 11 Enterprise Benchmark v2.0.0, and CIS Microsoft Windows Server 2022 Standard Benchmark v2.0.0.

Exceptions settings for FactoryTalk View SE version 14.00.00 are listed.

CIS Microsoft Windows 10 Enterprise Benchmark v2.0.0

CIS Microsoft Windows Server 2019 Standard Benchmark v2.0.0

CIS Microsoft Windows 11 Enterprise Benchmark v2.0.0

CIS Microsoft Windows Server 2022 Standard Benchmark v2.0.0

UAC support

Turning off User Account Control (UAC) is not recommended.

This action
Prompts for authentication or confirmation before running this program
Configuring Internet Information Services (IIS)
RSViewWebManager.exe  CustomWebSite.exe
Updating Samples application directory information
RefreshSampleApplication.exe
End processes
VSClean.exe
DeskLock
DeskLock2000.exe
Legacy Tag Database Conversion
LegacyTagDBConvertTool.exe


VeriSign Universal Root Certification Authority certificate

If the VeriSign Universal Root Certification Authority certificate does not exist on the local computer, the certificate is installed while installing Rockwell Automation software. Use Microsoft Management Console (MMC) to view the certificate in Console Root > Certificates (Local Computer) > Trusted Root Certification Authorities > Certificates.

KEPServer

If you are using KEPServer Enterprise as an OPC server with FactoryTalk View version 9.00.00 or later and using an HMI tag to connect to a third-party device, you will not be able to access the tag value. The cause is that the security enhancements in FactoryTalk View version 9.00.00 or later affect the communications with third-party devices. To access the tag value, additional Distributed Component Object Model (DCOM) configuration is required for KEPServer Enterprise on the computers.

For more information about the configuration, see Set DCOM configuration for KEPServer Enterprise in Help.

Considerations for application server host computers

In a network application, it is possible for a single-server computer that meets the recommended requirements to host all of the following components:

If a network application requires multiple HMI servers, data servers, or alarm servers, to distribute the load, it is recommended that you install the necessary software and run the servers on multiple host computers.

For information about setting up redundant FactoryTalk View SE servers, see FactoryTalk View Site Edition User’s Guide.

TrendPro objects

Clicking on the X-axis or Y-axis takes it into the free layout mode. In this case, anything done to the canvas is how you want it and it does not resize. The free mode does not persist scale and removes tags from the trend. Avoid using the free mode in the trend.

FactoryTalk Batch View HMI controls

Using EChartsWidget .NET control and earlier versions of FactoryTalk Batch View HMI controls in the same FactoryTalk View SE application may have compatibility problems. To avoid such problems, we recommend that you use the built-in version of Batch View HMI controls included in the FactoryTalk View installation package. For example, EChartsWidget of FactoryTalk View version 14.00 and Batch View HMI controls version 2.02 or earlier cannot be used in the same application. To fix this problem, upgrade Batch View HMI controls to version 3.00.

Resolve error 0x80010100

In some rare cases, FactoryTalk Live Data might fail to call FactoryTalk View SE with an error 0x80010100. This is because the application exceeds the limit of posted messages per message queue defined in Windows. By default, there is a limit of 10,000 posted messages per message queue in Windows.

To resolve this problem, you need to manually increase the limit by modify the USERPostMessageLimit registry key.

  1. Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows NT > CurrentVersion > Windows, and then double-click USERPostMessageLimit.
  2. Select Decimal, and then increase the value.
Note: The recommended value to fix this problem is 20,000, which should be sufficiently large. However, if the issue persists, change it to a greater value.
Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such terms and making changes to our products and content. Please excuse the use of such terms in our content while we implement these changes.

Copyright © 2026 Rockwell Automation, Inc. All rights reserved.
Rockwell Automation, Allen-Bradley, and FactoryTalk are trademarks of Rockwell Automation, Inc.
To view a complete list of Rockwell Automation trademarks please click here.
Trademarks not belonging to Rockwell Automation are property of their respective companies.