drjdpowell

Confirmed this error on LabVIEW 2017 (no SP1 yet), and VIPM 2017.0.0f1. I'll try it on LabVIEW 2017 SP1 in a few days.

Interestingly, I have a couple of VIMs that contain other VIMs, and they don't produce this error. Only the VIs that call VIMs do.

I have the exact same issue: At the moment, I'm only calling VIMs inside my Examples, and so I'm excluding Examples from the package temporarily.

Note that if you do this you are committed to making sure that any sequence of “states” you call must be able to handle any possible external interruption at any point. In other words, you must be super vigilant against race conditions. With the “idle” method, one can choose where in a sequence of steps one will accept outside input. For example, if you had the macro: Take Data Analysis Data Save Analysis and also a “Set Parameter” event that changes a parameter used in Analysis and Save, then you have a race condition where the analysis may be saved with a different parameter value, if the “Set Parameter” happens between Analysis and Save.

I think I am having the same issue. When is the next VIPM service pack expected? And is there a work around in the meantime?