Data Socket related Crash

[viScience]

Greetings,

I have an LV 8.6 HMI that performs Data Socket reads from Network Shared Variables. I am finding that it works well until I try to shut down and close all the DS references. I can usually get away with this
once, but if I try to restart the application I often will not be able to reopen the DS reference and it will always crash when I try to shutdown again. I have narrowed it down to just DS opens and closes
and the problem persists. Attached is the error message that pops up when LV crashes, not much to go on but any ideas would be greatly appreciated.

[Andrew_E]

Hello,

Which version of Windows are using? There are some cases in the past with NT that relate to this error because windows was updated. A Microsoft KB explains that here.

This also may be an issue with the Shared Variable Engine having a conflict with the firewall or antivirus software. You may need to go through this document to configure your windows firewall if you already have not.

[viScience]

Ok, I have narrowed down the problem somewhat... In my HMI application I have both static NSV's and dynamic (call by URL) NSV's.  If I remove all of the static NSV's then

the app does not crash,  If I include a single static NSV then the SV library is autodeployed and this sets up the app to subsequently crash.  It appears that there may be a race

condition between performing the Datasocket Open's and when the runtime autodeploys the NSV library which may confuse the SVE in regards to the dynamic SV references

that I have generated.  Perhaps there is a way to sequence the events so that the autodeployment happens first?