Sam Taggart

was this ever resolved, because I am currently having the same problem.

thanks Jim!

I have a library with some VIMs and regular VIs. On the Display information Screen in the package builder I have Edit All VI Descriptions checked. My regular VIs get the copyright notice added, no problem. The VIMs don't. I am using VIPM PRO 2019.0.0.0. Checked for an update. It says I have the latest. Source Code is in LV19.0f2 if that helps. I suspect the vim file extension may be causing the issue. I attached a simple reproduction. thanks for creating such a great product! Sam VIM Descr Issue.zip

Jim, Here is a simple example. Note it appears that also text files (and perhaps any non-LV files) are affected. The .vipb file is from 2017. Sam Simple Example.zip

I am recieving the same Build failed during "source distribution step" dialog box Here is what the error log file says: =========== START of VIPM Error Message =========== An internal VIPM Error has occured on: Thursday February 04, 2010 at 01:02:53 PM = Automated Message Start = Error 1031 occurred at Open VI Reference in Filter Illegal File Names__ogb.vi->Generate Resources Copy Info__ogb.vi->Build Application__ogb.vi->Build Application from Build File__ogb.vi->Build Application from Build File__ogb.vi.ProxyCaller Possible reason(s): LabVIEW: VI Reference type does not match VI connector pane. VI Path: C:\Program Files\National Instruments\LabVIEW 2009\vi.lib\Utility\libraryn.llb\Is Name Multiplatform.vi = Automated Message End = = Error Handler Call Chain Start = 54D2245E470720481F84F1814A9A98B9-> 4E7C998AE57AE1D967DF0265A668032E-> 91E96C108F86D9E95051E7FA71E90326 = Error Handler Call Chain End = =========== END of VIPM Error Message =========== any ideas?