ThomasGutzler

I just encountered this error for the first time (but then 4 times in a row) for a large project that has built for a year on the same tool versions. It only happens on our build server. I can't reproduce it on my local pc. I'm running VIPM 2020.3 build 2540 with LabVIEW 2020 (20.0.1 64 bit) I followed Antoine's recipe but still get the same error ERROR: Error 1055 occurred at VIPM API_vipm_api.lvlib:Parse Build Return Message_vipm_api.vi Possible reason(s): Code:: 1055 Source:: Error 1055 occurred at Invoke Node in Library.Save__ogb.vi->Copy Project Library Files__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: (Hex 0x41F) Object reference is invalid. Error Conditions: Copy Project Library error: Source: C:\agent\_work\4\s\.src\xxx_class\xxx.lvclass Target: C:\Users\xxx\AppData\Local\Temp\vpbtmp\src\LabVIEW\instr.lib\xxx\xxx_class\xxx.lvclass The Project Library is linked to: FactoryCreate.vi (160 other files)

Hi, For my build servers I would like to avoid having to call Labview to run a vi that uses VIPM API to apply a vipc. Instead I would like to execute a command that does the same thing. I keep reading about the VIPM (File Handler) command line API but I can't find any documentation about it? Where is it? Cheers

Our build server fell over last Friday. Nobody noticed, this morning I am greeted with this: This is how it started: =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 05:29:08 PM = Automated Message Start = Error 2 occurred at Obtain Queue in JKI_LVConfig__jki_lib_configuration_file.lvlib:1188A4A91C005F423D89358A8C95F362->4F9D0428213F8F95FE3 A745133E46203->FF473C6B63ADACAEF90D52E8AFBDC45F->246E5055266A40F567071DB843B25FE8->1C008B1C8A190D0D7 176E93799F7534B->VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi:6610001->5AB213F9CD1875C24859DB C20A7CDE64->VIPB_API.BuildAndPackageLibrary.vi->VIPM API.lvlib:31462C1008B1B48A698808B4D0EE6D58->41AC743D0ED402FF42A432FD77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = User Defined Message Start = VI Package Builder Error = User Defined Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0-> VIPM API.lvlib:31462C1008B1B48A698808B4D0EE6D58-> VIPB_API.BuildAndPackageLibrary.vi-> 5AB213F9CD1875C24859DBC20A7CDE64-> VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi:6610001 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 05:29:10 PM = Automated Message Start = Error 2 occurred at Obtain Queue in JKI_LVConfig__jki_lib_configuration_file.lvlib:1188A4A91C005F423D89358A8C95F362->4F9D0428213F8F95FE3 A745133E46203->FF473C6B63ADACAEF90D52E8AFBDC45F->246E5055266A40F567071DB843B25FE8->1C008B1C8A190D0D7 176E93799F7534B->VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi:6610001->5AB213F9CD1875C24859DB C20A7CDE64->VIPB_API.BuildAndPackageLibrary.vi->VIPM API.lvlib:31462C1008B1B48A698808B4D0EE6D58->41AC743D0ED402FF42A432FD77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 08:57:05 PM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 08:57:05 PM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 08:57:05 PM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== And after that it's just this: =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Monday August 03, 2020 at 09:13:31 AM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== and continuing to fill. Task Manager tells me there are still 2GB of memory available

Always forward, Jim I don't want to bring up the "increased performance" argument. I mean, we're using LabVIEW after all. Nobody who's using LabVIEW can seriously play the performance card. I regularly see VIPM using over 1GB of memory and sometimes crashing with an "out of memory" error - although that might be due to the ridiculous 4GB of total memory available on that machine. How long before that goes to 2GB, 3GB? We've had 64bit on windows for 15 years now. I think it's time to move on. At least give us the option. Surely VIPM isn't depending on modules that don't exist in 64bit land

Please make a 64bit release of VIPM

Excellent, Thanks @Jim Kring. Is there a planned release date for VIPM 2020?

Has anyone from JKI seen this? @Ashish @Jim Kring I thought there might be some interest in fixing this bug

Here's an example I posted on lavag bits.zip