01-09-2007 01:50 PM
01-10-2007 02:30 PM
01-11-2007 07:43 AM
Xaq. I am using LabVIEW 8.2. I do not want the program to run when opened.
"Problem: VI Settings saved in a build specification are ignored while building the application.
Workaround(s): Simply change and save the settings in the VI properties of the actual VIs before building the application. This works for all settings except for Run When Opened. A workaround for this setting is tot go to the Advanced page of the build specification and check "Enable debugging" and "Wait for debugger on launch". One side effect is this will include the block diagrams of the VIs and extra code for debug tool support.
ID: 41D846X2, 40HEDDJG "
So why am I getting that prompt "Failed to start debug server" ? The application runs fine after I click on OK and press the run arrow.
I guess it is really not an issue unless I want to debug the exe. Also, it does not look that professional to users when they see a message prompt "Failed to Launch Debug Server". I get a lot of "whats this?" My response "heck if I know".
Brian
03-31-2008 05:25 PM
Robst - CLD |
Using LabVIEW since version 7.0 |
04-01-2008 05:18 PM
04-02-2008 01:09 PM
Hello Lauren:
Thanks for the reply. Yes, I know I've enabled debugging, and that's what I want, since I want to be able to see what the executable is doing, we're still testing the application. I know I can always debug from LabVIEW but if I can debug from the executable itself, I'd prefer it. The message rarely appears, so I'd like to know why it appears, it's a bit of curiosity. Any ideas?
Robst.
Robst - CLD |
Using LabVIEW since version 7.0 |
04-03-2008 04:42 PM
Robst,
We have seen a couple of instances in which this error message occurs intermittently. It has been investigated, but as of yet, cannot be reproduced. If you are able to isolate the behavior to a specific function or situation, we may be able to trace it down.
Regards,
Lauren
06-12-2008 10:45 AM
08-12-2008 10:28 AM
08-13-2008 02:36 PM
Hi gpww,
If you are not able to see your NI Service Locator in your list of services, that is most likely the source of the problem. Make sure that you are not having issues with your firewall and that port 3580 is open. I am looking into using NI Services Locator with a Vista 64-bit system, and will let you know if there are any problems with this.
In general, this should only be a problem if you have debugging enabled, as discussed above, and should go away if you disable debugging.
Regards,
Stephen S.