Problem with Shared Variable Engine after Windows Update from June 13th 2017

[User002]

We are running an OPC-Client/Server set-up on our lab computer using the NI-OPC-Client VI and Beckhoff PLC as OPC server on LabVIEW 2014 SP1 and latest patch. This had been working without issues till the Windows 10 Update from 13^th June.  After the update of windows 10 (KB4022725) the computer in the lab is facing issues namely:

1. Local shared variables are not being displayed under the process names in the distributed system manager. Even though the NI Tagging Service is running.
2. NI-OPC-UA-Client.lvlib: Connect.vi is giving an error within our LabVIEW program. The error – 356629 is being shown with comment “an operating system resource is not available” (Hex0xFFFA8EEB). We are noticing that the VI is not executing properly and hence our code to communicate with the OPC server (Beckhoff PLC) is not executing either.

Another point we have noted is that the same code is working properly when run from a laptop also running windows 10 with same updates.

Following are the characteristics of the desktop in the lab and the laptop:

Desktop:

• Intel Xeon, W3550 @ 3.07 hz 3.06 Ghz
• RAM 8 GB
• 64 bit OS with x64 Processor
• Data Acquisition Devices connected: PXIe -4357,6363
• Windows 10 enterprise with update KB4022725

Laptop:

• Intel Core, 15-6300 2.4 Ghz
• RAM GB
• 64 bit OS with x64 Processor
• Windows 10 Home

Anyone having similar issues after the updates or has tips to solve the problem ??

Thanks and best wishes from Offenburg, Germany

[Bob_Schor]

I found this on the Web --

Microsoft rolled out cumulative update KB4022725 for Windows 10 version 1703 on Patch Tuesday, addressing a series of issues affecting the OS. Unfortunately, users report that this update brings quite a few issues of its own, with some of these bugs can even breaking computers.

Bob Schor

[User002]

Thanks for the reply. We updated our system to LabVIEW 2016 and now it the shared variable engine is working again 🙂