When a FactoryTalk View SE client cannot open the application, or opens it but shows tags with errors, the cause is usually on one of four layers: the FactoryTalk Directory, the network between client and servers, the servers themselves, or a firewall. The checklist below follows Rockwell Automation's own troubleshooting pages.
1. Client and server basics
Rockwell's troubleshooting page for client–server communication lists these first checks (FactoryTalk View SE 16.00 help, "Troubleshooting the client and server communications"):
- The client and the server point to the same FactoryTalk Directory.
- The client and the server run the same version.
- Ping the server by name, then by IP address. If the IP address answers but the name does not, the problem is name resolution, not the network.
- Browse to the server name to test IIS (restart IIS in IIS Manager if needed), then browse to the RSViewSE site.
2. Check the status of the servers
The FactoryTalk System Status Portal shows the status of the HMI, Alarms and Events, FactoryTalk Linx and OPC servers in the application. States include Active, Standby, Not loaded, Failed, Transitioning and Unknown; with redundancy configured, the partner server provides service when one fails (FactoryTalk View SE help, "Server status of an application").
In displays, the functions PrimaryServerStatus("/Area/Server") and SecondaryServerStatus return codes such as 4 = Active, 5 = Standby, 6 = Active with no partner or partner unreachable, and 0x80000003 = failed or host unreachable (SE help, "Redundancy functions"). On a poor network these functions can return empty or wrong values; Rockwell's fix is to increase the detection intervals in FactoryTalk Administration Console under System > Policies > System Policies > Health Monitoring Policy (same page).
3. If the FactoryTalk Directory server was replaced
If the Directory server computer was replaced and the new computer has a different name, user authentication can fail even though the client appears connected. The fix is to add the client computers under System > Computers and Groups and reconnect each client (FactoryTalk Services Platform 6.60 help, "I can't connect to the FactoryTalk Directory server").
4. Firewalls between client and servers
Rockwell lists the ports FactoryTalk services use in FTSP-RM001C, "Configuring Firewalls for FactoryTalk Services Platform" (September 2025). Examples:
| Service | Program | Port | Reference |
|---|---|---|---|
| FactoryTalk Directory | RnaDirServer.exe | TCP 3060 (v6.21 and later), TCP 3061 (v6.40 and later) | Table 11, p. 22 |
| FactoryTalk Directory agent | — | TCP 1332 | Table 7, p. 17 |
| FactoryTalk Linx | FTLinxServices.exe | TCP 5698 | Table 13, pp. 24–25 |
| FactoryTalk Linx | RSLinxNG.exe | TCP 2221, TCP/UDP 44818, TCP 2222 | Table 13, pp. 24–25 |
| Alarms and Events | RnaAeServer.exe | TCP 6543 | Table 13, p. 24 |
The publication also notes the dynamic port range 49152–65535 (p. 8). Use the full tables in the publication for the version installed; this list is not complete.
Before calling for help
Note the FactoryTalk View SE and FactoryTalk Services Platform versions on client and servers, the server states shown in the System Status Portal, the exact error text, and whether one client or all clients are affected. TDL engineers can then check the case remotely or on site.
Frequently asked questions
What should I check first when a FactoryTalk View SE client cannot connect to the server?
Per Rockwell's troubleshooting page, check that the client and the server point to the same FactoryTalk Directory and run the same version, then ping the server by name and by IP address. If the IP address answers but the name does not, the problem is name resolution, not the network.
Where can I see the status of the HMI, Alarms and Events and FactoryTalk Linx servers?
The FactoryTalk System Status Portal shows the status of the servers in the application: Active, Standby, Not loaded, Failed, Transitioning or Unknown. In displays, the PrimaryServerStatus and SecondaryServerStatus functions return codes such as 4 = Active, 5 = Standby, 6 = Active with no partner or partner unreachable.
The FactoryTalk Directory server was replaced and clients now fail authentication. What should I do?
If the new Directory server computer has a different name, user authentication can fail even though the client appears connected. The fix is to add the client computers under System > Computers and Groups and reconnect each client.
Which firewall ports does the FactoryTalk Directory use?
According to FTSP-RM001C, RnaDirServer.exe uses TCP 3060 (v6.21 and later) and TCP 3061 (v6.40 and later), the Directory agent uses TCP 1332, and the publication also notes the dynamic port range 49152–65535. Use the full tables in the publication for the version installed.
Sources
- Rockwell Automation, FTSP-RM001C-EN-P, Configuring Firewalls for FactoryTalk Services Platform, 09/2025 — pp. 8, 17, 22, 24–25
- Rockwell Automation, FactoryTalk View SE 16.00 help: "Troubleshooting the client and server communications"; "Server status of an application"; "Redundancy functions" (rockwellautomation.com)
- Rockwell Automation, FactoryTalk Services Platform 6.60 help: "I can't connect to the FactoryTalk Directory server"
Read 24 October 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system. Links open the latest edition in Rockwell's literature library; page numbers refer to the edition cited.