Hej,
We have a weird problem with our software. We have a custom middleware that communicates through sockets. It run's succesfully on 50+ servers, clusters, both 2003 and 2008 OS. Sometimes depending on the wish of the developer that uses our middelware we deploy on their workstation (Microsoft XP) a version of our middelware.
We get the following error on a few workstations:
Either the application hasn't called WSAStartup or WSAStartup failed
I think it's about 1% of the the workstations that have this problem note: everyone has the same machine, the software on that machine can be different, other tools, development, .....
Does anybody of you has any idea how we can bugfix this? Or how we can get the reason why we get this error? We don't think it is an wrong use of sockets in our code, because our middelware component is already running 5+ years on servers (never had that problem) and other machines.
Kind regards,
Jonathan
For posterity: Always check what WSAStartup returns. If it's something else than 0 then handle error appropriately.