"OPC UA Connector is out of memory" appears in FactoryTalk Diagnostics Log

The

FactoryTalk Linx

OPC

UA Connector service is out of system resources. The

FactoryTalk Diagnostics

Log

may display the error "Insufficient memory to continue".

Use

Windows

Event Viewer to determine if the

FactoryTalk Linx

OPC

UA Connector service crashed or was closed due to insufficient system memory.

Use

Windows

Resource Monitor to determine how much CPU capacity is used by the

FactoryTalk Linx

OPC

UA Connector service. If the

FactoryTalk Linx

OPC

UA Connector service uses 100% of host CPU capacity, move the service to a host with higher CPU performance. For best performance, use high power Server hosts instead of embedded controllers.

Use

Windows

Resource Monitor to determine how much Memory capacity is used by the

FactoryTalk Linx

OPC

UA Connector service. If the

FactoryTalk Linx

OPC

UA Connector service uses 100% of host Memory capacity, move the service to a host with higher Memory capacity. For best performance, use high power Server hosts instead of embedded controllers.

Use

Windows

Resource Monitor to identify services that may be competing for system resources with the

FactoryTalk Linx

OPC

UA Connector service. Disable unnecessary services on the

FactoryTalk Linx

OPC

UA Connector host, or move the

FactoryTalk Linx

OPC

UA Connector service to a dedicated host. For best performance, use high power Server hosts instead of embedded controllers.

Spread the

OPC

UA Server load across multiple

FactoryTalk Linx

OPC

UA Connectors. In the same application, create a new

FactoryTalk Linx

OPC

UA Connector hosted on another host. Remove

OPC

UA Servers from the

FactoryTalk Linx

OPC

UA Connector host that is out of system resources. Then, add the

OPC

UA Servers to the

FactoryTalk Linx

OPC

UA Connector on new host. Update tag browse paths in the

FactoryTalk

client application to use the new

FactoryTalk Linx

OPC

UA Connector path.