- Posts: 60
- Thank you received: 1
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.
Selected data can be transferred to Excel, where it continues to stay subscribed, giving cell values that are dynamically updated with live OPC data.
EasyDAClient Exception in Connectivity Explorer
I have found the problem. We are including (and also instructing the users to install if necessary) a wrong version of Visual C++ libraries. We will fix this in the upcoming version (2020.3). Until then, there is a simple workaround:
1. Visit support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads .
2. Scroll down to find the heading "Visual Studio 2015, 2017 and 2019".
3. In that paragraph, if you are on 32-bit machine, download and install x86: vc_redist.x86.exe . If you are on a 64-bit machine, install the previous as well, and *also* download and install x64: vc_redist.x64.exe .
no need to pursue the VM way. I managed to reproduce the problem!
It seems that the distinguishing factor is whether Visual Studio is installed or not. When it is not installed, the problem manifests itself. I have not discovered this earlier because I normally use baseline VM images that already have Visual Studio in them.
So, I will now investigate on my side.
and best regards
The file specified is not a virtual disk Cannot open the disk 'D:\TechSupport\2933\Windows10-1903-flat.vmdk' or one of the snapshot disks it depends on. Module 'Disk' power on failed. Failed to start the virtual machine.
I have shared a zipped folder with you through Dropbox at the email address you shared. The folder contains the VMX and VMDK files. Please let me know if you need anything else.
Initially, I did install 22.214.171.124 first and then 126.96.36.199 over it because that is what my customer did and this replicated the issue, but this morning I rolled back the VM to factory default and installed just 188.8.131.52 and the issue was replicated.
it is very good that you have it reproduced in a VMWare VM.
You can use dropbox and email to support09 (at) opclabs.com, or I can open an FTP server for you.
But, I have spotted something in your text: Is this only only happening if you install 184.108.40.206 first? That is, you actually *had* to do it, otherwise you wouldn't be able reproduce it? But, installing 220.127.116.11 on a fresh VM would work fine?
If so, it might be an installation issue, which would direct me in looking for the cause. And, it would explain why I was not able to reproduce it - because I do not normally bother installing older builds first.
I have now replicated this issue with 18.104.22.168 on a VM. I used VMware. Is it just the VMX and VMDK files that you'll need? I will try to upload it to a dropbox account. Is there an email address I can send the link to?
I replicated this by installing 22.214.171.124 to a fresh Windows 10 (10.0.18362) install. This had the issue, as expected. Then I installed 126.96.36.199 over it and the issue remains.
There was an issue in that specific build ( 188.8.131.52) that has been fixed.
Interestingly, I have another customer (but just one) who is reporting the same or similar issue. He is very cooperative, but I still was not able to reproduce it. I even installed the precise Windows version he had. He then tried to deliver VM image (manifesting the problem) to me, but this has failed as I only have Microsoft and VMware virtualization software, and he was using something different which in the could not have been imported.
So, I can try to reproduce on the Windows the customer has, but I am afraid it won't show either.
Can you yourself reproduce it? Can you, or the customer, provide a VM image (in Microsoft or VMWare formats) with the problem?
I have a customer who was using 184.108.40.206 and encountering the following error every time the Connectivity Explorer is run:
The type initializer "OpcLabs.EasyOpc.DataAccess.EasyDAClient" threw an exception.
I saw in another forum post that this was resolved already, so I had them install 220.127.116.11; however, the issue still exists. I have attached some screenshots from the Event Viewer that were thrown along with the error.
I am waiting to hear back on what the OS version and installed .NET Frameworks are, but wanted to go ahead and get this posted.