LabVIEW
MAX Database not running
I am repeatedly getting the error 'The MAX database is not running' when trying to perform operations in MAX on a PXI (Windows 7, don't know the PXI model at the moment). When this error is present I will also not be able to run code with DAQmx functions.
I have followed the advice on this page https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000PAp0SAG&l=en-GB and tried restarting the NI Configuration Manager (Which wasn't running) but it stops immediately. I have also done this with the firewall switched off
If I reset the MAX database and restart most of the time it will work, but it sometimes takes a couple of attempts.
I have been living with it for a while now but it is starting to drive me mad. Does anyone have any suggestions apart from a full reinstall of NI/Windows?
@Worle wrote:
I am repeatedly getting the error 'The MAX database is not running' when trying to perform operations in MAX on a PXI (Windows 7, don't know the PXI model at the moment). When this error is present I will also not be able to run code with DAQmx functions.
I have followed the advice on this page https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000PAp0SAG&l=en-GB and tried restarting the NI Configuration Manager (Which wasn't running) but it stops immediately. I have also done this with the firewall switched off
If I reset the MAX database and restart most of the time it will work, but it sometimes takes a couple of attempts.
I have been living with it for a while now but it is starting to drive me mad. Does anyone have any suggestions apart from a full reinstall of NI/Windows?
I don't know if this will help in your case, but there are TWO services related to NI-MAX to get the database running. The one that is cut off at the bottom of your picture (Device Loader) is the other.
In addition to restarting them, set them both to start with delay. While it sounds weird, I seem to recall that sometimes these services are considered threats by Windows and blocks them from running, but that by setting them to delayed start somehow gets around this. I don't even know if I am explaining it right, but I do know that this works.
