Microsoft say this about Winsock error 10024 - WSAEMFILE:

Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread.

Full details of Winsock TCP error 10024 - WSAEMFILE:

Berkeley description: Too many open files. No process may have more than a system-defined number of file descriptors open at a time.

Microsoft C description: Too many open files. No more file handles are available, so no more files can be opened.

WinSock description: Similar to Berkeley & Microsoft C, but in reference to sockets rather than file handles (although the descriptions in the v1.1 specification say "no more file descriptors available"). Generically, the error means the network system has run out of socket handles.

User suggestions: It may indicate that there are too many WinSock applications running simultaneously, but this is unlikely since most network systems have many socket handles available. It could also occur if an application opens and closes sockets often, but doesn't properly close the sockets (so it leaves them open, as "orphans"). To recover the orphaned sockets, you can try closing the application and restarting it to recover the open sockets; you may have to end all WinSock applications (to force an unload of the WinSock DLL).