Professional OPC
Development Tools


Online Forums

Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.

Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.

Do not use the Contact page for technical issues.


04 Dec 2013 08:27 #1590 by support
Replied by support on topic OPC DCOM
I agree this is related to DCOM. Most likely, it is the reverse direction (setting up and performing callbacks from the OPC server to OPC client) that does not work. This reverse direction is needed for OPC async read/writes, and for subscriptions.

Earlier versions of QuickOPC (5.12 included) required the reverse direction be always operational. The newer versions are more forgiving, and degrade their functionality where possible - so if you are just using reads and writes, and the callbacks are not operational, QuickOPC will just fallback to synchronous calls, and work. I suppose that this is happening with QuickOPC 5.23. It might be OK unless you need subscriptions as well. To verify that the reverse call direction is causing the problem, try to establish a subscription with QuickOPC Version 5.23 - my bet is that it won't work.

For truly resolving the issue, try to:
  1. Configure DCOM - pay special attention to settings for the reverse direction - i.e. mainly on the client machine - it should be possible for the server to get back to (access) the client.
  2. Experiment with parameter settings, as in this topic:

Best regards

Please Log in or Create an account to join the conversation.

03 Dec 2013 08:45 #1588 by barbieri
Replied by barbieri on topic OPC DCOM
Hello, thanks for your support.

1. We tested 5.12 without success (unable to read and write) and then we tested 5.23 and this versions works.

2. We can read and write with version 5.23

3. We tested only read and write

4. We tested on a local kepware server and it works without problems

5. We tested Quick OPC Client and it works without problems

With Version 5.23 we have a working situation but sometimes we have problems related to timeout error (-1073430527 cannot connect data access client (timeout)).

thanks for your support

Please Log in or Create an account to join the conversation.

03 Dec 2013 08:32 #1587 by support
Replied by support on topic OPC DCOM
I do not fully understand your report.

Can you please answer:
  1. Are you only using Version 5.10, or some other version as well?
  2. Is there is a situation in which the read or write DOES work?
  3. Are there are other things that work - for example, the BrowseXXXX methods? Or SubscribeXXXX? Or, do they return the same error? Or have you just not tried them - you only tested ReadXXXX and WriteXXXX?
  4. Does it work well when the OPC server is local (if it can be tested)?
  5. Have you tried some other OPC client, from the same computer, and what were the results?

Thank you

Please Log in or Create an account to join the conversation.

02 Dec 2013 13:30 #1584 by barbieri
OPC DCOM was created by barbieri
Dear All, I have this kind of problem:
I'm connecting an OPC client on my PC to a remote B&R OPC server.
using an OPC client (i.e OPC Quick client) I'm able to read an write all the TAG on the remote server.
using my c# application, this application works as an OPC client using quick OPCClassic 5.10 dll, I'm not able to write TAGs.
this is the error I have on my application:
OPC Operation failure error code - 2147220992
I think this is a DCOM related problem but I don't know the DCOM configuration to be changed.

thanks for your support

Please Log in or Create an account to join the conversation.

Moderators: support
Time to create page: 0.056 seconds