Error launching the 'LabVIEW.Application [Error Code: -18001]

[hegb_85]

I'm having the same trouble here with a PXI Machine. I'm not sure of the specs but i'll check them tomorrow.

Im using TS4.0 and LV8.5.1 and it appears randomly.

 I'll check my code to see if i have any problems with the parameters or something.

Any other ideas?

[RGreene]

---

ethan85 wrote:

I'm having the same trouble here with a PXI Machine. I'm not sure of the specs but i'll check them tomorrow.

Im using TS4.0 and LV8.5.1 and it appears randomly.

 I'll check my code to see if i have any problems with the parameters or something.

Any other ideas?

---

I have this trouble also on a PXI Machine. Using TS4.2 and LV2009. The error appears during test, at seemingly arbitrary occasions when run in the TestStand Full-Featured OI using the LV Development System AND the LVRTE. There are four Agilent PSUs and two HP DMMs in communication in the sequence, as well as utilisation of 2 PXI-6229 DAQ Card. There is also serial comms (RS-232). The error can occur on any VIs that carry out the above operations.

Attached is an error screenshot! Has anyone any ideas? Help would be greatly greatly appreciated!!

Rob

Message Edited by Greener on 03-25-2010 12:56 PM

[RayFarmer]

What could be happening is one of your instrument calls is crashing and that will cause the labview activeX server to stop, hence the error.

Difficuilt to track down if it's occurring at seemly random areas. You would have to identify what all these areas have in common.

Regards

Ray Farmer

[RGreene · Accepted solution]

---

RGreene wrote:

I have this trouble also on a PXI Machine. Using TS4.2 and LV2009. The error appears during test, at seemingly arbitrary occasions when run in the TestStand Full-Featured OI using the LV Development System AND the LVRTE. There are four Agilent PSUs and two HP DMMs in communication in the sequence, as well as utilisation of 2 PXI-6229 DAQ Card. There is also serial comms (RS-232). The error can occur on any VIs that carry out the above operations.

Attached is an error screenshot! Has anyone any ideas? Help would be greatly greatly appreciated!!

Rob

---

An update, for anyone else who had this kind of problem.

We found that the error occurred in two places - each one was a LabVIEW module step that called the same function in a DLL. It only happened in parallel testing and seems to be a buffer overflow or similar error (I am not familiar with the DLL, it was from our customer).

As a result, the buffer overflow caused a memory access/write fault and closed down LabVIEW. It didn't show any error or message. I found the error by literally disabling everything step by step until I found it. Not exactly elegant debugging, but the best I could do.

[OnlyOne]

Then it was a very big testplan if it took you 3 month to enable/disable 🙂

Thanks for sharing your solution.

[RGreene]

---

@OnlyOne wrote:

Then it was a very big testplan if it took you 3 month to enable/disable 🙂

Thanks for sharing your solution.

---

It didn't take quite that long, but we've only just signed off on it now as having no issue, after strenuous validation. 😄