# OPC-DA Connection Issues With Red Lion OPCWorx Server **URL:** \ **Category:** Ignition\ **Created:** [October 12, 2026, 6:45pm UTC](https://forum.inductiveautomation.com/t/opc-da-connection-issues-with-red-lion-opcworx-server/117429 "2026-10-12T18:45:14Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![coyne.321](https://avatars.discourse-cdn.com/v4/letter/c/db5fbb/32.png) [@coyne.321](https://forum.inductiveautomation.com/u/coyne.321)\ **Post date:** [October 12, 2026, 6:45pm UTC](https://forum.inductiveautomation.com/t/opc-da-connection-issues-with-red-lion-opcworx-server/117429/1 "2026-10-12T18:45:14Z")
Hi, I'm struggling to connect to an OPCWorx server, which is provided by Red Lion Controls. This server is running on the same Windows 10 VM that my Ignition gateway (v8.3.9) is on. The progID shows up automatically when configuring the connection: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/9/c9d83099f6f59ffa35965f85a3973c7e0cdad037.png) After saving the config, I get the error below. I'm able to successfully browse tags from this server using the Matrikon OPC Explorer. I went through (almost) all of the steps on this page: [OPC COM | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/ignition-modules/opc-ua/third-party-opc-servers/opc-com), with the exception of the "OPC Server DCOM Settings" section at the end since I'm unable to identify an entry corresponding with the OPC server. In case it's relevant, I'm seeing a few DCOM events in the Windows Event Viewer like this: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/d/fde272b375b9fc329d929dbdabd8460dd2ff49c5.png) A bit strange that the APPID and SID are not populated. Any suggestions on what I can look at next? Jeremy `java.lang.IllegalStateException: The server did not indicate that it was ready to receive connections.` `at com.inductiveautomation.opccom.COMServerImpl$3.run(COMServerImpl.java:465)` `at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$ThrowableCatchingRunnable.run(BasicExecutionEngine.java:557)` `at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)` `at java.base/java.util.concurrent.FutureTask.run(Unknown Source)` `at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)` `at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)` `at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)` `at java.base/java.lang.Thread.run(Unknown Source)` ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [October 12, 2026, 7:35pm UTC](https://forum.inductiveautomation.com/t/opc-da-connection-issues-with-red-lion-opcworx-server/117429/2 "2026-10-12T19:35:02Z")
I've used [OPCExpert](https://www.opcti.com/opcexpert.aspx) in the past to troubleshoot OPC-DA things. The free version runs four hours at a stretch. It might give you some insight. * * * Didactic warning ahead... ☝🤓 That particular error usually pops up because the Windows Security Center service is configured with a delayed startup. WscDataProtection tries to communicate early before wscsvc has finished starting. That can be fixed by turning of the DelayedAutoStart flag. IIRC, that has to be done through the registry editor. I've also seen this happen if OneDrive is a startup app. * * * ---
**Author:** ![coyne.321](https://avatars.discourse-cdn.com/v4/letter/c/db5fbb/32.png) [@coyne.321](https://forum.inductiveautomation.com/u/coyne.321)\ **Post date:** [October 12, 2026, 9:59pm UTC](https://forum.inductiveautomation.com/t/opc-da-connection-issues-with-red-lion-opcworx-server/117429/3 "2026-10-12T21:59:14Z")
Appreciate the advice, @JordanCClark. I tried OPCExpert per your suggestion and got the following error: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/0/e0d430a2dff2da04df1ddaf75dd1e869fa6a4222.png) I registered both of the DLLs recommended (they were packaged with the OPCExpert software in the "General OPC Files" folder), but I get the same error upon closing and restarting OPCExpert. Per your second suggestion, I tried setting the value of the registry entry Computer\HKEY\_LOCAL\_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc\DelayedAutoStart from 1 to 0. I have the same error in both the Ignition gateway and OPCExpert after rebooting my VM. Any other thoughts? Thanks, Jeremy ---
**Author:** ![coyne.321](https://avatars.discourse-cdn.com/v4/letter/c/db5fbb/32.png) [@coyne.321](https://forum.inductiveautomation.com/u/coyne.321)\ **Post date:** [October 12, 2026, 10:28pm UTC](https://forum.inductiveautomation.com/t/opc-da-connection-issues-with-red-lion-opcworx-server/117429/4 "2026-10-12T22:28:25Z")
Also, for what it's worth, I'm able to connect and browse tags on the server if I DON'T run OPCExpert as admin. There's a warning when launching the software that running as a non-admin user can cause "unexpected failures", but it seems to be the opposite case for me. Interestingly, I have the same behavior with the Matrikon OPC Explorer program. It works fine when run as a normal user, but I cannot connect or browse tags when running as admin. Curious whether that indicates any possible issues for Ignition connecting? ---
**Author:** ![ejones761](https://avatars.discourse-cdn.com/v4/letter/e/45deac/32.png) [@ejones761](https://forum.inductiveautomation.com/u/ejones761)\ **Post date:** [October 30, 2026, 12:40pm UTC](https://forum.inductiveautomation.com/t/opc-da-connection-issues-with-red-lion-opcworx-server/117429/5 "2026-10-30T12:40:09Z")
Did you ever figure out your problem? ---
**Author:** ![coyne.321](https://avatars.discourse-cdn.com/v4/letter/c/db5fbb/32.png) [@coyne.321](https://forum.inductiveautomation.com/u/coyne.321)\ **Post date:** [October 30, 2026, 4:26pm UTC](https://forum.inductiveautomation.com/t/opc-da-connection-issues-with-red-lion-opcworx-server/117429/6 "2026-10-30T16:26:14Z")
No luck yet. Still curious to figure out how to get OPC-DA working, but will have to use Modbus otherwise. ---
**Author:** ![Nol](https://avatars.discourse-cdn.com/v4/letter/n/8e8cbc/32.png) [@Nol](https://forum.inductiveautomation.com/u/Nol)\ **Post date:** [November 2, 2026, 8:26pm UTC](https://forum.inductiveautomation.com/t/opc-da-connection-issues-with-red-lion-opcworx-server/117429/7 "2026-11-02T20:26:46Z")
> [@coyne.321](#): > > A bit strange that the APPID and SID are not populated. Any suggestions on what I can look at next? > [@coyne.321](#): > > I'm able to connect and browse tags on the server if I DON'T run OPCExpert as admin. Given ProgId populated that means windows can lookup the server from the registry but the fact it works with one user account but not admin (and probably Ignition cant via system) I think it's an issue where windows is spinning up a new copy of the server for each user so the one Ignition is connecting to isn't configured. This is probably the section relevant: > **[Ignition Launches Second Instance of an Already Running OPC Server and is... -...](https://www.docs.inductiveautomation.com/docs/8.3/ignition-modules/opc-ua/third-party-opc-servers/opc-com#ignition-launches-second-instance-of-an-already-running-opc-server-and-is-unable-to-see-any-data)** > > OPC Classic is based on COM, which is a technology in Microsoft Windows. Therefore, the information in this section only applies to Ignition Gateways installed on Windows. Other operating systems must use OPC UA. | Connecting to OPC Classic (COM)