Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by odjau

  1. Hello Ashish,

    I think I have a good understanding of the two topics you mention. I'll try to better explain my issue.

    We have packages built with older version of VIPM that we can properly install with all VIPM except VIPM 2014. Trying to install them with VIPM 2014 throw the conflict error. An easy workaround is to not upgrade VIPM to 2014 version. The problem with that is that we have some packages (available on the LVTN) built with VIPM 2014, so we need to upgrade to install them.


    The question is: why this error appear during the install process using 2014 and not with others VIPM version? Sending you the affected packages could help you to understand our issue ?





  2. Hello JKI team,

    The version of VIPM 2014 prevent us to install internal reuse packages that have been built and successfully used with previous VIPM version. The following dialog is shown.




    The weird thing is that the conflict point to a very old package not used.

    I've tried to build the package with VIPM 2014 and still have the error.


    This issue prevent us (15 developers) to upgrade VIPM. Knowing that package built with VIPM 2014 cannot be installed with older VIPM that could become a real issue for us.


    Any advice will be very helpful.


    Have a great day.



  3. Hello everyone,


    When I want to upgrade a package I come across error 14.




    Note that VIPM teel me that it is goig to perform an "install" action instead of "upgrade" action.


    The directory C:\ProgramData\JKI\VIPM\databases\LV 12.0\saphir_lib_mysqlview has the following files inside :




    Removing these files allow me to install the package.


    Any idea to fix this issue ?





  4. Hey JKI team,

    I'm just comming back fron NI-Week and installing new VIPM 2011 version.

    I know that Win XP is an end of life OS, but I'm still using it and my diplay settings give a weird look as you can see on the following picture.




    I think tha black strips are due to system color set by color template light grey.


    This is not an important issue, but it can be surprising.





  5. I've successfully upgrade all my old packages built with OpenG Package Builder except for one. Trying to build it with VIPM 2010 give me the following error:




    VIPM does not allow me to build package containing VIs with the same name. In my use case, I want to install template VIs in the corresponding LabVIEW directory. Some of my template VIs have the same name but are slightly different.

    If it's not too hard to allow duplicates in a same package, it will be great to had this feature to next release of VIPM.




    [Notice] Writing this post, I think about a possible workaround, split my package in many small packages. It can be done but hard to maintain in the future if I need to add lots of templates like these ones...

  6. Which version of VIPM are you using? 2010.0.0 or 2010.0.1?

    I'm using 2010.0.1 (build 1581) version.


    Also, please elaborate on the "open it from network HD" comment. Did you open it directly from the network drive by double-clicking on it?

    I use an explorer window to browse our LAN to find a shared directory on colleague's PC containing vip file. Then I double-click on it and obtain the error message.

    I've got the same behavior browsing a local directory via "Microsoft Windows Network".

    I'm running windows XP Pro SP3.

    Let me know if you need more information about our network settings.

    • Upvote 1

  7. Hi JKI team,


    I've come across some issues building licensed package with VIPM 2010. I don't know if it's wrong use or bug of VIPM 2010 (it can be LV activation feature too).


    1 - I build successfully licensed package for my toolkit. I install it successfully. I activate the license. Every thing is right at this point.

    Issue come when I want to access VI block diagram from toolkit, I can(!) and I don't want the end user can see diagram.

    In my understanding "Library protection" tab in "licensing & activation" category of VI Package Builder adds password to all lvlib VIs, am I wrong ? I've tried to apply password in "Source File Settings" but an error occurs during the build.


    2 - Setting an "automated Online Activation URL" result an error (code :-314515 source : _ValidateAutoActivationURL) during the build process (I've tried several form http, https,...)


    Thanks for your help

  8. Hi,

    This morning, my VIPM professional edition (v3.0 build 1280) seems to be deactivated. Impossible to activate again with my original activation code.

    The only unusual thing I've done yesterday on my PC is to merged old unused HD partitions to get more space and be able to install LV 2010.


    What can I do to solve this issue ?


    Thank you

  • Create New...

Important Information

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