Search the Community
Showing results for tags 'openg'.
Found 4 results
Hi JKI team, We have created an internal tool to automate the process of package installation through VIPM. We sometimes receive an error pop-up stating that the VI Package Network could not be accessed (refer image below) This pop-up (which occurs randomly) affects our automation and does not allow proper/smooth package installation. We observed that when we check (select) the "Disable built-in subscriptions" checkbox under Tools -> Options -> Network, this pop-up could be avoided. But, this prevents downloading and installation of OpenG and other external packages (from different companies). Kindly help us with this issue. It would be nice if we get to know the reason behind this error pop-up and how to avoid/handle in automation. Thanks in advance.
Hi, I work for Texas instruments and we heavily use VIPM for Package deployment to 1000 + users. Recently we upgraded the VIPM to 2019 and of late (Probably last 8-10 months), we are seeing users reporting VIPM throws this error intemittently and have to retry couple of times to get through the package installation. The error says " There was an error accessing the following repositories 1. LabVIEW Tools Network 2. VI Package network 3. OpenG mirrors list" We know this error is coming because we use OpenG packages as reusables. Any suggestions to get this fixed.
The OpenG Array Library 126.96.36.199 is not listed in VIPM from the JKI Package Network. I even tried refreshing, but it did not find the required library. Other observations: 1. I am able to see an older version 188.8.131.52 of that library in VIPM 2. I checked the website and was able to find the latest version But I want to understand why my VIPM is not listing it