You need to contact the vendor of the product you are using. The likely outcome is that he would instruct you to use a newer version.

Best regards

Hello.

Are you also connecting to Delta V OPC server?
Which QuickOPC version are you using?

Thank you

Added experimental code that directs the OPC DA node browsing to the NET API implementation (and not the standard "raw" implementation) when OPC DeltaV server is detected.

Built demo app with the experimental code. According to the customer it works OK (node browsing).

Will make a new QuickOPC 2020.1 build with this change (and also some tracing added in the meantime) - will be in builds 125.1 or later.

Regards

Memo: Remote session to customer's site performed on 202003190600.

64-bit machine.
Demonstrated problem with EasyOpcNetDemo app built with 5.41.1253.1. Shows "Class not registered" when attempting to browse nodes of OPC.DeltaV.1, runs in 64-bit process though (Michael's app runs in 32 bits). Used CORFLAGS with -32BIT+ /FORCE to switch EasyOpcNetDemo to 32-bit mode. After that, it gives "Object is not connected to server" in the same situation.

Tested with SOClient (is 32 bit). Works OK. Has no OPC DA 3.0 interfaces. Obtained OPC Analyzer trace of that.

Tested 32-bit EasyOpcNetDemo with OPC Analyzer. Unfortunately, it works OK. Obtained OPC Analyzer trace of that.

Server info from server browsing in the demo app:

Technology: OPC-COM
Implements: (OpcDataAccess10, OpcDataAccess20)
Vendor: Fisher-Rosemount Systems Inc.
ProgID: OPC.DeltaV.1
Version-independent ProgID: OPC.DeltaV.1
CLSID: {c3b72ab1-6b33-11d0-9007-0020afb6cf9f}
URL: opcda:OPC.DeltaV.1/%7Bc3b72ab1-6b33-11d0-9007-0020afb6cf9f%7D

Aside from browsing, when ItemID is entered as a string, reads work OK, subscriptions work OK.

Used REGEDIT to explore the registration. 64-bit registry has the ProgID part but not the CLSID part. 32-bit registry has the CLSID part but not the ProgID part. Target executable is FrsOpcDv.exe. Attempted to fix the 64-bit usage by copying the CLSID part to 64-bit registry, but that gave no change in behavior.

No suspicious entries in Windows event logs. The server process appears to be running the whole time (before and after the problem occurrence - no crash).

Later, the customer installed QuickOPC 2020.1 (build 114.1) and retested with its demo app. Same behavior as with 5.41.1253.1.

Replied by email to this now.

Thank you.

Here is an outline of possible outcomes as I see them, also regarding the notes in email about version "2017" used in your software. It should be made clear that there is no way any change will be made to that old version.

0) We may not find a solution.
1) We will find a solution that works with version "2017" and does not involve any change into our software. Fine then.
2) We will find that the problem does not occur with our current version (2020.x). This is unlikely because there were not significant changes in that area. But if it happens, we will give you a license to the new version, free of charge.
3) We will make a change in our software to resolve the problem. In such case the change will be made to the new version, and we will give you a license to the new version, free of charge.

Regards