felipefoz Posted May 31, 2023 Report Share Posted May 31, 2023 I am trying to locate where the problem is, but I can't find. Can anyone help with the error. I am able to build other packages, but this one particularly I can't. =========== START of VIPM 2023.1 (build 2499) Error Message =========== An internal VIPM 2023.1 (build 2499) Error has occured on: Wednesday May 31, 2023 at 12:33:52 PM = Automated Message Start = Error 7 occurred at Librarian Get Info.vi--Type and Creator Possible reason(s): LabVIEW: (Hex 0x7) File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct. ========================= Nonexistent GPIB interface. = Automated Message End = = Error Handler Call Chain Start = VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi.ACBRProxyCaller.B230004E-> VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi-> VIPB.lvclass:9D3CA612B30CF474171422C252AF2CEA-> EEA2B7938246E410B129865C9BAEBDD0 = Error Handler Call Chain End = =========== END of VIPM 2023.1 (build 2499) Error Message =========== Quote Link to comment Share on other sites More sharing options...
ShaunR Posted June 2, 2023 Report Share Posted June 2, 2023 (edited) I just ran into this but didn't have half of the text you have. It's not just 2017, it's all versions. It was caused by LLB's (in my case). It's caused by "Librarian Get Info.vi" (as it says in the error) and is because during validation it seems to use that function to check if an LLB is a valid file. It fails with error 7. That function is supposed to only be used with files within an LLB. I unpacked/converted the LLB's into directories (there are a few of them) and it successfully built after that. That's not a solution for me but may be fine for your project. Edited June 2, 2023 by ShaunR Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted June 19, 2023 Report Share Posted June 19, 2023 Hi @felipefoz (and @ShaunR). Thanks for posting this. Would you be willing to test to see if this is resolved in VIPM 2023 Q3 (build 2513 or later)? Details and download here: Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.