Asynchronous Socket Error 10038
Contents |
One games Xbox 360 games PC windows socket error 10038 games Windows games Windows phone games Entertainment All socket error 10038 delphi Entertainment Movies & TV Music Business & Education Business Students & socket error code 10038 educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security
Asynchronous Socket Error 10061
Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Band Microsoft asynchronous socket error 10053 Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads asynchronous socket error 10060 with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the
Asynchronous Socket Error 10049
Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute:
Socket Error 10054
Sign up 10038 socket error up vote 3 down vote favorite 1 Is there any solution for 10038 server error .i have done coding in c++; the server runs fine 10 to 12 hours but sudenly it gives 10038 socket error https://support.microsoft.com/en-us/kb/819124 c++ visual-c++ sockets share|improve this question edited Oct 16 '10 at 9:00 asked Oct 16 '10 at 8:32 SunilRai86 34231025 add a comment| 3 Answers 3 active oldest votes up vote 6 down vote Without seeing your code: the symptom you describe sounds like you are leaking memory/resources, i.e. you are forgetting to free/delete objects you are allocating. It could also be a timing issue. I suggest you post your (cut-down) code. 10038 (WSAENOTSOCK): Socket operation on nonsocket. An operation was attempted on http://stackoverflow.com/questions/3948164/10038-socket-error something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid. share|improve this answer answered Oct 16 '10 at 8:34 Mitch Wheat 214k28345442 1 downvoters please leave a comment. –Mitch Wheat Jan 30 at 0:00 Can you explain the cryptic: "An operation was attempted on something that is not a socket" –Silvester Aug 11 at 8:53 add a comment| up vote 6 down vote I bet you are accessing a socket that you already closed. This is a very common timing bug in WinSock programming - the good news (and bad news, because it's hard to reproduce) is that you are not hitting it very often so it's likely your code does not need much work to make it perfect. I think you should add thread-safe diagnostics that output a string including the socket value (an int, basically) on every open and close, and from anywhere you see this 10038 or other unexpected errors. If you can add those diagnostics and then set up a stress test that focuses on open and close areas in your program (you may need to strip down the code to a small subset for unit testing of the sockets handling, maybe doing this back-to-back on localhost, or to two LAN-connected machines) then it will likely manifest much more quickly than 10-12 hours and you may find and fix other timin
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn http://stackoverflow.com/questions/100074/winsock-10038-error-win2k3-server-baffling-behaviour more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Winsock - 10038 Error - Win2K3 Server - baffling behaviour up socket error vote 0 down vote favorite Attempt to send a message through a socket failed with WinSock error 10038. After around 40 seconds, messages are received successfully from the same socket and subsequently the send() is also succeeding in the same socket. This behaviour has been witnessed in Windows Server 2003. Is this any known behaviour with WinSock and Windows Server 2003? windows-server-2003 winsock share|improve this question asked Sep asynchronous socket error 19 '08 at 6:37 SentliSh Have you tried on another platform (XP for example)? –paxdiablo Sep 19 '08 at 6:45 Is there an asynchronous create call that hasn't finished before you try to access the socket? –Brad Bruce Sep 19 '08 at 10:49 add a comment| 3 Answers 3 active oldest votes up vote 3 down vote accepted Winsock error 10038 means "An operation was attempted on something that is not a socket". Little trick to find info about error codes (usefull for all sorts of windows error codes): Open a command prompt Type "net helpmsg 10038" What language is your application written in? If it's C/C++, could it be that you are using an invalid socket handle? share|improve this answer answered Sep 19 '08 at 12:46 Otherside 2,2561318 add a comment| up vote 0 down vote Not a platform issue, I can guarantee that. Most likely, whatever variable you are using to access the socket handle is not thread-safe and is being used in the send() call before the actual socket is created. Another possible cause is the presence of layered winsock providers. "netsh winsock show" at a cmd prompt will show you the installed providers and you c