Stobber Posted June 10, 2014 Report Share Posted June 10, 2014 I can use "Read VI Package Build Spec" to get my Package Version cluster from a VIPB file. If I pass that cluster into "Write VI Package Build Spec" and the major version is 0, the latter VI throws error 42 with the message "VIPM API_vipm_api.lvlib:Check Build Spec Input_vipm_api.vi<ERR>The package version cannot be 0 (zero) for the major number or the build number." That's not true in VIPB 2013 or 2014, though. I have several pre-release packages with majorVersion = 0, and I can build them in the VIPB UI just fine. Is this a legacy constraint or a bug in the API logic? Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted June 14, 2014 Report Share Posted June 14, 2014 Sorry. This is a legacy issue with the VIPM API VIs. We'll be releasing a new version in the next few weeks to address this issue. Link to comment Share on other sites More sharing options...
Satheeshvarma Posted March 14, 2018 Report Share Posted March 14, 2018 Hi, I am using VIPM API version 2017.0.0.55 and still getting this error. Is this issue addressed? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.