Remotely debugging an executable ... no Error List?

[josborne]

I built an EXE for LabVIEW code.  And the EXE works fine on my development machine.  But it fails to run (broken arrow) on other machines. So I figured I'd use the remote debugging tools.  I can connect to the remote EXE and see the panel and diagram (nifty!), but the Error List is empty.  It says "No VIs with errors".  So it won't tell me WHY it has a broken arrow.  

At this point, I am just guessing why the arrow is broken on deployment machines.

[Kyle97330]

In most cases I find that it's a missing external dependency such as a DLL.  If you use a ".config" file to get .NET DLLs working then you might need one for your EXE.  Or there might be drivers that installed DLLs that you're missing.

Also, since you can see the block diagram remotely, sometimes you can open up subVIs and find some with working run arrows and some with broken ones.  If you narrow it down to a subsection of VIs with broken arrows and they have common functionality, that can help track it down.