01-04-2008 01:51 PM
01-07-2008 09:31 AM
01-07-2008 09:51 AM
Hi Rob,
My issue is not the pop up window, my issue is the error. I would like to know what causes this issue and also what is the best way to contain it.
Thanks,
Mudda.
01-07-2008 10:05 AM
Hi Mudda,
The most likely reason for error 62 is that the VI that opened the connection has finished executing and has closed, when a VI finishes executing in LabVIEW the resources are automatically closed to ensure any open resources arn't left dangling. To get arounds this simply ensure that the VI that opened the TCP connection remains running as long as the connection is needed, you may even want to consider making a seperate VI that does all of your TCP functions and leave it running in the background.
I hope this answers your question, all the best
01-07-2008 10:11 AM
01-07-2008 10:15 AM
Hi Mudda,
Error 62 and 66 are similar, 66 is basically a trap error for when the connection is closed by the peer - error handling it the same way as error 66 should do the job for you.
All the best,
01-07-2008 10:18 AM
01-07-2008 10:57 AM
No problems, if you have any other questions regarding this please don't hesitate to ask.
Best of luck!
10-12-2018 06:06 PM
I'm getting error 62 on the server side sometimes and I'm not sure why. I'm pretty confident that none of my VIs are being closed as post number 4 suggests. What other reasons are there that cause error 62?
10-15-2018 10:29 AM
Hey Johnathan,
This forum post is about a decade old, so the original posters may not be monitoring it anymore. You will probably get more responses by making your own post as recently created posts will bump to the top. Make sure to include relevant screenshots and your troubleshooting steps thusfar so that other forum users can get a clear understanding of your issue. Thanks!