Hello,

you can use the CORFLAGS utility (learn.microsoft.com/en-us/dotnet/framework/tools/corflags-exe-corflags-conversion-tool ) with the -32BITREQ+ option, applied to the .exe of the ConnectivityExplorer, to force it to run in 32 bits.

You can verify how ConnectivityExplorer runs using Help->About; at the bottom of the About box, there is either "32-bit process" or "64-bit process".

Re "If I cannot run 32Bit python, is there a way that QuickOPC can bridge this gap?", there currently is no other known way; but as I wrote, if we got access to actually investigate in detail the computer with DeltaV server, there *might* be a way.

Best regards

Hello.

There are issues with DeltaV OPC server due to how it is registered in the system. Most OPC clients are 32-bits and can connect fine. Clients developed with QuickOPC can be either 32-bits or 64-bits, depending on how the application is built/run. If the OPC client runs in a 64-bit process, there are known issues connecting to DeltaV server.

See e.g.: support.softwaretoolbox.com/app/answers/detail/a_id/3972 .

Is your intent to do the OPC client in Python? If so, try switching to 32-bit edition of Python.

If we could get our hands on a DeltaV demo installable or a VM image with it, we might be able to develop a better workaround.

Best regards