Jump to content
Jed Davidow

VIPM Community locks up on startup (windows 7 pro x32)

Recommended Posts

I have installed VIPM on several W7 platforms (both x32 and x64) and not seen this.

 

The installation appears to go smoothly. When I start it for the first time, a list of packages appears (although I am not sure if it got to the point of downloading the list). If I don't click on a package, things are ok. But as soon as I click on a package, the program becomes unresponsive. Actually, the install/uninstall package buttons at the top appear to be racing through enabled/grayed out, as if the program is racing. I need to kill it via task manager.

 

I uninstalled, deleted the Program Files folder and the ProgramData folders, and got the same results.

 

I looked briefly through the forums, but did not see anything. Any ideas?

Share this post


Link to post
Share on other sites

Error log attached. That reminded me that I am running eval versions of 8.6 and 2009 on this new machine, until my client's upgrade comes through. So I thought that maybe this had something to do with the Eval screen that pops up, but I had already disabled it.

 

So after I looked at the logs, I started VIPM (it automatically started as an Admin) and it worked perfectly. So I am not sure what's up.

 

=========== START of VIPM Error Message ===========

An internal VIPM Error has occured on: Wednesday February 17, 2010 at 10:38:15 PM

 

= Automated Message Start =

Error -600 occurred at Query Registry Key Info.vi

Possible reason(s):

LabVIEW: Undetermined Windows registry error.

= Automated Message End =

 

= Error Handler Call Chain Start =

VIPM Main Window.vi->

6AC4D79455EAE877816D26FA9E5CDFD0.lvlib:VIPM Options Window.vi

= Error Handler Call Chain End =

=========== END of VIPM Error Message ===========

 

=========== START of VIPM Error Message ===========

An internal VIPM Error has occured on: Wednesday February 17, 2010 at 10:41:40 PM

 

= Automated Message Start =

Error 42 occurred at 9157622C13DB5BB79970A5285269953E

Possible reason(s):

Could not connect to the LabVIEW Version specified, due to another LabVIEW Version at the specified

port or path.

 

Complete call chain:

9157622C13DB5BB79970A5285269953E

A319F3C7B737363CC14EDAFAB3308F2B

VIPM Main Window.vi

= Automated Message End =

 

= User Defined Message Start =

Could not connect to LV.

= User Defined Message End =

 

= Error Handler Call Chain Start =

VIPM Main Window.vi->

A319F3C7B737363CC14EDAFAB3308F2B

= Error Handler Call Chain End =

=========== END of VIPM Error Message ===========

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.

Guest
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.

Loading...

×
×
  • Create New...

Important Information

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