Re : Error: Max Hex 0x80040311

[Rodéric]

Hello,

I am having this problem for some time now and I can't find a solution.

Theerror that LabVIEW throws is: Error -2147220719 occurred at XXX.vi -  - Possible reason(s): - MAX:  (Hex 0x80040311) The client process has been disconnected from the configuration server. If this problem persists, please note the steps you performed that led to this error and contact technical support at http://ni.com/support. - Task Name: RELAI_LATCHS

When I get this error, I can't communicate with any devices inside my PXI chassis (NI 4070, NI 6229, NI 2529, and 2 Pickering switch cards) exept the GPIB devices. I have a GPIB card and 4 instruments connected. The only solution is to reboot LabVIEW. The problem is that it seems to be happening on the third initiazation of my instruments ( so I can only test two DUT then I have to reboot my software).

My questions are:

-What is the configuration server?

-How can I (programmatically) restart it so my instruments are detected.

Some of the things I tried:

-Changed MAX version

-Changed NI DMM and NI switch version

-Update LabVIEW 2012 to LabVIEW 2012 sp1 +f5 patch

-Tried it on another computer and another PXI chassis and other cards (I have two test stations)

I can't post the code because it's to large and I can't make a simple example that reproduces the issue. It seems to happen only with everything running altogether....

I already openned a suport reauest form NI France but they don't know what this error might be nor what the configuration server is...

Best regards,

Rodéric

[JérémyC]

Hello,

Corrective Action Requests exist regarding this kind of behavior but the origin is uncertain :

I suppose you already look at the following document : Why Do I Get a Measurement & Automation Explorer (MAX) Database Connection Error?

I also noticed that lot of Support Requests related to this error involve DAQ device. You could try to update DAQmx, reset MAX 's database or reduce the number of boards in order to see if one type (DMM, DAQ or other) is responsible for the error.

In order to restart LabVIEW, maybe you could create a deamon executable which could peer at your application and restart LabVIEW through command line if the communication is broken.

Something else you could try is configurating the different services (NI Configuration Manager, NI Device Loader, ...) to "restart after failure".

Regards,