Error 66 while building VIPM package [cross-post]

[Antoine Chalons]

(message first posted on jki forum, but traffic there seems very low...)

I get this error when building my package with VIPM, previously the package was building fine.

It always took a long time (~15 to 20 minutes) to build this package because it's quite large (~78 classes, 1200+ VIs).
Since the last successful build I've only added some methods in the classes.

Mass compiling the folder containing the source code doesn't report any issue.

Error 66 is descibed in LabVIEW as 'The network connection was closed by the peer. If you are using the Open VI Reference function on a remote VI Server connection, verify that the machine is allowed access by selecting Tools>>Options>>VI Server on the server side.'

I've check this and other (smaller) package still build fine.

Sources are in LV 2019 32 bit

I'm using the latest version of VIPM 2021.1 b2754

Any suggestions?

Edited November 11, 2022 by Antoine Chalons
link to cross-post

[Antoine Chalons]

I enabled the "Do Not Compile on Build" option (in Source File Settings section) and the package building worked
and took a lot less time than before

As I mass compile my source folder anyway before building the package, am I risking anything?

Why is this option "not recommended"?

[Rolf Kalbermatter]

On 11/11/2022 at 2:18 PM, Antoine Chalons said:

Why is this option "not recommended"?

Well, my guess is that it is normally a lot safer to compile everything than to trust that the customer did a masscompile before the build. That automatic compile "should" only take time, not somehow stumble over things that for whatever strange reasons don't cause the masscompile to fail. That's at least the theory. That it doesn't work out like that in your case is not a good reason to make it recommended for everyone to do it otherwise.

[Antoine Chalons]

well, there might be a little more to it.

when this option is enabled, the package build goes through but the "rename" was skipped ; unless I completely misunderstand the feature,  I see that as a bug.