Failed to connect to remote application (fatal error)

[LabBEAN]

Symptom:

After building a debuggable application (EXE), I tried to connect to it by:

1.  Running the EXE

2.  Operate » Debug Application or Shared Library...

The IDE tried to connect to the EXE and then posted this dialog:

After clicking OK, my Connection Status looked like this:

Explanation:

It turns out you cannot debug an application if there are any subVIs without diagrams.  In my case, I'm calling someone else's VI in ONE location.  That VI happens to NOT have a diagram.

In case someone ever sees this puzzling "fatal error" dialog during connection, watch out for VIs where the diagrams have been removed.

Work Around:

Use a DDS (Diagram Disable Structure) to comment out the VI w/o diagram.  Then, build your application and debug it.  Enable the DDS case with the VI before building the final application.

[Dennis_Knutson]

It's just a very bad idea to work with VIs that do not have a diagram. By doing so, you prevent the user from upgrading the LabVIEW version for no reason. Password protect them if you must but always insist on VIs with diagrams.

[LabBEAN]

Tell me about it.  If you know how to convert hBitmap (DDB) to a LabVIEW image cluster PLEASE let me know.  This is the *only* downside of the G Toolbox...

[richjoh]

I currently have the problem described at the top of the this thread.

In my case, my LV2009 build connects just fine to the debugger. Now the same code is saved using LV2010, then rebuild the application and each time the OS reports the application has stopped and "failed to connect" message appears.

Any ideas how I fix this, I'm unable to debug the exe (the source code works just fine).

[richjoh]

I successfully debugged my application without use of the Project Operate debugger. How: (I set "open FP when called" and FP indicators on VIs for debugging the exe). But although all is well the debugger still fails to connect, even after creating a new build in the project from scratch.