10038 Socket Error
Contents |
One games Xbox 360 games PC wsa error 10054 games Windows games Windows phone games Entertainment All socket error 10022 Entertainment Movies & TV Music Business & Education Business Students & socket error 10057 educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security
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 socket error 10038 socket operation on non socket 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
One games Xbox 360 games PC socket error 10035 games Windows games Windows phone games Entertainment All
Socket Error 10053
Entertainment Movies & TV Music Business & Education Business Students &
Socket Error Codes Linux
educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security https://support.microsoft.com/en-us/kb/819124 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 https://support.microsoft.com/en-us/kb/155738 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 http://stackoverflow.com/questions/100074/winsock-10038-error-win2k3-server-baffling-behaviour 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 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 socket error 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 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 10038 socket error 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 can try removing any non-microsoft ones. share|improve this answer answered Feb 20 '09 at 23:46 a_mole add a comment| up vote 0 down vote Thanks so much to a_mole for the idea of checking for layered winsock providers. We are having problems with some of our PC's and TimesTen DB. When we try to setup and ODBC Client DSN, we get a 10038 error. On examining the netsh output from the affected PC's, we found that they h