Jump to content

Crash on startup


qbits

Recommended Posts

VIPM will either lockup or crash during the startup slash screen. Attached is a dump file that was generated. I have VIPM 2012.0.1 installed with LabVIEW 2012 (32-bit) and (64-bit) on Windows 8. I had the same issue when running on windows 7 so did a clean install of Windows 8 (as well as all the NI software).

 

One thing of interest that I am noticing.. If I remove LabVIEW 2012 (32-bit) VIPM will launch just fine. The program seems to be linked to the 32-bit install and runs just fine if I only have LabIVEW 64-bit installed. This is repeatable such that whenever LabVIEW 32-bit is installed VIPM will crash.

 

Any help would be appreciated.

 

Thanks.

29d9de07-237f-44ee-8782-04b9ab171f1a.zip

Link to comment
Share on other sites

qbits,

 

I am unable to recreate the behavior on my 64 bit Windows 7 virtual machine. I have LabVIEW 2012 (32 and 64 bit) and installed VIPM 2012.0.1 (build 1818). It launches successfully. Here is the screenshot: http://screencast.com/t/gCODbPuHBA

 

VIPM launched successfully from no-admin account as well.

 

While I am still investigating, let me know if you find anything that I can try.

Link to comment
Share on other sites

Hi Ashish,

 

This seems to only effect this one machine (I have other win8 machines with LV32+LV64+VIPM installed without problems). I installed TestStand and Switch Executive and now it will launch VIPM successfully. My only guess is that during the TestStand install that it must patch something fixing the problem.

 

Thanks for your help.

Link to comment
Share on other sites

  • 2 weeks later...

I'm getting the same problem. VIPM 2011 didn't work either.

Though I loaded it just now to try a dump, and it ran just fine...I'm going to install everything I might ever want in case it crashes again. :rolleyes:

 

EDIT: And just after I installed one package, it crashed again. Didn't get a dump of that, but I started it and it crashed, so I took a dump of that.

 

http://www.mediafire.com/?z8m899791eka6jy

Link to comment
Share on other sites

flarn2006,

 

What is your OS and other PC parameters? Was VIPM ever working for you before?

 

Please provide some screenshots if possible.

 

I have an Alienware Aurora R4, with a quad-core Intel Core i7-3820 factory-overclocked to 4.2 GHz (I think.) I have 16 GB of RAM, and 64-bit Windows 7 Ultimate. I have two 1 TB hard drives, combined using RAID to a 2 TB volume. VIPM has never worked on this computer, neither 2011 nor 2012. I don't know if anything before 2011 would work, though it might not even be compatible with LabVIEW 2012.

 

GPBjk.png

 

Problem Details:

Problem signature:

Problem Event Name: APPCRASH

Application Name: VI Package Manager.exe

Application Version: 2012.0.1.1818

Application Timestamp: 4ee684e5

Fault Module Name: ntdll.dll

Fault Module Version: 6.1.7601.17725

Fault Module Timestamp: 4ec49b8f

Exception Code: c0000005

Exception Offset: 00033792

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: 0a9e

Additional Information 2: 0a9e372d3b4ad19135b953a78882e789

Additional Information 3: 0a9e

Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

 

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

 

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

Link to comment
Share on other sites

same here, problem found on multiple systems, but exact same model (dell latitude e5520 - CPU i5-2520M@2.50GHz)

 

it works on older PCs (core2duo, dual core), it works on VMs (vmware workstation 9).

 

same config on all PCs (I use SCCM for deployment method, so it's the exact same config)

 

thanks for the support once again!

Link to comment
Share on other sites

  • 2 weeks later...

Not sure if this will help, but I installed VPM with LV2011, and it crashed on startup and never ran. I just onstalled LabVIEW 2012, and gave it another shot and now it runs fine. MicroSoft Framework 4.0 got installed during the 2012 upgrade - so maybe trying installing that?

 

Steve

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

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