Hi,

we are using the Virtual Box from Oracle and Packer/Vagrant. Thus I could either provide an Export made by the virtual box (*.ova) or the initial packer/vagrant file.

All the best

Hi

I'm back again. I went trough a windows update Odyssee. Which anyway would have been necessary. With the result, that I have a complete new installation of windows 10, version 1909. No additional software, just one user account. And I get the same failure.

I than installed a new download (to avoid a corrupted download file) into a virtual machine. Ubuntu and within a virtual machine WIN10. I get the same failure there.

I than installed the 2020.2 version onto a different windows machine (our testbed) and there I don't get the error message.

Question: is there anybody else facing the same problem?

Way forward: I could provide the virtual box, thus you could have an environment in which the failure appears.

All the best

Hi,

I'm not using C# or VB.NET. Only the crazy applications like PowerShell with PowerShell ISE and/or Visual Core, VBA with the Macro-IDE and Python (com) also via Visual Code. I fear to setup the system and to clearly point to a failure message related to the current issue may take a while.

Thus I'm rather thinking of making a major windows update hoping that this will unlock the blockage. If the failure is gone afterwards, we don't know the root cause. But if nobody else has the same issue, then it is not worth to know.

What I can do during the update is, when re-installing the software and adding the additional user account, to install QuickOPC first and watch if any of the later activities lead to the same issue again.

I will let you know what the outcome is, but it may take a while to find a time slot for this.

Regards from Bremen

Hi again,

just for curiosity I de-installed version 2020.2 and installed version 2018.3 again. In version 2018.3 the connectivity tool works as expected.

I also checked the build version of windows, which is 1809 and which is still supported. But I think, this doesn't matter.

Regards

Good morning,

yes I start the Connectivity Tool from the launcher.

I tried to start any other OPC-DA, none of them functioned. The OPC-UA behaved as expected.

I'm working at the moment with the OPC-UA assembly in the .net framework. So far everything is fine. I don't know if I will see problems, when using Excel for Data visualisation. But I will see.

Ciao