MAX 14.0 broken and database corrupt after installing LV2014 and latest device drivers

[Dr_M]

The only parts missing from the MAX zip file is the ResetConfigs folder, which is still too large to send.

[Oley_Mich]

Has there been a fix to this yet?  I am experiencing this with a fresh install of MAX 14.2.  Tried the configuration reset from within MAX and a few more of the other "fixes".

[mcduff]

Have you tried the newest version, 14.5.

There is something sketchy with MAX lately. I needed to reinstall after updating to 2014 SP1. (After updating everything MAX did not work, so I had to wipe all NI software form the computer and install on a blank state. The updates leave something amiss on my computer.) Typically the culprit for me is DAQmx.

Good luck.

mcduff

[Alisha_P]

I would agree - try updating to 14.5.

Check if there are any logs in C:\ProgramData\NationalInstruments\MAX\

If there are, post them here, and I can take a look at them.

Also, what operating system are you on?

[Oley_Mich]

My apologies.  This is actually a fresh 14.5 install.  Windows 7 is the OS.

Attached some logs.

[Alisha_P]

My mistake, I actually am interested in .dmp files if there are any in the MAX or MXS files.

These logs definitely show that something odd is going on though.

[Oley_Mich]

Here are some .dmp file from yesterday.

[Bob_Schor]

Could you clarify something?  Are you installing LabVIEW 2014 or LabVIEW 2014 SP1?  I'm waiting for my SP1 Distribution Kit, and want to know if I should anticipate similar headaches (I've got 2010, 2011, 2012, 2013, and 2014 on this machine).  I've also had "fun" with LabVIEW installations ...

Bob Schor

[mcduff]

As far as my personal experience goes ...

I was updating from 2014 to 2014SP1. Downloaded the device drivers, which did not have the new version of DAQmx at the time, and followed all of the installation instructions. The system was unusable. I uninstalled ALL NI components, then started from SP1 with a fresh install. Rather than use the Device Drivers, I downloaded and installed the components I wanted separately.

Cheers,

mcduff

[Alisha_P]

Hey Oley_Mich,

I've looked through the logs and the .dmp files that you've provided. The .dmp files match an issue we know about, but haven't been able to root cause (because we haven't been able to reproduce it). We're not sure how connected this is with the fact that the logs show your MXS database continually trying to restore itself.

In order to further evaluate the state of your system, can you provide a zip of C:\ProgramData\NationalInstruments\Installation Logs\

Could you also provide as much of the contents of C:\ProgramData\NationalInstruments\MAX\ as possible (will probably require a couple of zips)?

The ideas we have so far as to what could be going wrong would have been fixed by resetting the MAX database. You've already done that, right?