I have the same or similar issue. I couldn't narrow down exactly where it fails, seemed asynchronous for me.
The BrowseServers workaround didn't work for me.

version 5.53.405
Visual Studio 2019 v16.0.31025.194 D16.9
Windows 10 version 20H2 (OS Build 19042.867)
32bit .NET 4.5.2
connecting to Intellution.OPCiFIX

Used to work ok, then didn't use the VM for a couple years. Now doesn't work. Visual Studio and Windows 10 updated a number of times.

I switched to using Nuget, which didn't fix it for the same version. Then kept updating the version until version 5.58 (2020.2) fixed it (and 5.60 works too). I had to change to use .NET Framework 4.7.

I feel like that's probably my only solution, and just wanted to put that in here in case it is affecting anyone else or maybe someone has some insight into this.

Hi,
so I figured out a solution to the problem , I still don't know the root cause but This is the solution I found:
all I have to do is to is to call:

var easyDAClient = new EasyDAClient();
easyDAClient.BrowseServers();

If I start reading the data(using easyDAClient) like so:
_easyDAC.GetMultiplePropertyValues(Parameters.OPCIP, Parameters.OPCServerName, tag, _propertyIds)

without loading the list of servers first, the application is crashing.
I do not know the root cause for this crash, and I am unable to debug it.(I have tried enabling all of the exceptions) but this is the solution I found, if you can please try and reproduce it It would be a great help.

Regards,
Roie Beck

Hi all,
I am new to OPCLabs And I have a WPF client that is connecting to a server,
the connection works OK,
however , if I start the app without loading the OpcServerDialog() & showing it, the application crashes after I stop taking measurements from the OPC server(by pressing any button in the WPF UI).
the only way to avoid is is to show the OpcServerDialog before starting to get measurements from the server, but I would like to avoid the need of opening it every time I load the Application,
also no exception is thrown, I only see the following in event logger(below)
again, problem can be solved via opening the OpcServerDialog which I guess load the DLL's necessary,
Can you please help?
Regards,
Roie Beck

Faulting application name: EMU.App.vshost.exe, version: 14.0.23107.0, time stamp: 0x559b788a
Faulting module name: ntdll.dll, version: 10.0.15063.608, time stamp: 0x8274fd8b
Exception code: 0xc0000008
Fault offset: 0x00000000000a917a
Faulting process id: 0x2efc
Faulting application start time: 0x01d35160753bea8b
Faulting application path: C:\Siga\Repositories\SigaGuard\APP\EMU\EMU.App\bin\Debug\EMU.App.vshost.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 98e642de-846d-4e88-81e8-61e392d190a5
Faulting package full name:
Faulting package-relative application ID:

Duplicate , sorry

duplicate , sorry

Hi All,
I am a new OPCLab use. and I am currently using OPC-DA server & a WPF client App,
problem is: after reading a few tags(like so):
_easyDAC.GetMultiplePropertyValues(Parameters.OPCIP, Parameters.OPCServerName, tag, _propertyIds)
the application crashes when pressing a button, it only happening when I use the OPC device, no other device does it and I am also reading from Phoenix modbus, labjack etc...
I think it has something to do with me being force to upgrade to .NET 4.5.2 in order to use OPCLabs nugets (we were at .Net 4.5 prior to this), no exception is caught & the application just crashed, In the event viewer I can see the following(below)
I am also attaching the memory dump and additional log files from the crash,I have tried looking in google but nothing related to OPClabs came up.


Faulting application name: EMU.App.vshost.exe, version: 14.0.23107.0, time stamp: 0x559b788a
Faulting module name: ntdll.dll, version: 10.0.15063.608, time stamp: 0x8274fd8b
Exception code: 0xc0000008
Fault offset: 0x00000000000a917a
Faulting process id: 0x2efc
Faulting application start time: 0x01d35160753bea8b
Faulting application path: C:\Siga\Repositories\SigaGuard\APP\EMU\EMU.App\bin\Debug\EMU.App.vshost.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 98e642de-846d-4e88-81e8-61e392d190a5
Faulting package full name:
Faulting package-relative application ID: