New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Either the application has not called WSAStartup, or WSAStartup failed. (os error 10093) #56
Comments
That's the Winsock DLL initialization function, deep below the level on which I'll keep this open for a couple of days, but I'd prefer to close it later, resolved or not, since I don't think there's anything that can be done about it in this crate; it exposes the issue, but doesn't cause it. |
Thanks for your answer! But |
It doesn't, but the linked issue is the closest analogue I can find. Look at |
True, and I found this: tokio-rs/mio#1046 which removes |
The dummy UDP socket creation has just moved to |
I see, so what's happening is something bad in |
It's probably some strange interaction of the user's environment with Winsock. Windows has gotten better in the past decade, but there are still problems which are best "solved" with one of three R's (restart/reboot/reinstall). Perhaps this is one of them. If it's reproducible, a low-level call trace ought to help. |
Let's close this then, nothing you can do about it anyway, thank you very much for your expertise! |
Hi,
A user of my app using
ldap3
just send me logs containing:What does it mean?
The text was updated successfully, but these errors were encountered: