Discussion:
Failed to Start Debug Server
(too old to reply)
brianlachlan
2007-01-09 20:10:06 UTC
Permalink
Anyone know why I would get "Failed to Start Debug Server" message prompt when I launch my executables on a windows 2000 pc?
 
forgetting to include something in the installer?
 
Thanks,
Brian
Robst
2008-03-31 22:40:07 UTC
Permalink
Hello:
 
I've developed an application and it has the same problem. When I run the executable, the message "Failed to start debug server" appears. I click the OK button, and the application runs normally. The message doesn´t appear everytime. 
 
Any ideas why this might happen?
 
Thanks in advance.
Lauren L
2008-04-01 22:40:15 UTC
Permalink
Hi Robst,
 
You are probably getting the error because you have "enable debugging" set in the advanced properties of the vi, so it tries to start the debug server upon startup.  In order to eliminate the error message, you should just change the setting to disable debugging and recompile the executable.
 
Regards,
 
Lauren
Robst
2008-04-02 18:10:11 UTC
Permalink
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.
Lauren L
2008-04-03 22:10:05 UTC
Permalink
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
Trey B
2008-06-12 16:10:05 UTC
Permalink
The Debug Server may have problems starting if NI Service Locator isn't running.  Try these: - Verify that NI Service Locator is running.
- Go to Start»Run
- Enter services.msc
- Make sure that NI Service Locator has Started and is set to Automatic
- If using a firewall, or any application that can block ports, make sure that Port 3580 is open.&nbsp; This is the port that NI Service Locator uses.&nbsp; <a href="http://digital.ni.com/public.nsf/allkb/CEF5A3568A5DA71D8625732800520EA1?OpenDocument" target="_blank">KnowledgeBase 2GD9CL6Q</a> has a listing of all ports that may need to be open.
- If you just installed NI software, be sure to restart your computer.
If all else fails, a work around is to disable Debugging in your Application's Build Specifications.&nbsp; Double check the application's .ini file on the run-time PC.&nbsp; If you have these two tokens, they should look like:DebugServerEnabled=FalseDebugServerWaitOnLaunch=FalseIf you can reproduce this with a very simple VI (a while loop writing the Loop Iteration to a indicator for example), please post the build executable.&nbsp; We might be able to find the problem.Trey BApplications EngineeringNational Instruments
gpww
2008-08-12 15:40:26 UTC
Permalink
I have this problem, and it doesn't seem to be intermittent. I checked for the NI Services Locator and it's not listed. My system is not a development system, but I have installed the runtime. I'm running VIsta 64-bit OS.
Stephen_S.
2008-08-13 19:40:10 UTC
Permalink
Hi gpww,&nbsp;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.&nbsp;In general, this should only be a problem if you have debugging enabled, as discussed above, and should go away if you disable debugging. &nbsp;Regards,Stephen S.&nbsp;
Continue reading on narkive:
Loading...