Jump to content

[Solved] VIPM crashes with file permission error

Recommended Posts


Over night something changed on my windows 10 build server and I can now no longer open VIPM. It just shows the splash screen and then closes again.

Here's the log file:

=========== START of VIPM 2018.0.0 (build 2025) Error Message ===========
An internal VIPM 2018.0.0 (build 2025) Error has occured on: Tuesday August 20, 2019 at 03:19:48 PM

= Automated Message Start = 
Error 8 occurred at Open/Create/Replace File in NI_LVConfig.lvlib:Parse Config to 
Queue.vi->NI_LVConfig.lvlib:Load.vi->NI_LVConfig.lvlib:Open Config Data 
Class.lvlib:D69AB3997B80ACD75689430E3922612C->OGPM Class.lvlib:OGPM Init.vi->VIPM Splash.vi
Possible reason(s):
LabVIEW:  File permission error. You do not have the correct permissions for the file.
DMA hardware error detected.
= Automated Message End =

= User Defined Message Start = 
    Error(s) Generated in Splash Window
= User Defined Message End =

= Error Handler Call Chain Start =
    VIPM Splash.vi
= Error Handler Call Chain End =
=========== END of VIPM 2018.0.0 (build 2025) Error Message ===========

Any idea where the files are that it doesn't have the right permissions for?

Edited by ThomasGutzler

Share this post

Link to post
Share on other sites

Did your user account get locked that you run the service under?

Edited by MikaelH

Share this post

Link to post
Share on other sites

No, the account is fine.

The CI build (system account) still works. The problem is when I log in manually to debug a problem. I just don't know where to look for those files it's trying to access or which files those are.

Edited by ThomasGutzler

Share this post

Link to post
Share on other sites

Try running VIPM as an administrator.

I have had similar issues happen when trying to install packages that were cached from the tools network by another user.  Cached packages (and some other VIPM settings, I would assume) are stored in %ProgramData%, and Windows 10 seems to think that you shouldn't be able to access files in program data created by (in this case downloaded by) another user.

Share this post

Link to post
Share on other sites

Turns out that deleting the VIPM cache (C:\ProgramData\JKI\VIPM\cache) fixes the problem.

With the cache folder gone I restarted VIPM and it created it again with fixed permissions and running happily for myself and the system user which is used for CI builds.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By JKSH
      This is an offshoot of https://lavag.org/topic/19414-can-i-save-as-a-vipb-file-in-vipm-and-keep-the-old-palette-if-i-change-the-source-directory/. That thread discusses hand-modifying the XML data in a *.vipb file, which Jim Kring himself seems to accept as a viable solution in some cases. However, when I try that, VIPM says, "VI Package Builder was unable to open the build spec due to an error."
      I initially thought this was new behaviour introduced in VIPM 2016, but downgrading to VIPM 2014 SP2 didn't change anything. I'm now unable to downgrade any further, as my PC is convinced that 2014 SP2 is still installed (even though it's not...)
      Could someone kindly try the attached *.vipb file and see if it opens? It's a bare minimum default file, with only a description summary added. I've hand-modified the summary from "Lorem ipsum" to "Larem ipsum" and now VIPM refuses to open it.
    • By oskretc
      This maybe has been ask/answered/discuss before but here it is.
      Is there any VIPM alternative out there?
      If not, It will be very interesting to start a discussion whether an open source version is feasible and how many members in the community are willing to work on it.
      I know JKI has a great product already but seems like development has come to halt wrt VIPM.
      Any comments?
    • By Callan
      Hi all,
      I have been trying to use VIPM to distribute drivers that rely on a .NET framework that is unsigned (i.e not in the global assembly cache).  My issue is that after the package is installed, none of the VIs will work because LabVIEW cannot locate the .net assembly.  However, if I launch labview by opening the library VIPM installed, all of the VIs will work, and LabVIEW is able to locate the the .Net framework and it appears in the main application instance.  I need to be able to use the installed vis all the time, not just when LabVIEW is launched in this particular way.
      Here is a link to all the all the files I used: 
      Here are the steps I went through:
      1) We put all the .NET dlls and the LabVIEW.exe.config file in the Labview directory.

      2) We installed the package on our computer.  

      3)We closed everything and relaunched Labview from the start menu.  Then accessed the BioRobotics/Vicon palette.

      4)We placed the Get Ref subVI on the block diagram, opened it up, and ran it it.
      5) We got the following error:

      We also get a similar error for any VI that uses a method associated with the .NET dll.
      6) However, if we again start with everything closed and launch Labview by clicking on the VICON.lvlib located in the vi.lib

      7) Then repeat steps 3 and 4.  We do not get any errors in the VIs on the palette, and the .Net assembly loads fine.  We can even close the library and everything still works.  Somehow opening the library first makes LabVIEW know to load the ViconDataStreamSDK_DotNet assembly when using functions on the Vicon palette.

      If anyone does attempt to build a new package, it is worth noting that I included the dlls in the source files, and in the same folder as the vipb:

    • By oskretc
      Let me start with some context
      We have to differentiate from a Production environment (to produce data) and Development environment (to develop test and debugging).
      Our code (very simplified) is organized in this way
      - Tests (Actual vi that will produce results)
      - System files (support vi, drivers, common functions etc.)
      Both are under source control
      We have decided to make VIPM's (residing in vi.lib) for all System files and leave the Tests files where they are (random folder under source control).
      This means the all the vi's inside Tests will have links to the System Files (inside vi.lib now) and that works pretty well for the Production Environment, but when we want to use the Tests in the development environment (Tests and System Files in a random folder) we need to re-link all the Tests to point to the local files and not the System Files inside vi.lib.
      The question is:
      Is there any way to manually update the references of the Tests so we can choose from where we want to get the System Files?
    • By jsettles
      Does anyone have any ideas as to why I would be getting the following message while trying to install the OpenG Toolkit through VIPM?

      I'm using LabVIEW 2014 SP1 (32-bit) and Windows 7 Enterprise SP1 (64-bit)
  • Create New...

Important Information

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