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.
Update to Version 2020.2
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
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
I hate to ask you for additional work, but since I cannot reproduce it, there aren't many other options.
Can you find out what are the messages and call stacks of the inner exceptions? That would probably require opening the solution with C# or VB.NET example source code, run one of the OPC-DA examples under debugger, and then examining the exception. But not just the highest-level one (you already gave me its text), but also what is in its .InnerException property (message and call stack), and if its InnerException is not null, then further deeper.
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.
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.
- Installed 2018.3, upgraded to 2020.2.
- Installed German version of WIndows 10, installed QuickOPC 2020.2
I still could not reproduce it.
1. How do you start the COnnectivity Explorer - is it from the Launcher app, under Tools?
2. What about other .NET-based apps in QuickOPC that use OPC Classic - do they work or what do they give? From the Launcher, can you please try Demo Applications (.NET) -> Demo Application (OPC-DA), then press "Subscribe item"?
No, I didn't try with another computer. This is my Development Device, and I need to get it working there.
But, I have two accounts on that device. I tried to deinstall and install in bot accounts, no change.
Any other thing you could recommend me to try, like cleaning the windows registry.
that's weird. You have the right version&build. I checked it also with your Setup log.
Unfortunately it works in my test (on a clean computer). I wonder whether it is not related to the fact that you have made an upgrade. Do you know which version you had before?
And, have you tried on some other computer?