# Connecting DeltaV OPC DA server to Ignition **URL:** \ **Category:** Ignition\ **Created:** [May 19, 2020, 6:24pm UTC](https://forum.inductiveautomation.com/t/connecting-deltav-opc-da-server-to-ignition/34893 "2020-05-19T18:24:55Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Andy.Olsen](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@Andy.Olsen](https://forum.inductiveautomation.com/u/Andy.Olsen)\ **Post date:** [May 19, 2020, 6:24pm UTC](https://forum.inductiveautomation.com/t/connecting-deltav-opc-da-server-to-ignition/34893/1 "2020-05-19T18:24:55Z")
I’m trying to connect the gateway to an Emerson DeltaV OPC-DA server to no avail. I keep getting the general COM object method returns error code: 0x80040154; REGDB\_E\_CLASSNOTREG error. I know that the OPC Core Components are installed and working. I can successfully connect to the OPC server from the same client machine with TopView and other OPC tools and browse the tag trees and get values. This is because I can launch the applications under a different user (DeltaVAdmin) that is required to talk to the OPC server. That is the ONLY account Emerson allows to communicate with OPC as a client. I can fire up Firefox as that user, but I think there is some other service connecting to the OPC server as another account and it is failing. I can see the JAVA wrapper is using the proper credentials to connect, but something is weird in between. I’ve wasted several days on DCOM and other attempts at connecting. It’s frustrating because I can connect PI OPC interfaces and other tools to it successfully. Anyone else figure out a solution to something like this? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 19, 2020, 6:27pm UTC](https://forum.inductiveautomation.com/t/connecting-deltav-opc-da-server-to-ignition/34893/2 "2020-05-19T18:27:02Z")
> [@Andy.Olsen](#): > > This is because I can launch the applications under a different user (DeltaVAdmin) that is required to talk to the OPC server. That is the ONLY account Emerson allows to communicate with OPC as a client. Have you tried changing the user the Ignition service runs under to DeltaVAdmin? ---
**Author:** ![Andy.Olsen](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@Andy.Olsen](https://forum.inductiveautomation.com/u/Andy.Olsen)\ **Post date:** [May 19, 2020, 6:31pm UTC](https://forum.inductiveautomation.com/t/connecting-deltav-opc-da-server-to-ignition/34893/3 "2020-05-19T18:31:08Z")
Did that. The weird thing, is that when I set up the OPC module to connect to the OPC Source, it will browse out and let me pick from the list of available OPC ProgIDs. It just won’t connect once I save the settings. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/d47f573bd63f08a97d224eea68cc94ae1a0c66ce.png) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 19, 2020, 6:36pm UTC](https://forum.inductiveautomation.com/t/connecting-deltav-opc-da-server-to-ignition/34893/4 "2020-05-19T18:36:11Z")
Hmm. I don’t know enough about DCOM to be much help. There’s some other threads about DeltaV, like [this one](http://forum.inductiveautomation.com/t/opc-com-connection-between-64-and-32-bit-systems/11143/3), that suggest making sure you have a 64-bit OPC Core Components installed, and [this one](http://forum.inductiveautomation.com/t/opc-da-errors/8003/2), that suggest the Ignition service also needs to be set up to run as an interactive user. ---
**Author:** ![Andy.Olsen](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@Andy.Olsen](https://forum.inductiveautomation.com/u/Andy.Olsen)\ **Post date:** [May 19, 2020, 8:16pm UTC](https://forum.inductiveautomation.com/t/connecting-deltav-opc-da-server-to-ignition/34893/5 "2020-05-19T20:16:21Z")
I just don’t think it is in OPC, I can run any number of tools and connect. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/9/9c000ecda4f8eab6e1f694939091ccdf3f9b1736.png) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 19, 2020, 8:19pm UTC](https://forum.inductiveautomation.com/t/connecting-deltav-opc-da-server-to-ignition/34893/6 "2020-05-19T20:19:25Z")
Did you try setting the service to run as an interactive user? [https://www.ibm.com/support/knowledgecenter/en/SSGR73\_7.5.1/com.ibm.wci.live.doc/Secure\_Connector/enablinginteractivemodeforwindowsservices.html](https://www.ibm.com/support/knowledgecenter/en/SSGR73_7.5.1/com.ibm.wci.live.doc/Secure_Connector/enablinginteractivemodeforwindowsservices.html) Ignition is different than any of the tools you’re using in that it runs as a service, which is also a different user by default, so sometimes things like changing the service user and allowing the service to interact with the desktop are required. ---
**Author:** ![Andy.Olsen](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@Andy.Olsen](https://forum.inductiveautomation.com/u/Andy.Olsen)\ **Post date:** [May 19, 2020, 8:26pm UTC](https://forum.inductiveautomation.com/t/connecting-deltav-opc-da-server-to-ignition/34893/7 "2020-05-19T20:26:19Z")
Once I change that to interactive logon, I get Access Denied as the error. And it will not offer a list of ProgIds when setting up a new OPC connection. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/5/532c8204d27dcae308146fc5a2903e7c249024da.png) ---
**Author:** ![Andy.Olsen](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@Andy.Olsen](https://forum.inductiveautomation.com/u/Andy.Olsen)\ **Post date:** [May 19, 2020, 8:57pm UTC](https://forum.inductiveautomation.com/t/connecting-deltav-opc-da-server-to-ignition/34893/8 "2020-05-19T20:57:02Z")
DCOM got error “2147942405” from the computer 172.16.10.129 when attempting to activate the server: {C3B72AB1-6B33-11D0-9007-0020AFB6CF9F} ---
**Author:** ![qliu](https://avatars.discourse-cdn.com/v4/letter/q/bc8723/32.png) [@qliu](https://forum.inductiveautomation.com/u/qliu)\ **Post date:** [March 1, 2021, 8:51pm UTC](https://forum.inductiveautomation.com/t/connecting-deltav-opc-da-server-to-ignition/34893/9 "2021-03-01T20:51:12Z")
Hey Andy, Do you get the solution for this issue? I am working on a project and try to learn how to set up between Ignition and DeltaV. Thanks! ---
**Author:** ![richard040693](https://avatars.discourse-cdn.com/v4/letter/r/7cd45c/32.png) [@richard040693](https://forum.inductiveautomation.com/u/richard040693)\ **Post date:** [October 28, 2021, 3:17pm UTC](https://forum.inductiveautomation.com/t/connecting-deltav-opc-da-server-to-ignition/34893/10 "2021-10-28T15:17:28Z")
Hi Andy, Qliu We recently have the same issue and we had to open a support ticket with Emerson (DeltaV Vendor). The response was _"Please note that by default, DeltaV OPC Server only supports 32-bit OPC Clients. If you want to have OPC communication using 64-bit OPC Clients, you need to use OPC Data Link as specified in the attached KBA._" Our solution was install a OPC DA Client 32 bits (our case was Ignition 7.9.18 32 bits) and expose the tags with OPC Tunneller. With this steps we can browse the tags at Ignition 8.1.7 64 bits because we need perspective in our infrastructure. I hope this will help! ---
**Author:** ![Andy.Olsen](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@Andy.Olsen](https://forum.inductiveautomation.com/u/Andy.Olsen)\ **Post date:** [October 28, 2021, 3:39pm UTC](https://forum.inductiveautomation.com/t/connecting-deltav-opc-da-server-to-ignition/34893/11 "2021-10-28T15:39:32Z")
Thanks for the update, we ended up using Kepware as the OPC tunneller and exposed it as OPCUA to the Ignition client. DeltaV is a complicated package of requirements regarding OPC connections. It’s too bad that there was a need for an extra intermediary in the data pipe, but it turned out to work well for the customer.