Issue scripting module includes

[theSloopJohnB]

I'm testing out the OPC UA package and ran into some issues when scripting the module includes when I'm using OPC UA.

Also, more minorly:

I don't feel good about including this in the release with this issue. I've asked @dbendele to reproduce on his setup.

[dbendele]

reproduced when including OPC UA module in 2017 project.
following error observed when scripting module includes VI:

[jacobson3]

@dbendele and @theSloopJohnB Can you let me know what steps you took to get this error? I can try it on a clean system and try to figure out what is happening. If you can also attach a max tech report for the system which throws this error that would be nice.

[a-clucker]

@dbendele and @theSloopJohnB - bumping this thread. Can you help him? @jacobson3 is halted until he gets repro steps. And as I understand it putting this module on VIPM is halted until this gets resolved.

[Linnaeus-Ling0]

Hi, I recently joined in order to present my fix. I wanted to use this module, but also came across the same error as the first post. After some debugging, I found that the execution class name does not contain the correct filename for the runtime class, which should be OPC UA Client runtime.lvclass found in C:\Program Files (x86)\National Instruments\LabVIEW 2017\vi.lib\NI\DCAF\Modules\OPC UA\module\execution. To fix this yourself, do the following:

In file explorer go to:
C:\Program Files (x86)\National Instruments\LabVIEW 2017\vi.lib\NI\DCAF\Modules\OPC UA\module\configuration
If you use a different version of Labview, replace "LabVIEW 2017" with your own version.
If you use the 64bit version of LabVIew, go to C:\Program Files, not C:\Program File(x86)

Open "execution class name.vi"

In the class name text box, add the word Client in between the words "UA" and "runtime". It should now read OPC UA Client runtime.

Save and close the VI

Generate the Includes file as usual, and it should succeed this time. You should see OPC UA runtime in the Includes block diagram.