Jump to content

Search the Community

Showing results for tags 'repositories'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Special Interest Boards
    • Professional User Interface Design in LabVIEW
  • VI Package Manager (VIPM)
    • VI Package Manager (VIPM)
  • JKI Tools
    • JKI Flat UI Controls
    • JKI Design Palette
    • JKI State Machine
    • JKI State Machine Objects (SMO)
    • Caraya Unit Tester
    • VI Tester
    • JKI JSON
    • HTTP REST Client
    • JKI Simple Localization
    • EasyXML Toolkit
  • Legacy Tools
    • Legacy Tools

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. 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.
  2. After starting VIPM 2019, I get an error when checking for updates: " there was an error accessing the following repositories:" LabVIEW Tools Network and VI Package Network. I have been using VIPM 2019 ever since it came out and have not seen this issue until now. I have checked for update and I am running the latest. I have checked with my IT guy and there is no web filtering that would be causing it not to get through.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.