FactoryTalk Linx health

Safety first

Treat HMI commands as real machine commands. Do not test writes from a production HMI or OPC client unless operations has approved the exact tag and state change.
Back up FactoryTalk Directory, application files, and FactoryTalk Linx shortcut/driver configuration before replacing or importing communication setup.
Coordinate with production before restarting FactoryTalk Linx, FactoryTalk Directory, HMI servers, or Gateway services.
If the issue involves security or permissions, do not temporarily grant broad access without documenting the test and reverting it.

HMI displays question marks, stale values, or bad quality.
Tag browser cannot see a controller or sees the wrong controller.
A shortcut browses in development but fails at runtime.
Restored application has missing or broken shortcuts.
FactoryTalk Linx Gateway clients can connect but see no tags, bad quality, or write failures.
One workstation works but another client or server does not.

Confirm whether the application is using Local Directory or Network Directory and open the same scope in FactoryTalk Administration Console.
Open Communication Setup and verify the shortcut points to the intended online controller, not an old path, old IP, or offline project reference.
Check FactoryTalk Diagnostics around the failure time before restarting services.
Confirm the FactoryTalk Linx data server is in the expected area and that there is not an unnecessary second data server competing for the same clients.
Export or screenshot the current shortcuts and drivers before editing them.
For OPC UA/Gateway, verify endpoint, certificate trust, namespace/tag group selection, authentication method, and whether the tag itself is controller read-only.

Follow the sequence before changing parameters, replacing hardware, or cycling power.

1Write down the client: View SE display, alarm server, historian, OPC client, Excel RTD, custom client, or Gateway client.
2Write down the tag name as the client sees it and the expected controller, program, and tag path.
3Determine whether the data path is FactoryTalk Live Data through View SE, direct FactoryTalk Linx browsing, or FactoryTalk Linx Gateway.
4Confirm which server owns the path: local workstation, HMI server, data server, or Gateway workstation.

1Open FactoryTalk Administration Console or FactoryTalk View Studio in the same directory scope as the failing application.
2Open FactoryTalk Linx Communication Setup.
3Browse to the controller through the configured driver and verify the shortcut target is online.
4If the controller was replaced, downloaded, or moved, re-browse and re-apply the shortcut rather than trusting the old path.
5Use the configuration import/export tool for repeatable backups or migrations instead of relying on screenshots only.

1Check Windows Services for FactoryTalk Linx, FactoryTalk Directory, and Gateway services that apply to the affected workstation.
2Review FactoryTalk Diagnostics and Windows Event Viewer before service restarts.
3Confirm the logged-in user or service account has FactoryTalk Security access to the requested feature and tags.
4When OPC UA clients are affected, check certificate trust, endpoint hostnames, authentication mode, and tag group access.

Use these buckets to separate evidence and avoid chasing unrelated symptoms.

Tag browser works inconsistently, HMI reads old data, or the online path changes after controller replacement.

Shortcut target still references an old chassis slot, IP address, or controller identity.
Application was restored to a different workstation and driver names or host names changed.
The wrong FactoryTalk Directory scope is open.

Browse from the actual HMI server or data server, not only from an engineering laptop.
Compare shortcut path, controller name, IP address, slot, and online identity.
Check whether the shortcut exists in the same application area used by the client.
Export current shortcut configuration before making changes.

Re-browse and re-assign the shortcut to the online controller.
Correct driver names and workstation references after restores or server moves.
Use the import/export tool for repeatable restoration and peer review.
Restart only the affected clients or services after confirming the change window.

Multiple applications or clients fail at once, or the same shortcut fails from only one server.

Compare behavior from the HMI server, engineering workstation, and client workstation.
Review FactoryTalk Diagnostics for directory, security, and Live Data messages.
Confirm DNS and hostnames for distributed FactoryTalk servers.
Check service startup state and account changes.

Restore name resolution or Directory connectivity before editing shortcuts.
Restart affected services only during an approved window.
Correct FactoryTalk Security permissions narrowly, then retest with the intended user or service account.
Document the event log time range and service restart time.

OPC UA client connects but sees missing nodes, bad quality, failed writes, or certificate-related errors.

Client certificate is not trusted or endpoint hostname does not match.
Tags were not added to the UA tag list or tag group.
FactoryTalk Security group does not grant access to the client identity.
Controller tag access is read-only even though the Gateway tag group appears write-enabled.
Namespace is stale after controller tag changes.

Verify endpoint URL, certificate trust, security policy, and client authentication method.
Check UA tag list and tag group membership for the affected tags.
Confirm the OPC UA client user is in the expected FactoryTalk Security group.
Compare Gateway access settings to the tag access settings in the controller.
Plan namespace refresh because active OPC UA clients can be disconnected during refresh.

Trust or regenerate certificates using the approved certificate workflow.
Add missing tags to the correct tag group and save the Gateway configuration.
Fix security group membership or endpoint authentication settings.
Change controller tag access in Studio 5000 when the controller is the limiting authority.
Refresh namespace during a planned window if the tag structure changed.

FactoryTalk Directory scope: Local or Network.
Application name, area, FactoryTalk Linx server name, shortcut name, and controller target.
Screenshots of Communication Setup before and after changes.
FactoryTalk Diagnostics export around the failure time.
Windows Event Viewer service errors.
Gateway endpoint URL, certificate status, security policy, tag group, authentication mode, and affected node ID.
Whether the issue follows the client, server, user, controller, or shortcut.

FactoryTalk Directory cannot be reached by multiple FactoryTalk products.
Diagnostics show security or policy errors and the site has formal access-control ownership.
Gateway clients require production writes and the test tag/write procedure is not approved.
Restored application appears to have lost shortcut configuration and no recent export exists.
Service restarts would affect active operators or alarm handling.