- Posts: 16
- Thank you received: 0
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.
This issue should now be fixed - QuickOPC 2019.2, (5.56.)1055.1 or later. Please download the latest version form our Web site, verify the build number (on the first page of the installation wizard), install, rebuild and retest.
> QuickOPC does not support them, so you won't be able to read that node after the fix anyway.
I understand it. The main thing for me is to avoid an error. The fact is that we made a program with which users can try to read any tag they wish. And the main thing for us is to exclude the program crash.
[unrelated part removed]
I was able to reproduce the problem. This appears to be a bug in QuickOPC 2019.2. Thank you for reporting it.
There will be a fix (a new build). Please be patient - it may take some days. I will make another post here when it is ready.
Note that the problem has to do with reading values of type ExpandedNodeId that contain non-zero server index. QuickOPC does not support them, so you won't be able to read that node after the fix anyway. The proper behavior is that a non-null .Exception appears in the corresponding element of the array returned from ReadMultiple or ReadMultipleValues.
On your PC, the error does not occur when reading the tag "ExpandedNodeId"?