ServerTCPWrite times out after the application has been running for a day or two

[LabWindows_newbie]

Hi all,

Our application registers itself as a TCP server and once a client is connected, status data (about 300 bytes) will be sent back to the client at a rate of once a second.

This part works fine for a day or two and then I will get a -8 error back from the ServerTCPWrite function call which indicates that the write failed. The

client side seems to process the data in a timely manner so I don't think the receive buffer is filled. Has anyone seen this problem before?

Regards,

LabWindows_newbie

[RobertoBozzolo]

Just a suggestion: have you tried to call GetTCPSystemErrorString when you get the error? According to documentation there is a chance that returned string is more descriptive that the enumerated type.

I have personally never received such an error: one of our application is proven working for months using regularly ServerTCPWrite function; it is to be noted though that our write rate is slower (1 write per minute or so).