Oh, thank you very much. I was now able to reproduce the problem. The item that causes the problem is:

• SimulateEvents.ConditionState1.AttributeValues.15409166

(there may be more).

After investigation, the nature of the problem appears to be as you reported - but it turns out to be on the server side. The server is supposed to return the errors "one by one", and it normally does that - but not in this particular case; instead, it fails the whole "Read" call which contains multiple items, and therefore nothing useful can be returned for any item contained in the call.

This is clearly a server bug, and I will investigate and eventually fix it too. But there is nothing that should or can be fixed on the client side.

It will work well with other servers.

Best regards

Yes, if one item is somehow "wrong", only the result for that item should indicate a failure.

But you have made a logical shortcut somewhere. What makes you think that one item is wrong? There is nothing that implies that, in what you have written. It looks more like that you have something wrong in all of them.

I cannot reproduce the problem. Can you send a full code that shows the problem?

Regards

Thank you for additional information.

But, how do you know that "one item is wrong", if you have taken all of them and treated in the same way?

Regards

Hello,
can you please respond? I would really like get to the cause of this issue.

Best regards

Hello.
More to this: I understand what you are saying, but which of the items in your inputs is 'wrong", and in which way?

How can I reproduce it?

Thank you

Which QuickOPC version are you using please?