Jump to content


Photo

Error 1 reported when using Publish Packages to Repository.vi from VIPM API

VIPM_API

  • Please log in to reply
10 replies to this topic

#1 RDR

RDR
  • Members
  • 17 posts

Posted 04 May 2016 - 03:45 PM

When using the Publish Packages to Repository.vi from the VIPM API I am receiving the following error text:

 
10:27:19.871 AM 5/4/2016 Error  1 at VIPM API_vipm_api.lvlib:Parse String Array Message_vipm_api.vi<ERR>
Code:: 1
Source:: (Invalid URL) E6C7850DB8DC443245FEA289ED5599DC in OGPM Class.lvlib:2298EAB45C3ADB6BA393ADD20A1567B2->Repository.lvlib:E4BDF9BD7B76EC63B78E078A2430E6BE->Repository.lvlib:412A7FE00073B5B996D6EC522E780BF5->VIPM API.lvlib:5F6CC0C4C5DFEC614D6E5B026429AAF0->2EDC3C81B4A2C6C7E1F2041B75CF3851->VIPM Main Window.vi 
 
This is code we've not changed at all--the error started to show up recently and we can reproduce this on multiple machines.  Some have VIPM 2014 and others VIPM 2015.  Do you have any recommendations for what to try next in debugging this error?
 
Thanks,
 
-RDR
 

  • 0

#2 RDR

RDR
  • Members
  • 17 posts

Posted 04 May 2016 - 04:05 PM

As an update, I can post to a different repository without issue.  This appears to be specific to the Tools Network repository--do you see any issue with the .vipr file?

 

ftp://ftp.ni.com/evaluation/labview/lvtn/vipm/index.vipr

 

-RDR


  • 0

#3 RDR

RDR
  • Members
  • 17 posts

Posted 04 May 2016 - 04:09 PM

Also, I am able to manually add packages to the Tools Network repo without issue--the error is only reported when using the API call.


  • 0

#4 RDR

RDR
  • Members
  • 17 posts

Posted 04 May 2016 - 09:44 PM

Here is what I found in the VIPM error log:

 

=========== START of VIPM 2014.0.2 (build 1976) Error Message ===========
An internal VIPM 2014.0.2 (build 1976) Error has occured on: Wednesday May 04, 2016 at 04:42:09 PM
 
= Automated Message Start = 
Error 1 occurred at (Invalid URL) E6C7850DB8DC443245FEA289ED5599DC in OGPM 
Class.lvlib:2298EAB45C3ADB6BA393ADD20A1567B2->Repository.lvlib:E4BDF9BD7B76EC63B78E078A2430E6BE->Rep
ository.lvlib:412A7FE00073B5B996D6EC522E780BF5->VIPM 
API.lvlib:5F6CC0C4C5DFEC614D6E5B026429AAF0->2EDC3C81B4A2C6C7E1F2041B75CF3851->VIPM Main Window.vi
Possible reason(s):
LabVIEW:  An input parameter is invalid. For example if the input is a path, the path might contain 
a character not allowed by the OS such as ? or @.
= Automated Message End =
 
= Error Handler Call Chain Start =
    VIPM Main Window.vi->
    2EDC3C81B4A2C6C7E1F2041B75CF3851
= Error Handler Call Chain End =
=========== END of VIPM 2014.0.2 (build 1976) Error Message ===========

  • 0

#5 RDR

RDR
  • Members
  • 17 posts

Posted 04 May 2016 - 09:46 PM

Also, here is the string passed to the System Exec call within '\LabVIEW 2015\vi.lib\JKI\VIPM API\command-line\support\Run EXE with Command-line Switches_vipm_api.vi'.

 

"C:\Program Files (x86)\JKI\VI Package Manager\support\VIPM File Handler.exe" -- "/command:repository_add_package" "/sources:C:\Users\lvtn\AppData\Local\Temp\lvtemporary_431412.vipm_return" "/repo_name:NI LabVIEW Tools Network" "/return_file:C:\Users\lvtn\AppData\Local\Temp\lvtemporary_333527.vipm_return" "/quiet:TRUE"


  • 0

#6 Ashish

Ashish
  • JKI Team
  • 254 posts
  • Gender:Male

Posted 07 May 2016 - 03:01 AM

RDR,

 

Was there any change in the OS, admin privileges, API version and operating environment?

 

Also, for testing purpose, can we get access to repositories that you are using? Tools Network and another working repo?


  • 0
Ashish Uttarwar
Product Support Engineer and Certified LabVIEW Developer, JKI

#7 RDR

RDR
  • Members
  • 17 posts

Posted 09 May 2016 - 03:22 PM

RDR,

 

Was there any change in the OS, admin privileges, API version and operating environment?

 

Also, for testing purpose, can we get access to repositories that you are using? Tools Network and another working repo?

 

Hello Ashish,

 

This happens on 5 different systems with an EXE calling the VIPM API--no changes were made to the code or OSes besides regular Windows Updates.  As for access to the repository, you should have access to the LabVIEW Tools Network repository as we publish it to the NI FTP here: ftp://ftp.ni.com/evaluation/labview/lvtn/vipm/index.vipr

 

This is the repository we're having trouble with when using the API and it is quite large.

 

 

 

Here is the internal repo I tested with and did not have any trouble adding a package to using the API (no changes were made to code outside of changing the repository name string for the API call):

 

[Self]
Self.Name=LV2P Tool Repository
Self.URL=file:///c:/dropbox/lv2partner shared/lv2p tools/vipm tool repository
Release.Number=1
Release.Date=Wed, 04 May 2016 10:57:47 -0500
Self.ID=a1f737822f4af51af05e180b4ea215dc
Client.GlobalAccess=TRUE
 
[Package ni_lib_simple_math_library-1.0.0.1]
Package.URL=packages/ni_lib_simple_math_library/ni_lib_simple_math_library-1.0.0.1.vip
Icon.URL=packages/ni_lib_simple_math_library/ni_lib_simple_math_library-1.0.0.1.bmp
Spec.URL=packages/ni_lib_simple_math_library/ni_lib_simple_math_library-1.0.0.1.spec
Package.MD5=e0d8f11764d012aa44f16827b2c95631
Package.Release Date=Wed, 04 May 2016 10:57:47 -0500
Platform.Exclusive_LabVIEW_Version=LabVIEW>=13.0
Platform.Exclusive_OS=ALL
Package.Display Name=Simple Math Library
Platform.Exclusive_VIPM_Version=2014

 

-RDR


  • 0

#8 RDR

RDR
  • Members
  • 17 posts

Posted 11 May 2016 - 06:40 PM

Do you have anything else we can try in order to resolve this issue?


  • 0

#9 RDR

RDR
  • Members
  • 17 posts

Posted 12 May 2016 - 08:36 PM

...is there anything else we can provide to move this along?


  • 0

#10 RDR

RDR
  • Members
  • 17 posts

Posted 16 May 2016 - 02:31 PM

...Just checking in.  This issue still affects us and we've not heard back in about a week.  Is there any other information we can provide?


  • 0

#11 RDR

RDR
  • Members
  • 17 posts

Posted 20 May 2016 - 02:28 PM

I sorted this out by rebuilding the entire repository.

 

-RDR


  • 0