PXI

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 11 on FTP Attempt

Labview v8.5
Using FTP Get Buffer.vi to retrieve the contents of a file generates the following error
Code: 11 (Too many files open)
Error TCP Open Connection in FTP Open Session.vi->FTP Get Multiple Files and Buffers.vi->FTP Get Buffer.vi->read train report file.vi->MASTER.vi
 
Three machines in the system
A: Labview executable running on XP ( typical PC hardware)
B: PXI machine running Labview RT (where problem occurs)
C: Labview executable running on XP (typical PC hardware)
 
Machine A is regularly ( 30s interval) ftp'ing back a single file from machine B.
Machine B occasionally is occasionally ftp'ing back two consecutive files from machine C (one after the other)
 
Machine B fails with above message. Can occur soon after a reboot, or after a considereable time after a reboot.
Once failure has occurred, attempting to ftp in to machine B results in  failure as well.
Rest of machine B appears to operate as normal ( including shared variables ).
We have deployed similar scenarios (with previous versions of labview) and have not encountered this problem.
 
Possible options we have considered without success (so far):
* Problem occurs when ftp in to machine B occurs whilst ftp from machine B is also occurring.
* File open handles are running low and occasionally running out
 
Other questions/comments:
* Have noted an ftp related bug in the 8.5 release notes - is there other acknowledged bugs in ftp ?
* Can we monitor (programmatically) on RT system number of used file handles/set number of file handles ?
* Since the whole open/ read/close operation occurs within the single FTP_ReadBuffer.vi, it is hard to see that we are somehow leaving a file open.Apart from ftp'ing, there is some, but little, file access occuring on machine B.
0 Kudos
Message 1 of 2
(2,888 Views)
Hey DWJ,
 
This was reported to R&D (#64535) for further investigation. 
This may be due to the fact that if the TCP listener is not responding, the connection is not closed before another is opened. A possible workaround is to add an additional close connection.
 
Thanks for the feedback!
Aashish M
CEO
TransferFi
www.transferfi.com
0 Kudos
Message 2 of 2
(2,874 Views)