In the last two weeks I have had two separate projects at different customers give me warnings saying that the MAX configuration server has stopped working. (One system is a PXI and the other an ethernet cDAQ, this error stopped the DAQmx tasks from initialising and running) I have carried out the instructions on this link https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P8bkSAC&l=en-GB which reset the MAX configuration and I managed to get both systems working again. I don't want this to happen again, so I have three questions: - Does anyone have any insight into what causes MAX configuration server to become corrupted - Is it possible/recommended to bypass the MAX config server when setting up DAQmx tasks in LabVIEW by somehow programatically identifying and configuring all of your hardware instead of setting up configuration in MAX and just referencing the hardware aliases in your code (I have seen online that it is possible to identify hardware by its serial number which may be a way forward) - Has anyone had any success programatically resetting the MAX server, I am thinking something along the lines of storing a backup of the server in the installation directory, and if I receive errors saying the DAQmx task can't be started I could replace the config file and prompt the user to restart. Any thoughts would be appreciated

LabVIEW

MAX Configuration Server Corrupt

@Niatross wrote:

Just to re-clarify my question. I am after the best way of making code resilient to MAX database corruption issues. A lot of our code goes to customers who aren't knowledgeable with NI software/hardware and as far as they are concerned just want a magic black box. Everyones comments has confirmed that I am thinking along the right lines so I am going to have an experiment today.

@Mancho00 wrote:

We have ~20 computers using DAQ devices, and I get one with a MAX database corruption every 3-6 months. It's definitely not due to software installation/update, either. There is a reason NI put a menu item in MAX to fix it...

Mancho, I am guessing you are referring to the 'Reset Configuration Database' button?

@JÞB wrote:

@BS, look into my older posts about NI Device Manager. It is possible to automatically detect a new device and then associate it with everything DAQmx-ish with a simple executable and some adroit HKEY NInja like moves in the same installer. <Don't do this at home! We are professionals >

What posts are you refering to here JpB? I can't find them on your profile.

Devmon may be the best search term. The use of it is fragile! I do not recommend it! <I think that it has been useful twice in twenty years >

How do you manage the Client that thinks "Well... this is just LabVIEW, not SOFTWARE " ? ???? Should not be as "amusing " of a topic as I believe it could be.

"Should be" isn't "Is" -Jay