Hi!
We are using QuickOPC-5.34 in a way that we subscribe to changes through IEasyUAClient.SubscribeMonitoredItem() during initialization, and rely on QuickOPC to reconnect to the server when the connection was lost. When restarting the remote Kepware server however, sometimes the reconnection happens, but usually the connection is lost forever.
Is it the normal behavior? If it is a bug, was it fixed in later versions? How can I get the bugfix?
I also tried to use later versions (5.35 and "OPC Labs QuickOPC 2016.2"), but then the exact same test program which works with 5.34, fails with this:
The program '[0x37BC] test_quickopc.vshost.exe' has exited with code -1073741790 (0xc0000022).
If there are threads, all those threads are cancelled with the same HRESULT. Can it be some kind of licencing error?
LicenseManager.exe shows an installed license on my machine, but it has:
Release date covered: 2017-01-07
Version number covered: 539
Thanks,
Andrew
We are using QuickOPC-5.34 in a way that we subscribe to changes through IEasyUAClient.SubscribeMonitoredItem() during initialization, and rely on QuickOPC to reconnect to the server when the connection was lost. When restarting the remote Kepware server however, sometimes the reconnection happens, but usually the connection is lost forever.
Is it the normal behavior? If it is a bug, was it fixed in later versions? How can I get the bugfix?
I also tried to use later versions (5.35 and "OPC Labs QuickOPC 2016.2"), but then the exact same test program which works with 5.34, fails with this:
The program '[0x37BC] test_quickopc.vshost.exe' has exited with code -1073741790 (0xc0000022).
If there are threads, all those threads are cancelled with the same HRESULT. Can it be some kind of licencing error?
LicenseManager.exe shows an installed license on my machine, but it has:
Release date covered: 2017-01-07
Version number covered: 539
Thanks,
Andrew