Why does my TCP Connect VI return error code 42

[thisisnotadream]

None of the other threads regarding this "Generic Error" seem to apply. 

I have a real-time application in LV 8.6.1.  A simple target-host connection via cross-over cable.  Multiple host applications (on a static IP) connecting and interacting with a single target application.  Each host connects to a separate connection module that connects, receives, and transmits data to and from the host.  Stuff's been working pretty well, but as I add more of these connections during integration, problems have been coming up.  Specifically with the attached VI which is called periodically.  It no longer seems to want to connect.  Upon startup of the top-level VI, the connection attempt returns error 56 (expected as the server is not running on the host), occasionally a 63 pops up and occasionally a 42 pops up.  Eventually after about 30 seconds, the only error that is returned is error 42.  Once I start the server I never see a connection attempt.  I have started WireShark on the host and don't see any connection attempts there either. 

Not sure what 42 means...Please help.

Thanks,

Dan Marlow

[Ben]

Guessing based on experience...

The target is either memory or CPU deprived.

Check the performance of the target.

Ben

[thisisnotadream]

Memory is great.  CPU utilization under 10%.

I did a little more digging.  Apparently it may not be too kosher to call TCP VIs from within a timed loop.  I found that some calls were buried within some timed loops and am working on pulling them out into while loops.  Hopefully this will correct the issue...