LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

MAX Database Exited Abnormally

Solved!
Go to solution

Win 10, LV 18SP1(32 bit)

I suffered a disk crash (SSD) and am trying to get back to where I was.

I had to replace the SSD as it simply died.  All my source code was backed up, but Windows and LabVIEW went down with the ship.

I mistakenly tried to install from a LV2017 thumb drive but then realized my mistake.

 

I downloaded the 2018SP1LV-WinEng installation ZIP and the DVD-Jan-19-1 drivers ZIP

 

I installed them and all seemed OK. I can Activate LabVIEW and it works OK. I can create a VI and run it OK.

 

I have no actual DAQ hardware on this machine but I need to setup a simulated cDAQ system so my current project can operate as if it's on the target machine.

 

When I startup NI-MAX (v 18.5) it shows the splash screen for a long time (45+ seconds) and then the main window.

If I then click on DEVICES, or SCALES, or SOFTWARE, I immediately get the dialog "Max Database has exited abnormally" go to ni.com/info and enter this code.

 

I've been there and done that.

I made sure that MAX was completely closed.

I checked the NI Configuration Manager service in Windows.  It is NOT running, but I started it and tried again. 

This time it waits for 45 seconds and then comes up.  If I click on DEVICES, it waits 45 seconds and THEN gives me the "exited" dialog (and the service is no longer running)

I set the service action to RESTART, RESTART, RESTART, it all behaves the same.

I did RESET DATABASE from MAX menu and it's all the same.

If I run it as ADMINISTRATOR, with the Firewall OFF, It's the same.

 

I did a FORCE INSTALL from the SETUP, and installed the thing again. Same

I did a REMOVE ALL from the PACKAGE manager and installed again. Same.

 

I removed all NATIONAL INSTRUMENTS folders from C:\Program Files, C:\Program Files (x86), C:\Program Data, then stopped and deleted all NI services, and all keys from the registry.

Restarted and installed again.  Same deal.

 

I read all the forums posts about this, no joy.

 

Do I have a mismatch between the LV and the Driver install disks?

 

Any other ideas?

 

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 1 of 4
(167 Views)

By the way, during that 45 second hang, when MAX is trying to start, the windows TASK MANAGER doesn't even see it. So it cannot be terminated during that time.

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 2 of 4
(166 Views)

For the record, the CPU usage during that hang is minimal. Network usage spikes briefly then quits, Memory usage is steady. 

Sometimes the splash screen shows "initializing", sometimes "loading plug-ins".

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 3 of 4
(163 Views)
Solution
Accepted by topic author CoastalMaineBird

OK, so maybe something in Windows itself got gorched.

I downloaded the version of DRIVERS from MAY 2018, reinstalled windows, reinstalled those drivers. and all is well.

Not sure which item fixed it, but it doesn't matter in my case.

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 4 of 4
(108 Views)