Jump to content

Sam Taggart

Members
  • Content Count

    19
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by Sam Taggart


  1. Here is the whole error if that helps:

    =========== START of VIPM 2020.0.0 (build 2302) Error Message ===========
    An internal VIPM 2020.0.0 (build 2302) Error has occured on: Friday May 22, 2020 at 10:37:10 PM

    = Automated Message Start = 
    Error 42 occurred at (http response "404". URL Requested: 
    http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/austin_consultants_lib_finance_ohlc_plot/aus
    tin_consultants_lib_finance_ohlc_plot-1.1.0.14.spec) 85294761631CBC58471969C9E99FB95F:2980001 in 
    34ECF0FD9B9E81860D3E52C65FD0A442->15A1868D1CB3D6176D9B44B0ED323314->C898E814D7E422D8CA4487CB97FA7465
    ->OGPM Class.lvlib:0A647C51DBC1AD7225F71A08D470BB08->OGPM 
    Class.lvlib:4CD02F4728B5353B72E37139092E0B05->E1F6385E95370507176402E569A529D7->VIPM Main Window.vi
    . URL: 
    "http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/austin_consultants_lib_finance_ohlc_plot/au
    stin_consultants_lib_finance_ohlc_plot-1.1.0.14.spec".
    Possible reason(s):
    LabVIEW: (Hex 0x2A) Generic error.
    = Automated Message End =

    = User Defined Message Start = 
        Error downloading package info
    = User Defined Message End =

    = Error Handler Call Chain Start =
        VIPM Main Window.vi->
        E1F6385E95370507176402E569A529D7->
        OGPM Class.lvlib:4CD02F4728B5353B72E37139092E0B05->
        OGPM Class.lvlib:0A647C51DBC1AD7225F71A08D470BB08
    = Error Handler Call Chain End =
    =========== END of VIPM 2020.0.0 (build 2302) Error Message ===========


  2. On 5/22/2020 at 10:17 AM, Jim Kring said:

    Hi Sam. VIPM 2020 works a little bit differently. It hangs around in memory for a little bit in case someone uses it again -- this way, it's much more responsive. Yet, it's changed the observed behavior around exactly when the package list refreshes.  This is something we're working on and should be improved in the next release.

    I would mark this as an improvement since in the past it could sometimes take a while for VIPM to refresh everything.

     

    I am quite happy with the design palette at the moment, but if I think of anything I will let you know.

    • Like 1

  3. I have a library with some VIMs and regular VIs.  On the Display information Screen in the package builder I have Edit All VI Descriptions checked.  My regular VIs get the copyright notice added, no problem.  The VIMs don't.

    I am using VIPM PRO 2019.0.0.0.  Checked for an update.  It says I have the latest. Source Code is in LV19.0f2 if that helps.  I suspect the vim file extension may be causing the issue.

    I attached a simple reproduction.

    thanks for creating such a great product!

    Sam

    VIM Descr Issue.zip

    • Upvote 1

  4. I am recieving the same Build failed during "source distribution step" dialog box

     

    Here is what the error log file says:

     

    =========== START of VIPM Error Message ===========

    An internal VIPM Error has occured on: Thursday February 04, 2010 at 01:02:53 PM

     

    = Automated Message Start =

    Error 1031 occurred at Open VI Reference in Filter Illegal File Names__ogb.vi->Generate Resources

    Copy Info__ogb.vi->Build Application__ogb.vi->Build Application from Build File__ogb.vi->Build

    Application from Build File__ogb.vi.ProxyCaller

    Possible reason(s):

    LabVIEW: VI Reference type does not match VI connector pane.

    VI Path: C:\Program Files\National Instruments\LabVIEW 2009\vi.lib\Utility\libraryn.llb\Is Name

    Multiplatform.vi

    = Automated Message End =

     

    = Error Handler Call Chain Start =

    54D2245E470720481F84F1814A9A98B9->

    4E7C998AE57AE1D967DF0265A668032E->

    91E96C108F86D9E95051E7FA71E90326

    = Error Handler Call Chain End =

    =========== END of VIPM Error Message ===========

     

    any ideas?

×
×
  • Create New...

Important Information

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