[Solved] VIPM crashes with file permission error

[ThomasGutzler 54]

Hi,

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 
(compatibility).vi->DDEFA056211BA4DA4D215C322E067D90->621BFCD461979D3C7127139A69154E03->762BBE85A007
171D5A65B48289D23361->46803A2448FAC5F85BFF8F5C199E9C6F->OGPM 
Class.lvlib:7D7C5CD8C5D361C01081DF5613237E15->OGPM 
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.
C:\ProgramData\JKI\VIPM\cache\ngene_lib_deepltk_fpga_addon-1.0.0.45.spec
= 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 September 10 by ThomasGutzler

[MikaelH 172]

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

Edited August 20 by MikaelH

[ThomasGutzler 54]

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 August 21 by ThomasGutzler

[TomOrr0W 8]

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.

[ThomasGutzler 54]

You're right, running VIPM as admin works but I'd still like to know how to fix the problem rather than work around it.

[ThomasGutzler 54]

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.