OPC DA Connectivity Troubleshooting Between Ignition Edge and Kepware

Issue:
Trying to get values from a remote kepserver into ignition edge via OPC DA. Ignition Edge OPC DA connection to a remote Kepware server fails with 0x80040154 (Class not registered) and E_ACCESSDENIED errors, despite successful tag reads using Matrikon OPC Explorer on the same Edge machine.

Steps Taken:

  1. DCOM and User Configuration:
  • Ensured matching local admin user accounts on both Kepware and Edge machines.
  • Configured DCOM permissions for OpcEnum and Kepware DCOM objects (Launch/Activation and Access for Everyone/ANONYMOUS LOGON).
  • Set Ignition Edge service to run under a DCOM-authorized admin account.
  1. OPC Core Components:
  • Installed both 32-bit and 64-bit OPC Core Components Redistributables on the Edge machine.
  • Registered required 32-bit OPC DLLs using regsvr32 from SysWOW64.
  1. Registry Edits:
  • Located the CLSID for Kepware.KEPServerEX.V6 on the Kepware server.
  • Created and merged .reg files on the Edge machine under both regular and WOW6432Node registry paths, including correct RemoteServerName (Kepware server’s computer name).
  1. Firewall:
  • Opened TCP port 135 and dynamic ports 49152–65535 on both machines.
  • Allowed OPCEnum.exe through the firewall.
  1. Testing and Validation:
  • Used Matrikon OPC Explorer on the Edge machine to confirm OPC tags are readable from Kepware.
  • Ignition Edge still fails with class registration errors and cannot browse/connect to the remote server.

Current Status:

  • OPC access from third-party clients (Matrikon) works on the Edge machine.
  • Ignition Edge OPC COM module still cannot connect to the remote Kepware server due to class registration errors, despite all registry, DCOM, and firewall steps above.

Request:
Looking for any additional steps or insights to resolve the Class not registered error for OPC DA connections in Ignition Edge, or confirmation if there are known limitations with 32-bit Kepware and 64-bit Ignition Edge DA connectivity.