[RESOLVED] winsock2 send() is failing, with mystery error code '22119'

[ahoodin]

I have a Legacy Product that I support. When you try to enter values called parameters into the ASP Classic screen, the asp calls a VB6 Active-X dll to get the parameter validation limits and compares the value the user entered to the limits using some JavaScript (and will revert the value if it is not in limits). If the value is in limits, the ActiveX component sends the parameter to the devices that require the parameter via a TCP Client Send to each of them. If any of the Clients fail to get the parameter, the system sends feedback to the validation page, and the value is reverted to the original value.

The send command is wrapped ws2_send(), which is a winsock2 call. The code wrapps winsock 2 calls, so the errors should be winsock2.

My issue is that one of these Sends is failing, with the error code '22119'. I compared this to the Winsock Errors, and it doesn't line up with any of them. I am happy that I have an error code but what does it mean?

I will attempt to debug, but it may be tough. Any suggestions?

[ahoodin]

This was a custom return value. The code actually successfully completes the Client Send and Recv, and then for some odd reason, if there is a status returned from the device, it is entered in the return value of the function that calls the client send. This is pretty odd, since this should have been raised as a fault in the system, not registered as a communications error.