LabVIEW 2016 32 bit, crash after splash screen happening after packages installed through VIPM

[freemason]

Hi,

i recently installed 2016 32 bit, and installed few useful packages through VIPM, and suddenly LV crashed after that, never been able to get 2016 running again, i completely removed and reinstalled again. still get this crash message after the splash screen.

i am trying to uninstall all the packages from vipm but when it tries to open LV it crashes and so i am unable to uninstall packages too.

Plz help.. did any one have this problem?

stuck here in a loop..

lvlog.txt

####
#Date: Thu, Apr 06, 2017 7:13:07 AM
#OSName: Windows 7 Enterprise Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: LabVIEW
#Version: 16.0 32-bit
#AppKind: FDS
#AppModDate: 6/09/2016 02:12 GMT
#LabVIEW Base Address: 0x00400000

InitExecSystem() call to GetCurrProcessNumProcessors() reports: 8 processors
InitExecSystem() call to GetNumProcessors() reports: 8 processors
InitExecSystem() will use: 8 processors

<DEBUG_OUTPUT>
4/6/2017 7:14:11.752 AM
Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id: f9bb3e0b-4592-4484-a80c-e0c582ca4d9d
ExceptionCode: 0xC0000005

</DEBUG_OUTPUT>
0x100011AF - nierInterface <unknown> + 0
0x10005F5A - nierInterface <unknown> + 0
0x100062EC - nierInterface <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x77CF5BE7 - ntdll <unknown> + 0
0x77CB98D5 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0

Thanks

[aputman]

Have you tried a repair install of Labview from the Add/Remove Programs?

[freemason]

Yes i did that too before completely removing and installing again

still crashes

[pallen]

Just found your old post after exactly the same thing happened. 

LabVIEW 2016 was working perfectly. 

Use VIPM to try to install package.  LabVIEW crash. 

Now LabVIEW 2016 refuses to start at all. 

[freemason]

if i remember correctly , i think i uninstalled all VIPM packages and installed the latest patch then reinstalled the packages.

[pallen]

Thanks for your reply.  

Unfortunately VIPM wasn't able to uninstall anything, as LabVIEW 2016 would crash immediately on start up.

Your reply prompted me to take another look though. 

I ran a search on the Access Violation string and found this page: https://www.tsxperts.com/forums/topic/ausnahme-access-violation-0xc0000005-bei-eip0x01013310/

In my case I deleted C:\Program Files (x86)\National Instruments\LabVIEW 2016\project\Plasmionique and C:\Program Files (x86)\National Instruments\LabVIEW 2016\vi.lib\Plasmionique    

I had not run LabVIEW 2016 for awhile.  In that time, my license had been renewed. When VIPM initially started LV, it timed out because I didn't notice the splash screen in the background waiting for me to hit the "Launch" button. 

I launched LabVIEW and then repeated the install on VIPM.  LabVIEW crashed after the DQMH install started.

Not sure if the license renewal had anything to do with the crash.  LabVIEW 2016 seems to be starting and running again now. 

This is on a bit of a legacy dev machine with multiple versions of LabVIEW living together nicely for a long time.  So it's quite relief having it up and running again.