FactoryTalk AssetCentre version 13.00.00 (CPR 9 SR 14)

FactoryTalk AssetCentre works within the system requirements of all Rockwell Automation® software products.

Hardware requirements

• For the optimal performance of the FactoryTalk AssetCentre system, we recommend that computers running FactoryTalk AssetCentre Server, FactoryTalk AssetCentre Desktop Client, or FactoryTalk AssetCentre Agent meet or exceed the following hardware requirements.

Type	Description	CPU	Core Processors	RAM
Operator Workstation	FactoryTalk AssetCentre Desktop Client	Intel® Core™ i5 Standard Power processor	2	8 GB
Engineering Workstation	FactoryTalk AssetCentre Desktop Client FactoryTalk AssetCentre Agent	Intel Core i5 Standard Power processor	2	8 GB
System Agent	FactoryTalk AssetCentre Agent	Intel Core i5 Standard Power processor	2	8 GB
Application Server	FactoryTalk AssetCentre Server	Small systems: Intel Core i5 Standard Power processor	2	8 GB
		Medium to large systems: Intel® Xeon® quad-core family processor	4	16 GB

• For the optimal performance of the FactoryTalk AssetCentre system, we recommend that virtual machines running FactoryTalk AssetCentre Server, FactoryTalk AssetCentre Desktop Client, or FactoryTalk AssetCentre Agent meet or exceed the following hardware requirements.

Type	Description	CPU	Core Processors	RAM
Operator Workstation	FactoryTalk AssetCentre Desktop Client	Intel Xeon quad-core family processor	2	8 GB
Engineering Workstation	FactoryTalk AssetCentre Desktop Client FactoryTalk AssetCentre Agent	Intel Xeon quad-core family processor	2	8 GB
System Agent	FactoryTalk AssetCentre Agent	Intel Xeon quad-core family processor	2	8 GB
Application Server	FactoryTalk AssetCentre Server	Small systems: Intel Xeon quad-core family processor	2	8 GB
		Medium to large systems: Intel Xeon quad-core family processor	4	16 GB

• For display resolution, 1024x768 or higher resolution is required.

System size

FactoryTalk AssetCentre is tested based on these system sizes.

Product compatibility

FactoryTalk AssetCentre version 13.00.00 is compatible with the following Rockwell Automation products. For the latest compatibility information, refer to the Rockwell Automation Product Compatibility and Download Center.

FactoryTalk AssetCentre Desktop Client

• To edit the file and data settings for a compare operation, you must have associated software installed on the client computer. To perform archive to archive version compare, you must install the programming software on the client computer.

Asset	Compatible Software	Version
Allen-Bradley® PLC-5® Controller	RSLogix™ 5	10.00 or later
Allen-Bradley SLC™ 500 Controller and Allen-Bradley MicroLogix™ Controller	RSLogix 500®	12.00 or later
ControlLogix® and CompactLogix™	RSLogix 5000®	20.00 or later
	Studio 5000 Logix Designer®	21.00 or later
	RSLogix 5000 Compare Utility or Logix Designer Compare Tool	10.00 or later
FactoryTalk® View Site Edition (SE)	FactoryTalk View Studio Enterprise	14.00 or later
Rockwell Automation drives	DriveExecutive™ Lite	5.02 or later

For more information about the specific drives that FactoryTalk AssetCentre is compatible with, see Knowledgebase Document ID: QA47141 - FactoryTalk AssetCentre RA Motor Control or PowerFlex Drive Device Support.

• FactoryTalk View ME Transfer Utility version 14.00 or later if your system includes Allen-Bradley PanelView Plus and MobileView™ operator interfaces.
• STEP7 version 5.6 sp1 or later if your system includes Siemens® S7 project.

FactoryTalk AssetCentre Agent

• For Disaster Recovery functions, the programming software for your devices MUST be installed on the agent computer.

Asset	Compatible Software	Version
Allen-Bradley PLC-5 Controller	RSLogix 5	10.00 or later
Allen-Bradley SLC 500 Controller and Allen-Bradley MicroLogix Controller	RSLogix 500	12.00 or later
ControlLogix and CompactLogix	RSLogix 5000	20.00 or later
	Studio 5000 Logix Designer	21.00 or later
	RSLogix 5000 Compare Utility or Logix Designer Compare Tool	10.00 or later
Allen-Bradley PanelView Plus Controller and Allen-Bradley MobileView Controller	FactoryTalk View ME Transfer Utility	14.00 or later
	FactoryTalk Linx (formerly known as RSLinx Enterprise)	6.40 or later
FactoryTalk View Site Edition	FactoryTalk View Studio Enterprise	14.00 or later
Rockwell Automation drives	DriveExecutive Lite	5.02 or later
Allen-Bradley PowerFlex® Drive	UDC	15.02 or later
Mitsubishi® Controller	GX Works2™	1.615R
	GX Works3™	1.095Z
Siemens S7 Controller	TIA Portal	15.1, 16, 17, and 18
	STEP7	5.6 sp1 or later

Operating systems

The following tables introduce FactoryTalk AssetCentre’s compatibility with different 64-bit operating systems.

• Turn off the Windows updates on production computers. Installing Microsoft Service Pack release or Windows operating system updates may affect the operation of Rockwell Automation software installed on the computer. To avoid this problem, see Knowledgebase Document ID: QA2151 - Microsoft Patch Qualifications.
• Before you install FactoryTalk AssetCentre on the computer running Windows Server 2012 R2, it is required that you install the following Windows update: Windows Server 2012 R2 update: April 2014.
• FactoryTalk AssetCentre requires .NET 4.8, which is only supported on Windows 10 v1803 and later.

Software requirements

SQL Server database

The following is the SQL Server supported by FactoryTalk AssetCentre.

• Microsoft SQL Server 2019
• Microsoft SQL Server 2022

FactoryTalk AssetCentre Agent

The following are minimum software requirements for FactoryTalk AssetCentre Agent.

• (optional) SIMATIC NET if you want to connect to Siemens S7 Controller (STEP7) via MPI (Multi Point Interface) or PROFIBUS protocol

  It is only required when using Disaster Recovery for Siemens S7 controllers (S7-300/400 with STEP7 software).

• (optional) Siemens TIA Portal software if you want to use Disaster Recovery for Siemens controllers (S7-1200, S71500, and ET200 with TIA Portal software).
• (optional) Mitsubishi GX Works3 software if you want to use Disaster Recovery for Mitsubishi controllers (iQ-F and iQ-R series with GX Works3 software).
• (optional) Mitsubishi GX Works2 software if you want to use Disaster Recovery for Mitsubishi controllers (L, F, and Q series with GX Works2 software).

FactoryTalk AssetCentre Client

The following are minimum software requirements for FactoryTalk AssetCentre Client.

• (optional) Editing software for Siemens S7 Controller (STEP7), such as SIMATIC Manager

  It is only required when using Archive to Archive comparison for Siemens S7 controllers (S7-300/400 with STEP7 software).

Supported browsers

The following web browsers have been tested and are supported for FactoryTalk AssetCentre Web Client and FactoryTalk AssetCentre Help with this release:

• Microsoft® Edge™
• Google® Chrome™ browser
• Mozilla® Firefox®

High Resolution Display Support

Windows 10 v1703 or later is the recommended operating system if running this software with a 2K or 4K High Resolution Display.

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.

Security requirements

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

• Configure System Security Features User Manual (publication SECURE-UM001)
• System Security Design Guidelines Reference Manual (publication SECURE-RM001)
• Converged Plantwide Ethernet (CPwE) Design and Implementation Guide (publication ENET-TD001)

FactoryTalk AssetCentre version 13.00.00 has the following new and enhanced features:

New features

• Third-party disaster recovery support for:
  • Siemens S7-1200, S7-1500, ET 200SP, and ET 200pro controllers programmed with TIA Portal v15.1, v16, v17, and v18
  • Mitsubishi iQ-R and iQ-F controllers programmed with GX Works 3
  • Mitsubishi Q series, L series, and F series controllers programmed with GX Works 2
• Re-imagined Asset Lifecycle capability featuring a summary dashboard, in the FactoryTalk AssetCentre Web Client, that aggregates devices from all inventories in the system.
• Disaster Recovery schedule management added to the FactoryTalk AssetCentre Web Client supports addition, deletion, and modification of schedules and asset tasks.
• Scheduled automatic maintenance of FactoryTalk AssetCentre log table to maintain database performance and size.
• Disaster Recovery for Rockwell Automation devices can use a FactoryTalk Linx Gateway for communications.
• Additional security policies to control access to the FactoryTalk AssetCentre Web Client, and the configuration of system setting.

Enhanced features

• Disaster Recovery for Rockwell Automation supports:
  • FactoryTalk Linx Echo version 3 emulating CompactLogix 5380 and Compact GuardLogix 5380.
  • FactoryTalk View Site Edition v14.00 new Navigation menu and DataLogPro objects.
• Re-organized the Asset Catalog to improve usability.
• Addressed user privacy by removing personal identifiable information from the FactoryTalk AssetCentre address book.

• Management of Change installation fails with the error "Error 27502. Could not connect to Microsoft SQL Server, log in time out expired(0)". The cryptographic algorithm used by FactoryTalk AssetCentre is not supported on computers that have FIPS enabled during the installation. First identified in FactoryTalk AssetCentre version 12.00.00. [Jira 1904162]

  Corrected in FactoryTalk AssetCentre version 13.00.00.

• When upgrading FactoryTalk AssetCentre Server from version 11.00.00 to 12.00.00, if you have removed Port 80 from the Internet Information Services (IIS) configuration in FactoryTalk AssetCentre version 11.00.00 environment before the upgrade, the FactoryTalk AssetCentre installation fails. First identified in FactoryTalk AssetCentre version 11.00.00. [Jira 1935674]

  Corrected in FactoryTalk AssetCentre version 13.00.00.

• If your Microsoft SQL server uses Windows Authentication as the server’s authentication mode and subsequently install FactoryTalk AssetCentre server using a Managed Service Account to access the SQL Server, then the Archive Management of Change capability cannot function properly. First identified in FactoryTalk AssetCentre version 11.00.00. [Jira 1224432]

Corrected in FactoryTalk AssetCentre version 13.00.00.

• When configuring Tag Filter for Backup and Compare schedule for Logix 5000 controller assets, clearing the Include tags that only exist in the right content checkbox doesn't affect the compare options used by FactoryTalk AssetCentre. First identified in FactoryTalk AssetCentre version 11.00.00. [Jira 1936491]

Corrected in FactoryTalk AssetCentre version 13.00.00.

• When running a Disaster Recovery schedule for Allen-Bradley Logix5000 Controller, the compare PDF report cannot be generated to FactoryTalk AssetCentre Desktop Client if no differences are detected. First identified in FactoryTalk AssetCentre version 11.00.00. [Jira 3173223]

Corrected in FactoryTalk AssetCentre version 13.00.00.

• After installing the FactoryTalk AssetCentre, if the FactoryTalk AssetCentre system’s HTTPS port was changed from the default port 443 to a custom port number in the FactoryTalk Administration Console, you may not be able to sign in to the FactoryTalk AssetCentre web client. First identified in FactoryTalk AssetCentre version 12.00.00. [Jira 3284354]
  Corrected in the FactoryTalk AssetCentre version 13.00.00.
  You can refer to the FactoryTalk AssetCentre version 12.00.00 Release Notes: Application notes for the version 12.00.00 workaround.

• If the FactoryTalk AssetCentre server is installed and the WebDavModule is enabled in the Internet Information Services (IIS) Manager on the same computer, the following actions in the FactoryTalk AssetCentre web client cannot be saved:

  • Changes to database limitation settings

  • Changes to database index maintenance properties

  • Changes to or deletion of a scheduled log cleanup task

  First identified in FactoryTalk AssetCentre version 13.00.00 [Jira 3368500].

  Corrected in FactoryTalk AssetCentre version 15.00.00.

  For more information, see FactoryTalk AssetCentre interactions with WebDavModule.

• When running a Source Code Validation schedule for Logix 5000 controllers, a scheduled task may return a false positive due to an anomaly Studio 5000 Logix Designer version 34.00 and version 35.00. First identified in FactoryTalk AssetCentre version 11.00.00. [Jira 2172329]

To resolve this problem, upgrade to Studio 5000 Logix Designer version 36.00 or later.

• When the installation for FactoryTalk AssetCentre Agent is completed, if you close the installation dialog or restart the computer without selecting either the Restart now or Restart later button that appears on the completion page, the Agent Controller will run as a service and log on as “Local System”. However, automatic permission changes that occur when you click Restart now or Restart later are not executed, preventing the Agent’s proper operation. First identified in FactoryTalk AssetCentre 13.00.00. [Jira 3211063]

Corrected in FactoryTalk AssetCentre version 15.00.00.

• After running a Backup and Compare schedule for Logix 5000 controller assets successfully, the compare PDF report cannot be generated and opened successfully if the PDF file size is extremely large, such as 8000 pages. First identified in FactoryTalk AssetCentre version 12.00.00. [Jira 1885002]

Corrected in FactoryTalk AssetCentre version 16.00.00.

• After installing FactoryTalk AssetCentre Server version 12.00.00 or later, if the FactoryTalk AssetCentre Server computer’s FactoryTalk Directory location is changed, the FactoryTalk AssetCentre system cannot function properly. First identified in FactoryTalk AssetCentre version 12.00.00. [Jira 2246229]

To avoid this problem, do the following for FactoryTalk AssetCentre Server version 13.00.00 or later:

1. On the FactoryTalk AssetCentre Server computer, select Start > Rockwell Software > FactoryTalk AssetCentre Server Settings.

2. In the Configure Server Settings Utility window, configure Server Location - that is the fully qualified domain name (FQDN) of the FactoryTalk AssetCentre.

3. Select or clear Use the secure communication channel.

4. Configure IIS Server Communication port.

   • When Use the secure communication channel is selected, by default the port number is set as 443. Please ensure that port 443 is not used by other applications.

   When customizing the IIS Server Communication port, please take note that if your AssetCentre system includes the Management of Change capability, it is required to use port 443.

   • When Use the secure communication channel is not selected, the port number is set as 80.

To avoid this problem, do the following for FactoryTalk AssetCentre Server version 12.00.00:

1. On the FactoryTalk AssetCentre Server computer, select Start > Rockwell Software > Server Settings.

2. In the Configure Server Settings Utility window, configure Server Location - that is the fully qualified domain name (FQDN) of the FactoryTalk AssetCentre.

3. Configure Use the secure communication channel - that is the communication between the server, client(s), and agent(s) encrypted using the TLS protocol.

   • When Use the secure communication channel is selected, the IIS Server is configured to use port 443.

   • When Use the secure communication channel is not selected, the IIS Server is configured to use port 80.

   • When customizing the communication port using IIS Manager, you must do the following to specify the port in Primary Server Web Services Base URL.

     1. Select Start > Rockwell Software > FactoryTalk Administration Console.

     2. Navigate to Network > System > Policies > Product Policies > FactoryTalk AssetCentre, and the double-click Server Settings.

     3. In the Server Settings Properties dialog, select Primary Server Web Services Base URL, and then append the port number following a colon to the web server FQDN in the form as https://<FactoryTalk AssetCentre Server FQDN>:<custom port>/RockwellSoftware/AssetCentre.

        When customizing the IIS Server Communication port, please take note that if your AssetCentre system includes the Management of Change capability, it is required to use port 443.

• A disaster recovery task for an Asset Inventory asset configured to scan a network using SNMP does not detect and add Siemens devices to the inventory (.RAAI) file. First identified in FactoryTalk AssetCentre version 13.00.00. [Jira 2336140]

There is currently no workaround for this anomaly.

• When the FactoryTalk AssetCentre Server activation expires or reaches the expiration warning threshold, no notification is shown to the user each time the FactoryTalk AssetCentre Web Client opens. First identified in FactoryTalk AssetCentre version 13.00.00. [Jira 2332699]

To see the expiration information, open FactoryTalk Activation Manager from Start > Rockwell Software, and then select Find Available Activations.

• When attempting a Secure Shell (SSH) connection to backup a Stratix Switch running IOS XE 17.10 and later, FactoryTalk AssetCentre encounters a "No Matching MAC Found" error. First identified in FactoryTalk AssetCentre version 13.00.00. [Jira 2129821]

Corrected in FactoryTalk AssetCentre version 15.00.00.

• When cleaning the Diagnostic and Health log, if the system is configured to export records to an external database, the resulting backup database contains no records, the export fails. First identified in FactoryTalk AssetCentre version 13.00.00. [Jira 3129967]

Corrected in FactoryTalk AssetCentre version 15.00.00.

• The following applications do not support Azure AD or OpenID Connect sign-in: FactoryTalk AssetCentre Log Cleanup utility, FactoryTalk AssetCentre Archive Cleanup utility, and the Source Control plug-in found in Studio 5000 Logix Designer, RSLogix 5000, RSLogix 5, and RSLogix 500. First identified in FactoryTalk AssetCentre version 13.00.00. [Jira 3171134]

There is no workaround for this anomaly.

From FactoryTalk AssetCentre version 15.00.00, FactoryTalk AssetCentre Log Cleanup utility and FactoryTalk AssetCentre Archive Cleanup utility support Azure AD or OpenID Connect sign-in.

• FactoryTalk AssetCentre cannot backup an Allen-Bradley E300 Overload Relay when the device is communicated with a controller using a Class 1 CIP connection. First identified in version 13.00.00. [Jira 1825589]

There is no workaround for this anomaly.

• Disaster recovery tasks for the Allen-Bradley Logix 5000 Controller, Allen-Bradley PLC-5 Controller, Allen-Bradley SLC 500 Controller, and Allen-Bradley MicroLogix Controller failed with the error “could not set security token”. First identified in FactoryTalk AssetCentre version 13.00.00. [Jira 3209566]

To resolve this problem, run FactoryTalk AssetCentre Agent Controller Launch Control Panel from Start > Rockwell Software, and then select Repair.

• If a scheduled task execution exceeds the VerificationAgentTimeout value that is set in the registry editor (the default value is 120 minutes), the system cannot stop FactoryTalk AssetCentre AgentController service with the error “Could not stop service. Access is denied” and the scheduled task in FactoryTalk AssetCentre continues to execute when the AgentController service is running using NetworkService. NetworkService lacks the necessary operating system permissions to stop other services. First identified in FactoryTalk AssetCentre version 13.00.00. [Jira 3195877]

To resolve this problem, do either of the following:

• Run FactoryTalk AsseCentre Agent Controller Launch Control Panel from Start > Rockwell Software, and then specify a Windows user account with administrative user permission to run it as an application. This requires that the computer be restarted.

• Stop the VerificationAgent from the task manager.

• When performing a disaster recovery schedule for FactoryTalk Directory or FactoryTalk View Site Edition, simultaneously running a disaster recovery schedule for assets that use the VerificationAgent service might cause errors with the messages "Error: could not load agent" and "Error: could not load Verification agent". First identified in FactoryTalk AssetCentre version 13.00.00. [Jira 3148107]

Assets that use the VerificationAgent service to run disaster recovery schedules include Allen-Bradley Logix 5000 Controller, Allen-Bradley PanelView, Allen-Bradley PanelView Plus, Allen-Bradley MobileView, Allen-Bradley MicroLogix Controller, Allen-Bradley PLC-5, and Allen-Bradley SLC 500 Controller.

To avoid this problem, adjust the time intervals between disaster recovery schedules for FactoryTalk Directory or FactoryTalk View Site Edition and disaster recovery schedules for assets that use the VerificationAgent service to prevent overlap. The interval duration depends on the size of the system, larger systems generally require longer intervals.

• If the FactoryTalk AssetCentre Client is installed in a non-system hard drive, comparing files using the archive to archive comparison fails. First identified in FactoryTalk AssetCentre version 13.00.00. [Jira 3221658]

To resolve this problem, do the following:

1. Open Tools > Options, and then select Compare Engines.

2. Select WinMerge.

3. Specify the path of Application to the installation path of the FactoryTalk AssetCentre Client.

• If the FactoryTalk AssetCentre AgentController runs as an application using a Windows user account with a username that exceeds eight characters, performing Disaster Recovery tasks for Siemens S7 Controller TIA Portal V16 or TIA Portal V15.1 fails with the error "TIA Portal error occurred during task execution (0x0019)". First identified in FactoryTalk AssetCentre version 13.00.00. [Jira 3426416]

Corrected in FactoryTalk AssetCentre version 15.00.00.

• When performing Mitsubishi GX Works2 disaster recovery tasks, those tasks will fail if the FactoryTalk AssetCentre agent computer's Ethernet adapter is not the same Ethernet adapter specified with the Mitsubishi project file. This is a Mitsubishi GX Works2 automation interface limitation. First identified in FactoryTalk AssetCentre version 13.00.00. [Jira 3238860]

To resolve this problem, do the following on the FactoryTalk AssetCentre agent computer from which you want to perform Mitsubishi GX Works2 disaster recovery tasks:

1. Open the GXW project file, and then open the PC side I/F Ethernet Board Setting.

2. Change Adapter from Not Specified to the agent computer’s Ethernet adapter, and then select OK.

3. Save the GXW project file.

4. In FactoryTalk AssetCentre, open the Mitsubishi Controller (GX Works2) asset property, and add the updated GXW project file to the Backup Data field.

IMPORTANT: You must execute Mitsubishi GX Works2 disaster recovery tasks on the agent computer from which you specified the GXW project file’s Ethernet Board. It is recommended to use Agent Groups to restrict Mitsubishi GX Works2 disaster recovery tasks to FactoryTalk AssetCentre agent computer that meets the Mitsubishi GX Works automation interface requirements for matching Ethernet adapters.

• If you attempt to configure the FactoryTalk AssetCentre Agent Controller to "Run As" an application using a Windows user account whose name contains braces ({}), the agent will not be properly configured.

  • Specifying the Windows user account name during the interactive or silent installation process:

  • The account name will display incorrectly in the FactoryTalk AssetCentre Agent Controller Launch Control Panel application.

  • The Repair permissions function fails with the error: "Input string was not in correct format."

  • Permissions for the specified user account cannot be configured successfully, and the agent will not operate successfully.

  • Specifying the Windows user account name using the FactoryTalk AssetCentre Agent Controller Launch Control Panel application:

    • The Repair permissions function fails with the error: "Input string was not in correct format."

    • Permissions for the specified user account cannot be configured successfully, and the agent will not operate successfully.

  First identified in FactoryTalk AssetCentre version 13.00.00. [Jira 4080151]

  Corrected in FactoryTalk AssetCentre version 15.00.01.

  To resolve these problems, do not use braces {} in the Windows user account name used to run the FactoryTalk AssetCentre agent, or upgrade FactoryTalk AssetCentre to version 15.00.01 or later, and apply the latest Rockwell Automation monthly Patch Roll-up.

• FactoryTalk AssetCentre web client may remain on the sign-in page after providing user credentials. This problem occurs because the size of the user’s authorization token exceeds the browser’s maximum supported cookie size of 4,096 bytes. First identified in FactoryTalk AssetCentre version 13.00.00. [Jira 5189634]

  To resolve this problem, install Patch: Web client fails to sign in, FactoryTalk AssetCentre 13.0, 15.0, 16.0, which breaks large authorization tokens into multiple cookies. The combined cookie size cannot exceed 16,384 bytes.

  In rare cases, the browser may return a "Bad Request – Request Too Long (HTTP Error 400)" error when the user’s authorization token size is close to the 16,384 byte limit. If this occurs, reduce the number of FactoryTalk groups the affected user account belongs to in the FactoryTalk Directory.

• If AssetCentre system databases are moved between domain locations, Manage of Change workflow does not work. There are two scenarios:

  Scenario one: When AssetCentre system databases are stored in domain A, if you backup the database in domain A and restore the database in domain B, Management of Change workflow does not work because domain B cannot identify the correct user.

  Scenario two: When AssetCentre system databases are in a Windows work group, if you backup the database in the work group and restore the database in domain B, Manage of Change workflow does not work because domain B cannot identify the correct user.

  First identified in FactoryTalk AssetCentre version 12.00.00. [Jira 1934291]

  To avoid this problem:

  1. In the current location, perform a database backup of the AssetCentre system databases, both: AssetCentre and Llumin_dB.

  2. In the new location, perform a database restore of the AssetCentre system databases, both AssetCentre and Llumin_dB.

  3. Proceed with the AssetCentre Server installation.

• When running a Source Code Validation schedule containing a controller whose firmware has been updated from version 34 to version 35 or later, the Source Code Validation schedule task will run successfully but the task’s result is invalid. First identified in FactoryTalk AssetCentre version 11.00.00. [Jira 1648178]

To avoid this problem, re-browse the controller’s Asset Tree Address Information property after applying the controller’s firmware update; run the Source Code Validation schedule again.

• When executing a search using Run Now from the FactoryTalk AssetCentre Web Client, if the search results contain more than 2,000 rows (approximately 200 pages), the PDF report will only show the first 2,000 rows. First identified in FactoryTalk AssetCentre version 12.00.00 [Jira 1877940]

  To avoid this problem, use FactoryTalk AssetCentre desktop client, or change the search parameters to return fewer rows of information.

• When a Disaster Recovery schedule contains a PowerFlex 755TR Drive, the drive’s disaster recovery task fails. First identified in FactoryTalk AssetCentre version 12.00.00. [Jira 1769829]

  To avoid this problem, use the latest drive firmware.

• When restarting services that were stopped for more than 30 minutes, some functions of FactoryTalk AssetCentre might fail. There are three scenarios:

  • Scenario one: When restarting the SQL Server service, the schedule function fails with the error "No Schedules have been created".

  • Scenario two: When restarting the SQL Server service, the Agent Groups function fails with the error "RockwellAutomation.FTAssetCentre.Aos.ReloadingAssetsException".

  • Scenario three: When restarting the World Wide Web publishing service, the Audit Log and Diagnostics and Health Log functions fail with the error "Cannot display data.Application in disconnected mode."

    First identified in FactoryTalk AssetCentre version 9.00.00. [Jira 1767030]

  To avoid this problem, do the following for each scenario:

  • Scenario one: Close the Schedule tab, and then reopen it.

  • Scenario two: Close the Agent Groups tab, and then reopen it.

  • Scenario three: Close the Audit Log tab or the Diagnostics and Health Log tab, and then reopen it.

• When the Device Monitor schedule is active, if you change the value of Copy Controller Log to Audit, for example from Ture to False, and then save the changes, the Copy Controller Log to Audit function fails. First identified in FactoryTalk AssetCentre version 12.00.00 [Jira 1924996]

  To avoid this problem, first deactivate the schedule by clearing the Active checkbox, and then reactivate the schedule.

• When upgrading FactoryTalk AssetCentre from version 11.00.00 or later, the Disaster Recovery tasks for PowerFlex assets fail. First identified in FactoryTalk AssetCentre version 11.00.00 [Jira 1913507]

To avoid this problem, re-browse the addressing information for assets.

• The remote FactoryTalk Agent cannot register to the Server successfully because the firewall is blocking the AgentController service. First identified in FactoryTalk AssetCentre version 12.00.00. [Jira 1807445]

  To avoid this problem, do one of the following:

  • Configure the firewall to permit traffic on the AgentController service.

  • Run Windows Firewall Configuration Utility manually.

• When running a Backup and Compare schedule with a large ControlLogix project, the schedule may fail because the Logix Designer Compare Tool runs out of memory. First identified in FactoryTalk AssetCentre version 9.00.00. [Jira 1552204]

  To avoid this problem, do the following:

  1. Open Logix Designer Compare Tool, select Memory Saver. Make sure that Enable Save is selected before selecting Memory Saver.

  2. Run the schedule again.

• If the Asset Inventory CIP scan contains more than 15,000 devices, the Backup and Compare schedule fails. First identified in FactoryTalk AssetCentre version 12.00.00 [Jira 1913506]

  Corrected in FactoryTalk AssetCentre version 16.00.00.

• When performing a FactoryTalk Directory or FactoryTalk View Site Edition backup, the FactoryTalk Directory is locked by design, and this may prevent the FactoryTalk AssetCentre Server from accessing a remote FactoryTalk Directory Server. As a result of the connection, between the FactoryTalk AssetCentre Server and FactoryTalk Directory, FactoryTalk AssetCentre Agents will disconnect from the FactoryTalk AssetCentre Server during the backup task execution. First identified in FactoryTalk AssetCentre version 12.00.00. [Jira 1943618]

  Once the backup task completes, the affected connections will automatically restore.

• When performing an Asset Inventory WMI to scan the software, with the Changes only option selected, the scan can not detect installation changes for applications that do not maintain installation information (for example, you uninstall the software today and then install it on another day). First identified in FactoryTalk AssetCentre version 7.00.00.[358777]

  There is currently no work around for this anomaly.

• Cannot modify or uninstall the software FactoryTalk AssetCentre Client or FactoryTalk AssetCentre Agent application by double-clicking Setup.exe in the installation package and selecting AssetCentre Custom Installation. First identified in FactoryTalk AssetCentre version 8.00.00. [46429]

  To modify or uninstall the software components, go to the Programs and Features list of the Control Panel.

• When configuring a PanelView asset's Addressing Info, if a device other than a PanelView is selected, several extraneous error messages may display. First identified in FactoryTalk AssetCentre version 9.00.00. [Jira 242271]

  To avoid this problem, choose the proper device type when configuring the Addressing Info of a PanelView asset.

• A PanelView Plus or MobileView Disaster Recovery schedule will fail with a communication error message, if the Address Info is not set for the device using FactoryTalk Linx Browser located on the FactoryTalk AssetCentre agent computer. First identified in FactoryTalk AssetCentre version 10.00.00. [Jira 395652]

  To avoid this problem, after configuring the Addressing Info property of a PanelView Plus asset or a MobileView asset, the user must browse for the device in FactoryTalk Linx Browser from the FactoryTalk AssetCentre agent computer when the agent computer is not collocated with the FactoryTalk AssetCentre client.

• After upgrading FactoryTalk AssetCentre from a previous version to the latest version, in some scenarios, the cached log cannot be written because SQL Server LocalDB is non-functional. First identified in FactoryTalk AssetCentre version 12.00.00. [Jira 1932900]

To avoid this problem:

1. Open Registry Editor, and find the CLSID within the following registry key:

HKEY_USERS\DEFAULT\SOFTWARE\Microsoft\Microsoft SQL Server\UserInstances



2. Modify the String Value ParentInstance according to the version that you want to upgrade. For example, after you upgrade from version 12.00.00 to version 13.00.00, modify it from MSSQL15E.LOCALDB to MSSQL16E.LOCALDB.

3. Restart the computer.

The following table provides the registry keys of the FactoryTalk AssetCentre versions.

FactoryTalk AssetCentre Version	LocalDB Version	Registry Keys
V13.00.00, V15.00.00, V16.00.00	Microsoft SQL Server 2022 LocalDB	MSSQL16E.LOCALDB
V12.00.00	Microsoft SQL Server 2019 LocalDB	MSSQL15E.LOCALDB
V9.00.00, V10.00.00, V11.00.00	Microsoft SQL Server 2014 Express LocalDB	MSSQL12E.LOCALDB

 

• When the Report Incremental Differences option is enabled for a Logix 5000 controller asset within a Disaster Recovery schedule, the task will fail if the controller firmware version does not match the firmware version of the ACD file associated with the Incremental Checkpoint label. First identified in FactoryTalk AssetCentre version 10.00.00. [Jira 806906]

  To avoid this problem, you can do the following steps:

  1. After upgrading or downgrading a Logix 5000 controller’s firmware, open the FactoryTalk AssetCentre archive to check in the ACD file that matches Logix 5000 controller firmware version.

  2. Select Add Label to move the Incremental Checkpoint, and then select the Allow reuse of existing labels check box.

  3. In the Label box, enter the label name exactly as Incremental Checkpoint.

     The Disaster and Recovery schedule will now run successfully.

• FactoryTalk AssetCentre has limited support for 4K displays, when display scaling is greater than 100%. First identified in FactoryTalk AssetCentre version 10.00.00. [Jira 355367]

  To avoid this problem, set the display scaling to 100% and restart the computer.

• When uninstalling FactoryTalk AssetCentre Agent, FactoryTalk AssetCentre Agent will remain in the Control Panel, Add/Remove until all supporting applications (for example, RSLogix 500) are also removed. First identified in FactoryTalk AssetCentre version 10.00.00. [Jira 488955]

  To resolve this problem, uninstall all software installed together with FactoryTalk AssetCentre Agent 10.00.00 installation and then it will be removed.

• When repairing a FactoryTalk AssetCentre Agent installation on a computer upon which Logix Designer Compare Tool is not installed, FactoryTalk AssetCentre will generate a nuisance warning message indicating that Logix Designer Compare Tool requires that Microsoft .NET Framework 3.5 to be installed. First identified in FactoryTalk AssetCentre version 10.00.00. [Jira 566002]

  This issue currently has no workaround. The behavior does not adversely impact the FactoryTalk AssetCentre Agent installation repair process.

• When updating an earlier version FactoryTalk AssetCentre Server with SSL enabled to version 11.00.00, failure to restart the computer using either the Restart Now or Restart Later in the installation user interface, prevents the FactoryTalk AssetCentre Client from launching. First identified in FactoryTalk AssetCentre version 11.00.00. [Jira 1046534]

  To resolve this problem, you can do the following steps:

  1. Open the Server Settings utility.

  2. In the Configure Server Settings Utility window, clear the Use the secure communication channel check box, and then select the Apply button.

  3. Reselect the Use the secure communication channel check box, and then select the Apply button.

  4. Select OK.

• When performing Archive version to version compare of a DNO file associated with a PowerFlex 755, an error message appears. First identified in FactoryTalk AssetCentre version 9.00.00. [Jira 1285794]

  To resolve this problem, do the following:

  1. Using the FactoryTalk AssetCentre Client, check out and open the DNO file.

  2. Go online with the target PowerFlex 755 device.

  3. Close the DNO file, and check in the DNO file.

• When using the silent or unattended setup to upgrade FactoryTalk AssetCentre version 8.00.00 or later, if any of the additional software components’ version (for example, Logix Designer Compare Tool) on the computer is equal to or higher than the version you will upgrade to, the upgrade will fail. First identified in FactoryTalk AssetCentre version 11.00.00. [Jira 1444198]

  To avoid this problem, you can do one of the following:

  • Upgrade FactoryTalk AssetCentre version 8.00.00 or later using the Setup wizard.

  • Enter /IgnoreWarning when upgrading FactoryTalk AssetCentre version 8.00.00 or later using the silent or unattended setup.

    Example:

    C:\Users\Administrator\Desktop\11.00.00-FTAssetCentre-DVDD\Setup.exe /Q /IAcceptAllLicenseTerms /AutoRestart /SetupLanguage=ENU /Product="AssetCentre Server" /SerialNumber=2740J00396 /ProductKey=RYN62-LWBQ6 /Version=11.00.00 /InstallDrive=D: /SqlServer="(local)" /DirectoryServer=FTDIRECTORY/ IgnoreWarning

• When a large binder, more than 1GB in total size, is being promoted in the Archive, running an Archive Check In and Check Out Status search schedule will fail. Once the promotion is completed the schedule can be executed successfully. First identified in FactoryTalk AssetCentre version 9.00.00. [Jira 1309942]

  There is currently no workaround for this anomaly.

• If running the FactoryTalk AssetCentre Client on Windows 10 version 1903, when opening a PowerFlex drive Backup & Compare comparison report (CSV file) in the Event Log, an error message appears. Please note Windows 10 version 1903 reached Microsoft End of Service on 8.Dec.2020. First identified in FactoryTalk AssetCentre version 10.00.00. [Jira 1285815]

  To avoid this problem, configure the default application to open the CSV file via the operating system Settings > Apps > Default apps. Notepad.exe is recommended

• The Agent Groups function fails with the error "RockwellAutomation.FTAssetCentre.AosReloadingAssetsException" in any of these scenarios:

  • When the network cable has been disconnected from the FactoryTalk AssetCentre Server computer for more than ten minutes, and then reconnecting it.

  • When the Default Web Site has been stopped for the FactoryTalk AssetCentre Server computer for more than ten minutes, and then restarting it.

  • When the World Wide Web Publishing service has been stopped for more than ten minutes, and then restarting it.

First identified in FactoryTalk AssetCentre version 12.00.00. [Jira 1933027]

To avoid this problem, close the Agent Groups tab, and then reopen it.

• When a user is denied the Configure Personal Archive Working Folder permission, performing an archive-to-archive comparison in the FactoryTalk AssetCentre desktop client in any of the following scenarios fails with a misleading error message: “Compare target not found. Unable to locate file at the specified working folder”.

  • Comparing two files within the FactoryTalk AssetCentre desktop client.

  • Comparing one file within the FactoryTalk AssetCentre desktop client and one file outside of it.

  First identified in FactoryTalk AssetCentre version 12.00.00. [Jira 5074188]

  Corrected in FactoryTalk AssetCentre version 16.00.00.

FactoryTalk AssetCentre version 13.00.00 has the following changes in functionality since the last release.

Remove Agent Service Logon Configuration tool

Beginning with FactoryTalk AssetCentre version 13.00.00, the Agent Service Logon Configuration tool is removed. From FactoryTalk AssetCentre version 13.00.00, you can use the FactoryTalk AssetCentre Agent Controller Launch Control Panel to grant the necessary permissions for Disaster Recovery operations.

Folder location change

FactoryTalk AssetCentre version 13.00 changes the following folder location:

• AssetCentre Inventory Crawler Log: Move from C:\Program File (x86)\Rockwell Software\AssetCentre Inventory Crawler\Log to C:\ProgramData\Rockwell\AssetCentre\AssetCentre Inventory Crawler\Log
• Trace Diagnostics Log: Move from C:\Program File (x86)\Common Files\Rockwell\TraceDiagnostics\Log to C:\Users\Public\RockwellSoftware\TraceDiagnostics\Log

Change in Address Book

Beginning with FactoryTalk AssetCentre version 13.00.00, personally identifiable information, such as phone number and street address, has been removed from the Address Book. When upgrading FactoryTalk AssetCentre to version 13.00.00, any personally identifiable information entered will be cleared in its entirety.

The following are the application notes for FactoryTalk AssetCentre version 13.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 AssetCentre 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.

Disaster Recovery schedule tasks fail with Device Not Found recorded in the FactoryTalk AssetCentre Event log

When a Logix controller asset’s Addressing property is configured using RSLinx Classic, Disaster Recovery schedule tasks may start failing with Device Not Found recorded in the FactoryTalk AssetCentre Event log. Rebooting the FactoryTalk AssetCentre Agent(s) will temporarily address the error, however, the task failures will eventually return. This behavior is addressed in an RSLinx Classic patch. See technote BF27867 for additional details.

Full OS backup

Rockwell Automation does not test any third-party software to perform the full Windows operating system backup, for example, Veritas Backup Exec. When performing a computer backup on a running virtualized system, it is recommended the system is stopped before performing a backup.

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 AssetCentre version 13.00.00 has been assessed against CIS Microsoft Windows 10 Enterprise Benchmark v2.0.0 (L1), CIS Microsoft Windows Server 2019 Benchmark v2.0.0 (L1), CIS Microsoft Windows 11 Enterprise Benchmark v2.0.0 (L1), and CIS Microsoft Windows Server 2022 Benchmark v2.0.0 (L1).

The exceptions for FactoryTalk AssetCentre version 13.00.00 are listed.

CIS Microsoft Windows 10 Enterprise Benchmark v2.0.0 (L1)

• 2.2.2 (L1) Ensure 'Access this computer from the network' is set to 'Administrators, Remote Desktop Users'

Only applies to FactoryTalk AssetCentre Agent - Allows the FactoryTalk AssetCentre Agent to register with the Server requires Managed Service Accounts be added to the policy

CIS Microsoft Windows Server 2019 Benchmark v2.0.0 (L1)

• 2.3.11.4 (L1) Ensure 'Network security: Configure encryption types allowed for Kerberos' is set to 'AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types'

Only applies to FactoryTalk AssetCentre Server - When the FactoryTalk AssetCentre Server is using a gMSA user the policy required AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types must be unchecked

Run the command "Set-ADServiceAccount -Identity gMSAUser -KerberosEncryptionType AES128,AES256" on the domain controller to enable the policy and allow the system to work

CIS Microsoft Windows 11 Enterprise Benchmark v2.0.0 (L1)

• 2.2.2 (L1) Ensure 'Access this computer from the network' is set to 'Administrators, Remote Desktop Users'

Only applies to FactoryTalk AssetCentre Agent - Allows the FactoryTalk AssetCentre Agent to register with the Server requires Managed Service Accounts be added to the policy

CIS Microsoft Windows Server 2022 Benchmark v2.0.0 (L1)

• 2.3.11.4 (L1) Ensure 'Network security: Configure encryption types allowed for Kerberos' is set to 'AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types'

Only applies to FactoryTalk AssetCentre Server - When the FactoryTalk AssetCentre Server is using a gMSA user the policy required AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types must be unchecked

Run the command "Set-ADServiceAccount -Identity gMSAUser -KerberosEncryptionType AES128,AES256" on the domain controller to enable the policy and allow the system to work

Secure communication with TLS and SSL protocols

Windows implements SSL and TLS through S-channel Security Support Provider (SSP). The S-channel SSP implementation of the TLS and SSL protocols uses algorithms from a cipher suite to create keys and encryption information. Starting from FactoryTalk AssetCentre version 9.00, the operating system's capability is used to automatically filter out the unsecure ciphers.

• For all cipher suites listed for different operating systems, refer to Cipher Suites in TLS/SSL (S-channel SSP).

• If you have a preference on the cipher suites and need to customize the priorities in group policy, refer to Prioritizing S-channel Cipher Suites.

• To enable or disable specific ciphers in the registry, refer to How to restrict the use of certain cryptographic algorithms and protocols in Schannel.dll.

Configure certificates for a remote FactoryTalk Network Directory when TLS is enabled

If your FactoryTalk Network Directory server and FactoryTalk AssetCentre server are installed on different computers and secure communications (TLS) are being used, the FactoryTalk Network Directory Web Authentication server requires a certificate for authenticating the FactoryTalk AssetCentre web client. You must configure a certificate authority (CA) issued, or a self-signed, certificate for the FactoryTalk Network Directory server so that the FactoryTalk AssetCentre web client can be used successfully. 

For instructions related to using a certificate authority (CA) issued certificate on the FactoryTalk Network Directory server, see the FactoryTalk AssetCentre Installation Guide:

-Configure the TLS protocol for FactoryTalk AssetCentre

For instructions related to using a self-signed certificate on the FactoryTalk Network Directory server, see the following topics in the FactoryTalk AssetCentre Installation Guide:

-Create a self-signed TLS certificate on the SQL Server or FactoryTalk Network Directory computer

-Configure the HTTPS site binding

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.

Unattended or silent install

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

IMPORTANT: When installing or upgrading FactoryTalk AssetCentre to version 11.00.00 or later with SQL Server Authentication, you must use silent or unattended setup to install it.

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

Error codes

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

FactoryTalk AssetCentre Client

• All FactoryTalk AssetCentre clients must have identical RSLinx Classic communication driver configurations.

• When performing backups or backup and compares on Generic FTP devices containing subdirectories, the FTP device must support both the "DIR" and "ls" commands.

• To verify, use the Command Line Prompt to sign in to the FTP device. Once logged in, type DIR and press Enter, and then type ls and press Enter. You should see the same results for each command issued.

• Disaster Recovery for Rockwell Automation devices supports the use of the DNS feature in FactoryTalk Linx for communications. However, the Allen-Bradley PanelView Plus and Allen-Bradley MobileView devices cannot use the DNS feature in FactoryTalk Linx.

• After upgrading a previous version of FactoryTalk AssetCentre to version 13.00.00, you must manually clear your browser’s cache to make sure that you can successfully sign in to FactoryTalk AssetCentre Web Client.

• The file password function in Mitsubishi GX Works3 is used to help prevent files in a controller from being accessed by unauthorized users. Using Mitsubishi GX Works3, you can set passwords to limit access to different types of data in a controller. However, FactoryTalk AssetCentre v13.00.00 only supports specifying a single password in the Password File Access field when configuring a Mitsubishi Controller (GX Works3) asset. When a Mitsubishi GX Works3 controller is password-protected, you must configure the same password for all types of data in the Mitsubishi GX Works3 project to allow FactoryTalk AssetCentre to successfully perform a Mitsubishi Controller (GX Works3) Disaster Recovery task.

• The Mitsubishi Controller (GX Works2) does not support the remote password and file password capability for Disaster Recovery schedules.

FactoryTalk AssetCentre Agent

• The agent installation now provides the ability to create and set security credentials needed for secured Logix editors.

  NOTE: This configuration step can be skipped during installation. If skipped, you may configure it manually later. For details, see the Installation Guide, chapter "Install FactoryTalk AssetCentre agents", section "Configure for security-enabled RSLogix family software".

• If you enable the security option for RSLogix 5, which is used by the FactoryTalk AssetCentre Recovery agent, you must install a service patch.

  For details, see Knowledgebase Document ID: BF20056 - RSLogix 5 7.x Patch for comms path getting erased, which breaks FactoryTalk AssetCentre.

• If you enable the security option for RSLogix 500 using version 8.00 or earlier, which is used by the FactoryTalk AssetCentre Disaster Recovery agent, you must install a service patch.

  For details, see Knowledgebase Document ID: BF20057 - RSLogix 500 7.20/8.00 Patch for comms path getting erased, which breaks FactoryTalk AssetCentre.

• FactoryTalk AssetCentre agents belonging to the same agent group must meet the following requirements:

  • Have identical RSLinx Classic and FactoryTalk Linx (formerly known as RSLinx Enterprise) communication driver configurations.

  • Be able to communicate with all assets configured for use with that agent group.

  • Have all programming software products installed that are required by the assets configured for use with that agent group.

    For example, if an agent group supports both SLC 500 and Logix 5000 controllers, then each agent belonging to that agent group must have both RSLogix 500 and the appropriate version of RSLogix 5000 or Logix Designer installed.

• For Siemens TIA Portal, Mitsubishi GX Works2, and GX Works3, FIPS must be disabled for communication to work properly.

• In a Windows domain environment, when the FactoryTalk AssetCentre AgentController runs as an application, it is critical to select a standard Windows domain user account. This allows Microsoft Windows Communication Foundation (WCF) to authenticate between the FactoryTalk AssetCentre agent to connect to the FactoryTalk AssetCentre server. If the AgentController is configured to use a local Windows user account, then WCF won’t work correctly and the FactoryTalk AssetCentre agent won’t be able to connect to the server.

The number of clients, agents, and agent groups qualified within one FactoryTalk AssetCentre system

The following is the number of clients, agents, and agent groups qualified within one FactoryTalk AssetCentre system at the same time. More clients, agents, or agent groups running will impact the system performance. The system cannot exceed 50 agents total. For example, a system could have 50 agent groups each with one agent member.

• Desktop client: 150

• Web client: 200

• Agent: 50

• Agent groups: 50

Ensuring consistent domain credentials for FactoryTalk AssetCentre desktop and web clients

In a Windows domain environment, signing in to the FactoryTalk AssetCentre desktop and web clients using the Windows domain user account without the domain name can result in file check-in failures on the web client, even though file check-out on desktop clients works. This happens because the web client handles authentication requests remotely. When the domain name is omitted, Windows automatically selects an authentication method, recognizing the user as a local account rather than a domain account. This causes authentication inconsistencies between the desktop and web clients.

To avoid this problem, sign in using domain\username on both desktop and web clients.

Considerations for generating large PDF reports

Generating very large PDF reports may result in generation failures, incomplete report content, or reports that cannot be opened. Common factors that can affect large PDF report generation include:

• System resources and environment

  Available memory and system conditions can affect the successful generation of large reports.

• Content complexity

  Reports that contain significant differences between versions or a large number of tags require additional processing resources.

To help avoid problems when generating large PDF reports:

• Upgrade to FactoryTalk AssetCentre version 16.00.00 or later.

• For large Logix 5000 compare reports, consider clearing the All Tag Values option in the Compare Options dialog.

• If an asset inventory scan fails because of a large number of changes, run a backup task to establish a new baseline.

Synchronizing lifecycle information with the Rockwell Automation lifecycle website

Lifecycle information can be used to develop hardware device migration plans, or to find devices that require firmware updates. To retrieve the lifecycle information of your Rockwell Automation devices from the Product Compatibility and Download Center (PCDC), perform one of the following methods:

Use a Forward Proxy Server

It is recommended to use a forward proxy server to communicate lifecycle information between the FactoryTalk AssetCentre Server and the PCDC because it provides a more secure connection than configuring firewall access. The forward proxy server must be accessible from the iDMZ and from the FactoryTalk AssetCentre server to access the PCDC.

In the FactoryTalk AssetCentre Server, configure the forward proxy for device lifecycle using FactoryTalk AssetCentre Server Settings. Enter a FactoryTalk administrator's credentials to log in.

In FactoryTalk AssetCentre Server Settings, to enable the forward proxy server, select the checkbox next to Use the forward proxy. In the dialogs, enter the IP address and port number used by your forward proxy server to communicate lifecycle information between the FactoryTalk AssetCentre server and the PCDC. Once this information is entered, select OK. Be sure to restart your computer to ensure the settings take effect.

For the forward proxy server, there are many types and styles of software available. Each proxy server will have different methods and settings. Ensure that the forward proxy server has the web domain https://api.rockwellautomation.com added to the allowed web domain list.

Configure firewall access

Use the following information to configure firewall access to retrieve the lifecycle statuses from the PCDC.

• PCDC URL: api.rockwellautomation.com

• TLS port: 443

• IP addresses: 52.xxx.xxx.xxx - 34.xxx.xxx.xxx

One size does not fit all when it comes to risk tolerance. Please refer to Rockwell Automation's Converged Plantwide Ethernet document for more information about configuring a scalable plant-wide security architecture.

Database mirroring fails when the communication between FactoryTalk AssetCentre and Microsoft SQL Server is encrypted using TLS

FactoryTalk AssetCentre supports database mirroring through the FactoryTalk AssetCentre Data Source Configuration Wizard to improve SQL Server availability.

If both Secure communications using TLS and Enable SQL Mirroring are selected, the FactoryTalk AssetCentre desktop client and web clients cannot connect to the mirrored database after a failover from the principal database.

To ensure the database mirroring function works properly, install Patch: Web client cannot show asset tree, FactoryTalk AssetCentre 12.0, 13.0, 15.0, 16.0, and then disable the TLS encryption. Follow the steps:

1. On the computer hosting SQL Server:

   1. Open SQL Server Configuration Manager, and then expand SQL Server Network Configuration.

   2. Right-click Protocols for <InstanceName>, and then select Properties.

   3. On Flags, set Force Encryption to Off, and then select OK.

   4. On SQL Server Configuration Manager, select SQL Server Services.

   5. Right-click SQL Server <InstanceName>, and then select Restart.

2. On the computer hosting the FactoryTalk AssetCentre server:

   1. Open FactoryTalk AssetCentre Data Source Configuration.

   2. On Database User Configuration, clear Secure communications using TLS.

   3. On FactoryTalk AssetCentre SQL Server Mirror, ensure Enable SQL Mirroring is selected.

   4. Complete the remaining configurations and save the changes.

Allen-Bradley Stratix Switch MAC address correction

For an Allen-Bradley Stratix Switch device, its actual MAC address scanned using CIP might differ from the MAC address shown on its switch management page. Each physical interface on a switch has its own unique MAC address that derives from a base MAC address. Additionally, logical ports, such as management ports, might have different MAC addresses. Therefore, the MAC address displayed on the switch management page of Stratix Switch serves only for management purposes. The actual MAC address is in its asset property or the RAAI file.

Use FactoryTalk Linx to browse Logix 5000 controllers of firmware revision 38.00 or later

Beginning with the version 38.00 firmware release, Logix 5000 controllers running firmware revision 38.00 or later can only be browsed using FactoryTalk Linx. RSLinx Classic cannot be used to browse controllers with these newer revisions in Studio 5000 Logix Designer nor FactoryTalk AssetCentre. The following table illustrates communication software support:

After upgrading an existing FactoryTalk AssetCentre system from an earlier version to version 16.00 and later, scheduled backup, backup and compare, and source code validation tasks will fail when:

• A Logix 5000 controller originally added to the asset tree using RSLinx Classic is later updated to firmware revision 38.00 or later.

• A Logix 5000 controller of firmware revision 38.00 or later is added to the asset tree via the import tool, and that controller was browsed using RSLinx Classic.

To resolve this problem, follow the steps to configure FactoryTalk Linx to browse Logix 5000 controllers:

1. In FactoryTalk AssetCentre Client, select Design.

2. In the asset tree, right-click the Allen-Bradley Logix 5000 Controller asset, and then select Properties.

3. In the Addressing Info box, select the browse button.

4. In the Network Browser list, select FactoryTalk Linx.

5. Find and select your device from the device list.

6. Select OK.

Run disaster recovery tasks for controller projects developed with RSLogix 5000 version 16.00 in FactoryTalk AssetCentre version 13.00 or later

FactoryTalk AssetCentre version 13.00 or later includes Logix Designer Compare Tool version 10.00 or later by default in its installation package. However, these versions of the Logix Designer Compare Tool are no longer compatible with RSLogix 5000 version 16.00. As a result, FactoryTalk AssetCentre version 13.00 or later cannot run disaster recovery tasks on controller projects developed with RSLogix 5000 version 16.00 when using the bundled Logix Designer Compare Tool.

To resolve this problem, do the following:

Part 1: Ensure FactoryTalk AssetCentre agent compatibility with RSLogix 5000 version 16.00

On the FactoryTalk AssetCentre agent computer version 13.00 or later, choose one of the following options. This is only required on agent computers that will be used to service Logix controllers running firmware revision 16.00.

• (Recommended) To install a new FactoryTalk AssetCentre agent version 13.00 or later

  1. Install Logix Designer Compare Tool version 9.00 from the Product Compatibility and Download Center (PCDC).

     We recommend installing this before installing the FactoryTalk AssetCentre agents. If a newer version is already installed, uninstall it via the Control Panel.

  2. Install FactoryTalk AssetCentre Agent software version 13.00 or later from the installation package or PCDC.

     During installation, manually clear the Logix Designer Compare Tool checkbox to prevent an automatic upgrade. For more information, see Install the FactoryTalk AssetCentre Agent software in the FactoryTalk AssetCentre Installation Guide.

• To modify an existing FactoryTalk AssetCentre agent version 13.00 or later installation for compatibility

  1. Uninstall the current Logix Designer Compare Tool version 10.00 or later via the Control Panel.

  2. Install Logix Designer Compare Tool version 9.00 from the Product Compatibility and Download Center (PCDC).

Part 2: Create agent groups for FactoryTalk AssetCentre agents that are compatible with the RSLogix 5000 version 16.00

On the FactoryTalk AssetCentre desktop client computer:

1. Open FactoryTalk AssetCentre desktop client, and then enter the Design mode.

2. Create an agent group to include agents that will run tasks for controller projects developed with RSLogix 5000 version 16.00.

   1. On the Menu bar, select View > Agent Groups.

   2. On the Agent Group Creation and Agent Assignment toolbar, select the Add Agent Group button, configure the settings for the agent group, and then select OK.

   3. Select the created agent group, and then select Add Agent Computer to add agents.

   4. Configure the settings for the agent computers, and then select OK.

3. Exit the Design mode.

Part 3: Assign controller assets to FactoryTalk AssetCentre agent groups that are compatible with the RSLogix 5000 version 16.00

On the FactoryTalk AssetCentre desktop client computer:

1. Open FactoryTalk AssetCentre desktop client, and then enter the Design mode.

2. Configure all Allen-Bradley Logix 5000 Controller assets running firmware with major revision 16 to use the newly created agent group.

   1. Select an Allen-Bradley Logix 5000 Controller asset in the asset catalog and add it to the asset tree.

   2. On asset properties, select the Agent Group field, find the created agent group, and then select OK.

   3. Configure other properties as desired, and then select OK.

      Repeat steps a-c for all controller assets running firmware with major revision 16.

3. Exit the Design mode.

4. Create disaster recovery tasks as needed.

   For more information, see Agent Groups and Schedules in the FactoryTalk AssetCentre Desktop Client Help. 

FactoryTalk Directory asset compare

Differences are always found between two FactoryTalk Directory backup files after a Backup and Compare schedule, even though no changes are made to the FactoryTalk Directory. This is because the BAK files include timestamp information, which is detected as a difference during the binary compare of the backup files.

Event Log Attachment Extractor

The Event Log Attachment Extractor utility cannot properly extract event log attachments in the following two cases:

• For Backup and Compare schedules that compare both backup data and configuration data, the event log attachment of the configuration data cannot be extracted by the Event Log Attachment Extractor utility.

• When running a Backup and Compare schedule on the Generic FTP device with a custom compare engine, only the last compare report attachment can be extracted.

Install product updates

For the latest Product Updates and Patch information, refer to Knowledgebase Document ID: QA15600 - FactoryTalk AssetCentre Patch Roll-up for 3.0 and later.

You can subscribe to be notified when new product updates, or patches are released via the Knowledgebase by clicking below the Knowledgebase answer title.

To download software or firmware updates, and patch roll-ups, go to Product Compatibility and Download Center.

Security requirements

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

• File extensions created by Rockwell Automation software, firewall rules, and service dependencies, see Knowledgebase Document ID: PN826 - Security considerations when using Rockwell Automation Software Products.

• TCP/UDP ports used by Rockwell Automation products, see Knowledgebase Document ID: BF7490 - TCP/UDP Ports Used by Rockwell Automation Products.