10/31/2019
With reference to my last post where I am trying to find a OPC automation wrapper that will allow me to get data from an OPC server into Excel, I have come across the wrapper opcdaauto.dll.
However when I use this with my Excel 2013 I get an error message. The error is Run-time error ‘429’ – ActiveX component can’t create object.
This error occurs when the VBA executes the following line of code:
Set myOPCServer = New OPCServer
opcdaauto.dll has been registered and added to the VBA references.
I am stuck as I feel I am banging my head against a wall in order to get this to work.
Any help or advice is gratefully received.
05/30/2017
OPC depends on DCOM permissions being set correctly.
If the OPC server is running in the same account as the Excel application then it should work.
As soon as you introduce other accounts or multiple machines then you need to go through the DCOM configuration process.
Start here if you need more information:
03/05/2018
I am having the same issue with same code, same dll.
A little background
I am running Matrikon OPC simulator and i am able to see values using the mobile OPC explorer (all from localhost). So I don’t think its a permissions issue.
I am running office 365 on Windows 10.
i’ve also tried installing OPC DA Auto 2.02 Specification
in which case i needed .net 1.1
i then had to run OPC DA Auto 2.02 Specification.msi in compatibility mode
it didn’t seem to give me any more dll files for excel.
05/30/2017
Being on localhost is not enough. The OPC Server must be running as the same user as the Excel application.
That said, opcdaauto.dll is 20 year+ s/w that uses technology that Microsoft no longer supports.
If you can get it work you are lucky but you should not assume that it will be possible.
You need to upgrade to libraries that support the latest versions of .NET.
1 Guest(s)