09-16-2016 12:00 AM
Hi all,
I am testing the Debug Application feature with a cRIO 9065 over a slightly flaky 4G link. When attempting to connect a remote debug session, the Debug Applcation of Shared Library window became unresponsive (everything was greyed out) and I could not close it. After several minutes of waiting, I terminated the LabVIEW.exe process and then tried to establish another debug connection. This time I keep getting the error message:
Debug connection refused by specified server: Only one debug connection is allowed per application or shared library
So presumably the initial debug attempt connected and left a connection active, though I could not use it. How can I remotely terminate an existing debug connection / session without rebooting the cRIO?
Edit: After waiting a period of time I managed to establish a new debug connection. After closing the session (right-click -> Remote Debugging -> Quit Debug Session), then starting a new session I get the same error message above. Any ideas?
09-16-2016 01:26 PM
Hi MichaelBalzer,
You are correct in saying that you are trying to instantiate another instance of that debug connection since the first one was not properly closed, which is what is throwing the error.
It's not ideal, but you'll have to restart the cRIO. If it's deployed in the field, you can restart it through MAX on a development machine without having to physically interface with the hardware. Here's a little more information about your options when it comes to rebooting: http://digital.ni.com/public.nsf/allkb/B9C4DA1E5F3BACBA862578C000633B76
From there, be sure to use the Quit Debug Session option that you mentioned and everything should be good to go.