That is a possibility at least theoretically, though it would be wiser to convert it to a virtual machine instead.

There is an issue, however, that due to vacation, between July 3 and July 10 no actual investigation/testing/development work can be done.

Then, most likely, the OPC Server is not compliant with the spec, because there is just a limited set of OPC methods that are allowed to be "Not implemented" (return E_NOTIMPL), and we call those only when you have a corresponding EasyAEClient method call in your code - which is not the case here.

In order to find out precisely what is happening, unfortunately the Team Viewer would not be enough. We would need to be able to access the server through OPC A&E from our test/development computer, so that we can debug inside the client and see the responses of the server (there are tools to analyze the OPC DA communication, such as OPC Analyzer from OPC Foundation, but unfortunately not for OPC A&E).

Isn't there a way to obtain a demo version for test?

Hello.

After checking in detail how the Refresh call (which most likely is not implemented in your OPC server) is handled, I have found that there are ways you can suppress its calling in QuickOPC, which should hopefully resolve this problem.

One way to do it is to specify RefreshWhenActive = false in the call to SubscribeEvents. Here is an example of how it may look like:


Please try this.

Another way to achieve similar outcome is to exclude the condition events from the event filter.

We may still change the E_NOTIMPL handling of the Refresh() result, but because there are ways to work around it, it will only go into a subsequent QuickOPC version.

Best regards

Thank you. Before we consider some kind of remote analysis, I'd rather make one change on our side. We will allow the suspect non-critical OPC call or calls (the Refresh method, mainly) to return "Not implemented" without that rendering the whole subscription as failed. The plan is to change the software (please allow several days) and post a new build.

I will let you know here on the forums when this is available or when there is more information to this case.

Best regards

The error code corresponds to "Not implemented" (i.e. some method, by the OPC server).

Which OPC server are you using? (vendor, model)
Is there a trial version of it that we can test here?

We might be able to make the client part more "forgiving" and work even when something is not implemented on the server, but we need to analyze the OPC communication details first.

Best regards