Leaderboard

VIPM 2020.3 (build 2540) I'm getting a bizarre error. I get a build failure where VIPM claims that the following source library is missing C:\Common\Generator Interface\Message Interfaces\Gen11 Message Interface\Gen11 Message Interface\Gen11 Message Interface.lvlib When the library actually is located here. C:\Common\Generator Interface\Message Interfaces\Gen11 Message Interface\Gen11 Message Interface.lvlib This library is a collection is actor message interface classes if that makes a difference. I'm also been able to do a mass compile of the entire directory without any errors. This might not be related, or a quirk of the builder that I don't know about: The other weird thing is if I open the project while VIPM is in the failed state, the error list contains a bunch of failed VIs that couldn't find a .NET library located within my project. (This project is pretty big and contains some proprietary information so I can't upload it. Sorry, that makes it hard to troubleshoot.)

Thanks for posting the screenshot. What does the dialog show after you press OK? It should indicate the caller of that missing vi. it’s hard to know for sure if A mass compile of your Source folder would fix the issue. Possibly, yet sometimes the linkages can be crossed up across different projects.

Does the VIPM error dialog state which calling VI is trying to find that missing VI? The dialogue has two parts: one that shows you the missing VIs, and the second that shows you which project source VIs are calling the missing VIs also, often the culprit is a VI on disc that is not actually being used anymore, but it’s broken. The package builder is including it, even though it’s not being called by anyone

My apologies. The option "Disable Built-in Subscriptions: LabVIEW Tools Network and VI Package Network" on the Network tab was checked by default. I unchecked that box and then had no problems installing. Such a newbie problem!

I just emailed you some instructions. I did this privately, since the steps involved are tricky and I don't want anyone trying this at home without a safety net.

Hi @Horsechilli I saw this happen recently, too, and it was also in LabVIEW 2017. I'll gather my notes on this to try to help you out. Stay tuned... -Jim