tibobo Posted July 24, 2007 Report Share Posted July 24, 2007 Hi ! I'm working on a Power Mac G4 , MAC OSX 10.4.10, with Labview 8.2.1. I'm trying to install the openG packages with VIPM 1.0. I've achieved to install a few packages, but I'm unable to install most of them. I can't install the oglib package, the ogrsc package, and picture3d. An error messages appears : Error code 10 Has anyone an idea how to solve this problem?? Kind Regards Boris error_code_10_VIPM.tiff Link to comment Share on other sites More sharing options...
JKI Posted July 24, 2007 Report Share Posted July 24, 2007 Hi Boris, I'm sorry to hear that you're having troubles. Error 10 is a File IO Error caused by trying to create a file or folder that already exists. Perhaps it is also caused, due to a file permission issue. Can you please send us the most recent error log file located in the ./error/ folder beneath your VI Package Manager installation? Thank you, -Jim Link to comment Share on other sites More sharing options...
tibobo Posted July 25, 2007 Author Report Share Posted July 25, 2007 Hi Jim! Thank you for your help. This is the only file I've found in the error folder. What do you think about it? Thanks a lot. Boris juillet_23_2007.txt Link to comment Share on other sites More sharing options...
JKI Posted July 25, 2007 Report Share Posted July 25, 2007 Boris, I think that problem is that VIPM cannot connect to LabVIEW's VI Server. Have you been able to successfully test the connection? Please ensure that your VI Server connection settings are configured and tested as described here: http://forums.jkisoft.com/index.php?showtopic=232 Please let me know if this helps. Thanks, -Jim Link to comment Share on other sites More sharing options...
tibobo Posted July 31, 2007 Author Report Share Posted July 31, 2007 Hi Jim! the problem is now solved! Thank you very much! Boris Link to comment Share on other sites More sharing options...
Jim Kring Posted July 31, 2007 Report Share Posted July 31, 2007 Boris, That's great news! Thanks, -Jim Link to comment Share on other sites More sharing options...
Ben Barrett Posted July 5, 2018 Report Share Posted July 5, 2018 Hi, this topic is 11 years old, but I'm having a similar problem with a package I'm trying to build. I'm getting the same error (10), and if i exclude two particular files from the build it goes away and builds successfully. I tried to find the ./errors directory but can't locate it, has its location changed in the intervening versions between the original post and now? I should note I'm running LV2017 on Windows 7 instead of Mac. Error Details: Code: 10 Source: Error 10 occurred at New VI Library.vi Possible reason(s): LabVIEW: Duplicate path. Error Conditions: Create Target File error: File Path: <Not A Path> Link to comment Share on other sites More sharing options...
Ben Barrett Posted July 10, 2018 Report Share Posted July 10, 2018 Some additional information: The VI's causing the problem all seem to be ones containing the same malleable VI Link to comment Share on other sites More sharing options...
Ben Barrett Posted July 10, 2018 Report Share Posted July 10, 2018 And one last update, sorry about the three posts in a row. I noticed that the malleable VI common to all the VIs failing the build also called malleable VIs within itself (part of the same set). Apparently it doesn't mind building malleable VIs, as long those malleable VIs don't contain other malleable VIs. Luckily for me, in this case, I only had one level of embedded malleable VIs. I solved the issue by replacing the embedded malleable VI its contents (it was a pretty small VI so this wasn't disruptive on the BD). I imagine it this could be a larger issue for someone who built a highly embedded malleable structure and wanted to try and build a package. Is this a bug or is there something about malleable VIs that make them incapable of being built into packages? Link to comment Share on other sites More sharing options...
Ashish Posted July 13, 2018 Report Share Posted July 13, 2018 Ben, Thanks for reporting the issue. We have forward this to our team to take a look at. We cannot promise on when the fix will be released. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.