Jump to content

VIPM 2020: No main window after splash screen on Windows 7

Recommended Posts

VIPM 2020 running in task manager, but main window does not appear, nor is VIPM icon in windows tray (Windows 7 on a Parallels virtual machine on a MacBook).  Can open build specs and get that window, but cannot install packages.  

Attached is image of Build Spec window , but no main window.


Share this post

Link to post
Share on other sites

I've seen similar happening on two different PCs as well. Restarting fixed it on one; had to reinstall on another.

Currently on this one it opens, but will automatically close itself after a maybe 20 or 30 seconds.

I'm not sure what's causing all of this, but this is all I have in C:\ProgramData\JKI\VIPM\error.


=========== START of VIPM 2020.0.0 (build 2302) Error Message ===========
An internal VIPM 2020.0.0 (build 2302) Error has occured on: Sunday June 28, 2020 at 05:22:19 PM

= Automated Message Start = 
Error 42 occurred at (http response "404". URL Requested: 
tin_consultants_lib_finance_ohlc_plot- 85294761631CBC58471969C9E99FB95F:2980001 in 
->OGPM Class.lvlib:0A647C51DBC1AD7225F71A08D470BB08->OGPM 
Class.lvlib:4CD02F4728B5353B72E37139092E0B05->E1F6385E95370507176402E569A529D7->VIPM Main Window.vi
. URL: 
Possible reason(s):
LabVIEW: (Hex 0x2A) Generic error.
= Automated Message End =

= User Defined Message Start = 
    Error downloading package info
= User Defined Message End =

= Error Handler Call Chain Start =
    VIPM Main Window.vi->
    OGPM Class.lvlib:4CD02F4728B5353B72E37139092E0B05->
    OGPM Class.lvlib:0A647C51DBC1AD7225F71A08D470BB08
= Error Handler Call Chain End =
=========== END of VIPM 2020.0.0 (build 2302) Error Message ===========

Share this post

Link to post
Share on other sites

Hi @drjdpowell, @jb1592,

Sorry for the issues. We're working hard on VIPM 2020.1 and hopefully this issue will be resolved.

It's odd that the package builder window opens, yet the VIPM main window and the system tray icon aren't showing.  I've heard a few other reports of similar behavior and we've got it on our radar.  I don't think it's related to the "Error 42 occurred at (http response "404". URL Requested)" -- I think that was an issue with a missing file on NI's LVTN package repository.



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.


  • Create New...

Important Information

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