TonP Posted June 3, 2014 Report Share Posted June 3, 2014 I was recently contacted by someone who wanted to install the Code Capture Tool, and was unsuccessful, I tried to reproduce and indeed I couldn't either. I cannot uninstall it either. Here's are some log entries: =========== START of VIPM 2014.0.0 (build 1941) Error Message =========== An internal VIPM 2014.0.0 (build 1941) Error has occured on: Tuesday June 03, 2014 at 08:00:20 p.m. = Automated Message Start = Error 1 occurred at (Package "lava_lib_code_capture_tool-3.2.2-48"is not cached) 6AB39A648CE6EFC743A3CD12262AD578 in OGPM Class.lvlib:04D268DDDD5A7242818EDB49A7B8F587->Pkg Props.lvclass:VIPM Package Properties SubPanel.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 = = User Defined Message Start = Error within the package detailed information section of the package properties dialog. = User Defined Message End = = Error Handler Call Chain Start = Pkg Props.lvclass:VIPM Package Properties SubPanel.vi = Error Handler Call Chain End = =========== END of VIPM 2014.0.0 (build 1941) Error Message =========== =========== START of VIPM 2014.0.0 (build 1941) Error Message =========== An internal VIPM 2014.0.0 (build 1941) Error has occured on: Tuesday June 03, 2014 at 07:49:58 p.m. = Automated Message Start = Error 7 occurred at File/Directory Info in ZLIB Open Unzip Archive__ogtk.vi->AA61FABC2E7B6BB4F479C1EF2F8565E5->1E20EF8033E06EC036DD5478ABAD1DFB->Pkg Props.lvclass:894662ADE214661F5CC3C735CC2C45C3->Pkg Props.lvclass:3DF45ADBE7799DE18D60C46D288ABA39->Pkg Props.lvclass:VIPM Package Properties Window.vi->VIPM Main Window.vi Possible reason(s): LabVIEW: File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct. C:\ProgramData\JKI\VIPM\cache\lava_lib_code_capture_tool-3.2.2-48.ogp = Automated Message End = = User Defined Message Start = Error inside Package Properties Window = User Defined Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> Pkg Props.lvclass:VIPM Package Properties Window.vi = Error Handler Call Chain End = =========== END of VIPM 2014.0.0 (build 1941) Error Message =========== =========== START of VIPM 2014.0.0 (build 1941) Error Message =========== An internal VIPM 2014.0.0 (build 1941) Error has occured on: Tuesday June 03, 2014 at 07:46:25 p.m. = Automated Message Start = Error 7 occurred at Copy in 28CB9C127591D50539121BFBB7FC977A->OGPM Class.lvlib:CD51A92C2C25771313A68E451CAA1620:2760001->18351B6FFCB82C7CA89533614A3DDF25->7D2504E31560 7556304537B0CF46AA0D->VIPM Main Window.vi Possible reason(s): LabVIEW: File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct. C:\ProgramData\JKI\VIPM\cache\lava_lib_code_capture_tool-3.2.2-48.ogp. File Path: "C:\ProgramData\JKI\VIPM\cache\lava_lib_code_capture_tool-3.2.2-48.ogp". = Automated Message End = = User Defined Message Start = Add To Library = User Defined Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 7D2504E315607556304537B0CF46AA0D = Error Handler Call Chain End = =========== END of VIPM 2014.0.0 (build 1941) Error Message =========== Further info: VIPM 2014 build 1941 Win 8.1 64-bit Dutch with english language pack Any ideas? Link to comment Share on other sites More sharing options...
Ashish Posted June 4, 2014 Report Share Posted June 4, 2014 TonP, We were not able to reproduce the exact issue but do see some discrepancy which is not allowing us to install the package. We are investigating this and will get back to you soon. Link to comment Share on other sites More sharing options...
crossrulz Posted July 21, 2014 Report Share Posted July 21, 2014 I was just playing around with this myself since I was trying to install the CCT with a new setup I have. I downloaded the ogp file from LAVA. I then went into the package and edited the spec file to remove the conflict with "Code_Capture_Tool>=0.0.1". It installed with no problems after that. So it appears (from an outside perspective) that VIPM is using Match Pattern to look for "Code_Capture_Tool", which is found in the latest package name "lava_lib_code_capture_tool". Since this worked just fine in the previous 2013 version of VIPM, I'd say this is a new bug in VIPM 2014. Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted July 23, 2014 Report Share Posted July 23, 2014 I took a look at this today and think I can isolate it to a VIPM bug. I'm working on a fix for this. Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted July 29, 2014 Report Share Posted July 29, 2014 This has been fixed in the latest VIPM Labs release: http://support.jki.net/entries/24071293-VIPM-Labs Link to comment Share on other sites More sharing options...
crossrulz Posted July 31, 2014 Report Share Posted July 31, 2014 This has been fixed in the latest VIPM Labs release: http://support.jki.net/entries/24071293-VIPM-Labs Yep, that seems to have worked for me. Thanks Michael. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.