Colbrunn

To add more data to this. Not only does the path to the .rtm get messed up in the library, but it also gets messed up in the vi/control itself. The path that it is looking for the .rtm file is in the temporary folder that VIPM uses when it builds the package. For example: (C:\Workspace\.Package) where the Package folder has the period after it. So, it seems to me that when VIPM does the install and then LabVIEW compiles everything, the rtm file paths are not re-referenced as part of that recompile process. Our work around was to save the menu with the control itself and not as a separate file. This is fine if the menu is only used in one location. It is a pain if it is used in multiple controls (which is why a .rtm file is handy). BTW we also tried with the latest VIPM package and it still has the same issue. I am wondering if this is supposed to have been addressed, or there is a plan to address?

Did this ever get resolved? I am experiencing this now. I have tried it with VIPM 2021.0 build 2750 and 2754. We have not seen this before. I looked through the VIPM release notes I could not find this fix mentioned.

Same error here on multiple computers. At first we thought our IT department rolled out something that caused the issue, but based on what I am seeing here it looks like something is corrupt with one of the AWS servers. I suspect the JKI crew is diligently working on it as it is effectively a worldwide outage for VIPM until they get to the bottom of it.