Hello,

the behavior you described seems to point in the same direction: The issue is in DCOM permissions, and more specifically, in the "reverse" direction: from the server to the client. This explains why getting properties works, because it does not use the reverse channel. What should also work, as a workaround, is a Read while disabling the asynchronous method (as you have done in the past) plus all the settings I described in my #8098 (from Dec 19, 2019).

For the DCOM permissions themselves, please have another look at the default DCOM permissions on the client side. And, have you tried the combinations of settings I described in my previous post (#8111, from Dec 29, 2019)?

Regards

Dear Sir,

unfortunately there isn't much I can advise at this state. I was hoping that with the OPC Analyzer, we would be able to see the flow of messages and determine what's wrong. But since the symptoms changed with OPC Analyzer in between (this sometimes happens), we are back to point zero.

Assuming that local connection works OK, problems that only appear on remote connections are almost always due to DCOM settings, or proxy/stub installation (OPC Redistributables). So, I can only advise "tinkering" with these. QuickOPC is somewhat different from many other clients in that it's in .NET, and the settings that works with native applications may differ.

You could also try assigning different combinations to following static properties - in the code, before the very first OPC operation is attempted; can be done just once in process run:

[TurnOffCallSecurity only has any influence when UseCustomSecurity == true.]

I am sorry I can only offer "wild guesses", but that's all I have.

Regards

Hello,
thanks for the report.

So, do I understand it correctly that with the OPC Analyzer, the behavior has changed, with both clients?
That would be unfortunate, as it would mostly preclude us from actually getting useful info from the OPC Analyzer, but it happens sometimes.

Regards

From: D.
Sent: Friday, December 20, 2019 2:35 PM
To: Z.
Subject: Re: OPC Analyzer link

Hello,
Thanks for you help.

My result:
OPCclient_trace.tra - trace for OPCLab .Net client. Data read through OPC Analyzer get very quickly.
MatrikonOPCExplorer.tra - trace for Matrikon OPC Explorer

OPC Server is x86, Client side is 64 bit.

During added tag in Matrikon OPC Explorer getting error:
OpcTestLab.OpcAnalyzer.1 caused COM/OPC error 0x80040202 on IConnectionPoint.Advise()
GetErrorString() on IOPCServer not implemented or could not resolve error string!
Error string: Could not resolve OPC error code
Additional: Could not establish data callback connection on group ''
Interface address is 0x00DB249C
Vendor detail: Matrikon Inc +1-780-945-4011 www.matrikonopc.com

Hello,

see:
- kb.opclabs.com/Collecting_information_for_troubleshooting
- kb.opclabs.com/How_to_use_OPC_Analyzer

I will send you a download link to the email address you have used to register with the forums.

Remember to capture the smallest example possible (only minimum amount of items/time required).
It would be beneficial to also have the capture from the client that you claim works well (Matrikon Explorer).
Regards

Hello,

please try this (at the beginning of the program - before any OPC operation are made):
If that does not help, I'd suggest to use OPC Analyzer (we can help with that) to figure out what precisely goes on between the client and the server.

Best regards