This release has the following requirements.
The following are the system requirements for FactoryTalk View SE version 16.00.00 (CPR 9 SR 16).
Hardware requirements
The hardware required to run FactoryTalk View SE depends on the demands that an application places on the system. Greater demand requires more powerful hardware. Factors influencing these demands include:
Modern CPU specifications, including core and thread counts, base frequency, max turbo frequency, and architectural efficiency all affect performance. For optimal results, we recommend using higher-end hardware configurations featuring a process speed of at least 2.4 gigahertz. Faster processors, higher memory capacity and speed, and solid-state drives yield better performance. Compared to Windows 10, Windows 11 generally needs more system resources. Additionally, ensure that the hard drive has sufficient disk space to provide virtual memory at least twice the size of the physical RAM.
Virtual Machines (VMs) are limited by the CPU megahertz of the physical core. A common misconception is that a VM can use as much CPU megahertz as needed from the combined total available. In reality, one virtual CPU (vCPU) of a VM never uses more megahertz than the maximum of one CPU core.
These tables provide sample hardware specifications for running different FactoryTalk View SE applications, based on the hardware used in development testing.
Distributed application
|
Type
|
Description
|
Hardware Requirements
|
|
Operator
Workstation
|
FactoryTalk View SE client
|
Minimum
Recommended
|
|
Engineering
Workstation
|
FactoryTalk View Studio
FactoryTalk Linx
Studio 5000
|
Minimum
Recommended
|
|
Application
Server
|
FactoryTalk View SE server
FactoryTalk View Studio
FactoryTalk Alarms and
Events tag-based server
FactoryTalk Linx data server with
FactoryTalk Alarms and Events enabled
|
Smaller systems (less than 10,000 tags
and 1,000 alarms):
Minimum
Recommended
|
| Medium to larger systems (more than
10,000 tags and 1,000 alarms):
Minimum
Recommended
|
Station application
|
Type
|
Description
|
Hardware Requirements
|
|
Station
Application
|
FactoryTalk View SE station
|
Smaller stations (less than 1,000 tags
and 500 alarms):
Minimum
Recommended
|
| Medium to larger stations (more than
1,000 tags and 500 alarms):
Minimum
Recommended
|
Software requirements
Operating systems
The following operating systems are supported and recommended*:
*The recommended operating systems have priority for Microsoft Patch Qualifications with Rockwell Automation software.
**Windows Server Datacenter editions are supported. The key difference between Windows Server Standard and Datacenter edition is how Microsoft licenses the operating system. Windows Server Standard includes licensing for up to two virtual machines per core license, making it suitable for lightly virtualized environments. Datacenter edition allows unlimited virtual machines per core license, offering better value for highly virtualized or cloud-scale deployments.
***Windows 11 IoT Enterprise LTSC and Windows 11 Enterprise LTSC are binary equivalents but are licensed differently. Windows 10 IoT Enterprise LTSC and Windows 10 Enterprise LTSC are binary equivalents but are licensed differently.
****For more information, see Rockwell Automation Knowledgebase Document ID: IN4493 - Windows 10 Support for the FactoryTalk Suite of Rockwell Software products.
Rockwell Automation's software installation policy is based on the lifecycle information of Microsoft operating systems. If an operating system's lifecycle state is approaching its end, you may encounter a warning message when trying to install Rockwell Automation software on it.
|
Microsoft
lifecycle
policy
|
Rockwell Automation installation warning
policy
|
Rockwell Automation installation
prevention policy
|
|
Fixed
|
Present a warning message during installation
on Microsoft operating systems that are 18
months before Microsoft's extended end date.
|
Prevent installation on Microsoft
operating systems that are six months
past Microsoft's extended end date.
|
|
Modern
|
Present a warning message during installation
on Microsoft operating systems that are 18
months before Microsoft's retirement date.
|
Prevent installation on Microsoft
operating systems that are six months
past Microsoft's retirement date.
|
The following table illustrates how the installation policy is applied using the current operating systems. For the latest compatibility information, refer to the Microsoft Lifecycle Policy and Product Compatibility and Download Center.
|
Operating system
|
Microsoft
lifecycle policy
|
Extended
end date
|
Retirement
date
|
Installation
warning
|
Installation
prevented
|
|
Windows 11 Enterprise
and Professional editions
|
Modern
|
None
|
None
|
None
|
None
|
|
Windows 10 Enterprise
and Professional editions
|
Modern
|
None
|
October 14,
2025
|
April 14, 2024
|
April 14, 2026
|
|
Windows Server 2025
Standard and Datacenter
editions
|
Fixed
|
October 10,
2034
|
None
|
April 10, 2033
|
April 10, 2035
|
|
Windows Server 2022
Standard and Datacenter
editions
|
Fixed
|
October 14,
2031
|
None
|
April 14, 2030
|
April 14, 2032
|
|
Windows Server 2019
Standard and Datacenter
editions
|
Fixed
|
January 9,
2029
|
None
|
July 9, 2027
|
July 9, 2029
|
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
If running this software with a 2K or 4K high-resolution display with scaling up to 125%, you can expect acceptable results. 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 are supported for use with this release:
Security requirements
To learn about designing a secure networking environment, review this publication:
To learn about implementing application-level security using FactoryTalk Security, review this publication:
To learn about designing and implementing an architecture with device-level security using CIP Security, review these publications:
This release includes the following system features.
FactoryTalk View SE version 16.00.00 has the following new and enhanced features.
New features
The toggle switch allows you to configure on/off controls in HMI applications using predefined shapes and assign Boolean tags for state management.
The linear gauge is a graphic control for displaying real-time process values with configurable alerts, limits, and layout options. It also includes a built-in sparkline that shows current and recent process values in a compact format.
Enhanced features
FactoryTalk View SE version 16.00.00 supports InfluxDB 3 Enterprise that is deployed on the Linux operating system.
TrendPro and XY Plot support structured data retrieval from FactoryTalk Historian SE Asset Framework.
RecipePro supports optional Unit, Min, and Max columns to define measurement standards and valid input ranges for recipe parameters.
A new VBA method that allows you to zoom into specific regions of TrendPro and XY Plot charts even though the toolbar or the Rubberband Zoom button is hidden.
The Web Browser object's context menu is disabled for enhanced system security.
This release corrects the following anomalies.
The following list identifies the anomalies corrected in FactoryTalk View SE version 16.00.00.
First reported in version 14.00.00. [Jira 5060688]
This release has the following known anomalies.
To ensure proper functionality of CurrentUserHasGroup, join the computer to the Active Directory domain.
To resolve this issue, make sure that the FactoryTalk Directory server is connected in a network distributed system.
This issue occurs due to the unintended handling of temporary files created when displays are opened in either FactoryTalk View SE client or FactoryTalk View Studio, especially within the Windows Remote Desktop Server (RDS) environment. For specific causes and associated solutions, see Knowledgebase Document ID: BF27588 - FactoryTalk View SE - No longer able to open displays in FactoryTalk View Studio or FactoryTalk View SE client.
The security token lifetime is controlled by the FactoryTalk Directory session lease security policy. When the session lease expires, users authenticated using LDAP or LDAPS must manually re-authenticate. If this is disruptive to the application, the system administrator can disable session expiration by setting the lease value to zero. Configure this setting in FactoryTalk Administration Console > System > Policies > System Policies > Security Policy > Logon session lease.
This issue occurs because the display retains the original window size from the first time it's opened. To resolve this issue, use the /Max parameter to open the display maximized, ensuring it adapts to the current window size.
This issue occurs due to how Microsoft's window management handles maximized child windows. To avoid this issue, try setting the display's design-time size to match the client window size, ensuring consistent sizing when opened.
To resolve these issues, avoid docking navigation menus perpendicularly on the same window in the multi-monitor setup.
To resolve this issue, set the object's initial visibility to true.
This occurs because the standby HMI server needs to synchronize with the active HMI server upon restart. The SE client will resume normal performance after synchronization is completed.
To resolve this issue, insert a short delay (for example, using the Sleep function) at the end of the VBA script.
To resolve this issue, restart the HMI client computer and connect the secondary HMI server to the network.
To resolve this issue, ensure the tag path is no longer than 255 characters.
These anomalies are from previous releases but are still known in this release.
This issue occurs due to the unintended handling of temporary files created when displays are opened in either FactoryTalk View SE client or FactoryTalk View Studio, especially within the Windows Remote Desktop Server (RDS) environment. For specific causes and associated solutions, see Knowledgebase Document ID: BF27588 - FactoryTalk View SE - No longer able to open displays in FactoryTalk View Studio or FactoryTalk View SE Client.
Datalogoff <name of datalog> and then the command
Datalogon <name of datalog>.Pause 5 command between the launch of each SE client file. This will allow the start of each SE client to be offset from each other.HKEY_USERS\.DEFAULT\Software\Rockwell Software\RSView Enterprise\Data Log
HKEY_USERS\S-1-5-18\Software\Rockwell Software\RSView Enterprise\Data Log
To avoid this issue, do not insert such string tags in a button toggle action's remark.
There is no workaround for this issue.
There is no workaround for this issue.
To view the annotation, right-click and select Annotation from the context menu.
To resolve this issue, set the Live Data policy to TCP/IP.
To resolve this issue, after performing any of those actions, restart your computer.
To avoid this issue, use other login types to log in.
First identified in FactoryTalk Service Platform version 6.40.00. [Jira 3289981]
These documents are renamed with the latest version of FactoryTalk Services Platform, and the older version of FactoryTalk View is hard-coded to previous names. You can view these documents in C:\Program Files (x86)\Common File\Rockwell\Help:
You can also view the FactoryTalk Services Platform Help and Release Notes from the FactoryTalk Administration Console Help menu.
This release has the following functional changes from the previous release.
FactoryTalk View SE version 16.00.00 has the following changes in functionality since the last release.
Updated internal communication mechanisms
The internal communication mechanisms are updated to align with modern security standards, resulting in a more robust and secure distributed architecture. These enhancements also improve performance in specific workflows, such as opening legacy applications with a high volume of displays or global objects in FactoryTalk View Studio and importing large HMI projects to remote computers.
This release has the following application notes.
The following are the application notes for FactoryTalk View SE version 16.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 pairs1
|
|
FactoryTalk server tag-based alarms per
FactoryTalk Alarms and Events server
|
20,0002
|
|
Logix device-based alarms per FactoryTalk
Linx server instance
|
20,0003
|
|
Total alarms (server tag-based alarms and
Logix device-based alarms) per server
computer
|
40,000
|
|
Total alarms (server tag-based alarms and
Logix device-based alarms)
per FactoryTalk Directory
|
150,000
|
|
FactoryTalk Linx
|
|
|
FactoryTalk Linx data servers
per FactoryTalk Directory
|
10 non-redundant servers or 10 redundant server pairs1
|
|
Total device tags
per FactoryTalk Directory
|
1,000,0004
|
|
Tags per FactoryTalk Linx data server
instance
|
100,0004
|
|
FactoryTalk View SE
|
|
|
HMI servers per FactoryTalk Directory
|
10 non-redundant servers or 10 redundant server pairs1
|
|
HMI tags per HMI server
|
40,0005
|
|
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
the system is required.
|
|
FactoryTalk View SE client sessions
simultaneously connected to the
application
|
120
|
|
FactoryTalk ViewPoint SE servers per
application
|
4
|
|
FactoryTalk ViewPoint SE concurrent
clients per ViewPoint server
|
50
|
| |
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:
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. When
applied, the installation process automatically creates a recording file
<Product>.REC that is stored in this path: %USERPROFILE%\Desktop.
This parameter is optional.
|
|
/Playback="value"
|
Plays back a recording file to specify the installation options. The value
is the full path of the REC file to be used.
For example,
/Playback="C:\Users\<Username>\Documents\<Product>.REC".
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 subproducts will be installed.
This parameter is required.
For FactoryTalk View ME, the value must be one of the following:
For FactoryTalk View SE, the value must be one of the following:
|
|
/ftsp-s="value"
|
Specifies the FactoryTalk Directory scope for restore. Only "global" and
"local" directory scopes are supported.
This parameter is optional.
|
|
/ftsp-bak="value"
|
Restores the FactoryTalk Directory backup file and specifies where the
restore file can be found.
Rockwell Automation provides a NETWORK_SECURE.BAK backup file
containing pre-configured access control lists, which limit user access.
The pre-configured access control lists follow Rockwell Automation
recommended best practice.
To implement the access control, restore the NETWORK_SECURE.BAK
backup file located in the FactoryTalk Services Platform installation
package, Redist\FTSPSecureBak. The BAK file is only supported for the
"global" scope, which can be specified with /ftsp-s.
This parameter is optional.
Important:
Applying a BAK file during installation will overwrite the existing
FactoryTalk Directory content. Use with caution when applying this
parameter.
|
|
/ftsp-pp="value"
|
Specifies the plaintext password used to decrypt the backup file.
This parameter is optional.
|
|
/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. The FactoryTalk Web Authentication Server
and FactoryTalk Reverse Proxy will be installed by default with
the FactoryTalk System Status Portal.
This parameter is optional.
The value must be one of the following:
If the value is Yes, the FactoryTalk System Status Portal will be
installed. The FactoryTalk Reverse Proxy and FactoryTalk Web
Authentication Server will also be installed as it is required for
operation of the FactoryTalk System Status Portal.
If the value is No, the FactoryTalk System Status Portal will not be
installed, but Internet Information Services (IIS) will be enabled.
|
|
/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 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.
|
|
/HMIFolder="value"
|
Specifies the folder to store the HMI projects.
This parameter is optional. If you specify a folder that doesn’t exist yet,
it will create a folder for you.
The larger the size of HMI projects, the longer it takes to set up the
folder. Thus, if the size of HMI projects is large, we recommend that
you use the HMI Projects Folder Path Config Utility to configure the
new HMI projects folder after the installation.
|
|
/NoDemo
|
Skips the demo applications when installing the product.
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.
|
Enable HTTPS option selected 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 selects the Secure communication with TLS (enable HTTPS) option by default. With HTTPS enabled, the RSViewSE site's Require SSL setting is also enabled in Internet Information Services (IIS), deactivating the HTTP protocol (with the default port 80).
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
UAC support
Turning off User Account Control (UAC) is not recommended.
|
Action or Utility
|
Prompts for Authentication or Confirmation Before Running
This Program
|
|
Installation process
|
Setup.exe
RSViewWebManager.exe
RefreshSampleApplicaiton.exe
|
|
Uninstallation process
|
Setup.exe
VSClean.exe
|
|
FactoryTalk View SE Website Setup
|
CustomWebsite.exe
RSViewWebManager.exe
|
|
DeskLock
|
DeskLock2000.exe
|
|
Legacy Tag Database Conversion
|
LegacyTagDBConvertTool.exe
|
|
HMI Projects Folder Path Config Utility
|
HMIProjectsFolderPathConfigUtility.exe
|
|
FactoyTalk View SE Cache File
Management Tool
|
FTViewSECacheFileManagementTool.exe
|
|
FactoryTalk DB Connection Config
Utility
|
RNADBConnConfigUtil.exe
|
|
FactoryTalk Alarms and Events
Database Update Utility
|
FTAEDatabaseUpdateUtility.exe
|
HMI server creating or opening impacted by SQL Server disk sector size limitation
Some newer storage devices and device drivers expose a disk sector size greater than the 4 KB limit supported by SQL Server. If a device exposes a larger sector size, SQL Server is unable to start due to the file system incompatibility.
This issue impacts the creating and opening of an HMI server that relies on SQL Server LocalDB. Specifically:
To verify the sector size of your system's drive C, run this command fsutil fsinfo sectorinfo C: in the Command Prompt as an administrator, and then check the PhysicalBytesPerSectorAtomicity and PhysicalBytesPerSectorPerformance values.
If either value exceeds 4096, you can configure the system to emulate a 4 KB sector size using the ForcedPhysicalSectorSizeInBytes registry key.
For more information, see Microsoft article: Troubleshoot errors related to system disk sector size greater than 4 KB.
Redundant servers
To restart primary and redundant servers such as FactoryTalk Linx (formerly RSLinx Enterprise), FactoryTalk Alarms and Events, or HMI servers, we recommend that you restart one server at a time. Wait for the first server to fully start, and then enter Active or Standby status before restarting the second server in the redundant pair. Doing so prevents both servers from restarting simultaneously, which might cause them to become unresponsive.
To change redundant server switchover settings, ensure the FactoryTalk Directory server is online. If these settings are changed while the FactoryTalk Directory server is offline, they will not be applied when the FactoryTalk Directory server returns online.
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.
InfluxDB: Memory usage
To help prevent excessive memory usage by the Influxd.exe process, consider balancing the number of tags being queried and the querying frequency, and adjusting your data retention period (storage duration) to optimize system performance.
InfluxDB: Ensuring access during administrator upgrade
If FactoryTalk View SE is upgraded by a different administrator, access to InfluxDB may be restricted because the upgrading administrator lacks permissions to the InfluxDB database.
To ensure uninterrupted access to InfluxDB, do either of the following before upgrading:
However, if the upgrade is completed without any precautions beforehand, you can still restore the InfluxDB access. In addition to either of the operations as described above, you must also reset InfluxDB. To do so, go to C:\Program Files (x86)\Rockwell Software\RSView Enterprise, and then run the SetupInfluxDB.exe /r command to reset InfluxDB.
InfluxDB 3 Enterprise: Windows stability limitation
InfluxDB 3 Enterprise may occasionally close unexpectedly when deployed on the Windows operating system. For optimal performance and stability, deploy InfluxDB 3 Enterprise on Linux or use the built-in InfluxDB OSS.
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.
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, the 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
FactoryTalk Batch View HMI Controls and FactoryTalk View SE components, such as EChartsWidget .NET control, use the Chromium Embedded Framework (CEF). Due to its limitations, CEF does not support multiple versions of CEF loaded in the same process. If you do not plan to use multiple CEF components, there are no version constraints. If you plan to use multiple CEF components in a single FactoryTalk View SE application, ensure that they are compatible. For example, EChartsWidget from FactoryTalk View version 14.00 and Batch View HMI Controls version 2.02 or earlier cannot be used together in the same application; you must upgrade Batch View HMI Controls to version 3.00.
To ensure optimal performance and stability, use the same CEF version for all components within your FactoryTalk View SE application.