10038 Error
Contents |
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & platforms Xamarin 10022 socket error ASP.NET C++ TypeScript .NET - VB, C#, F# Server Windows Server SQL Server
Socket Error Code 10057
BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows windows socket error 10061 Dev Center Windows Dev Center Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps Get started Design winsock 10061 and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps Get started
Wsa Error 10038
Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Networking and Internet Windows Sockets 2 Winsock Reference Winsock Reference Windows Sockets Error Codes Windows Sockets Error Codes Windows Sockets Error Codes Socket Options Winsock IOCTLs Winsock Annexes Winsock Enumerations Winsock Functions Winsock Structures and Typedefs Winsock Tracing Events Winsock SPI Windows Sockets Error Codes TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Windows Sockets Error Codes Most Windows Sockets 2 functions do not return the specific cause of an error when the function returns. For information, see the Handling Winsock Errors topic. The WSAGetLastError function returns the last error that occurred for the calling thread. When a particular Windows Sockets function indicates an error has occurred, this function should be called immediately to retrieve the extended error code for the failing function call. These error codes and a short text description ass
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 ipc error 10038 about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users getmsg error 10038 Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping
What Is A Socket Error
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 https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx 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 19 '08 at 6:37 SentliSh Have you tried on another platform (XP for example)? –paxdiablo Sep 19 '08 at 6:45 Is http://stackoverflow.com/questions/100074/winsock-10038-error-win2k3-server-baffling-behaviour 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 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
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 http://stackoverflow.com/questions/30028754/10038-wsa-socket-error-recv or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x http://www.masmforum.com/board/index.php?PHPSESSID=786dd40408172108b65a5a36b09c88c0&topic=7243.0 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 10038 wsa socket error recv up vote 1 down vote favorite I'm currently trying to implement a class to create and use TCP connections. (I'm quite new in c++ so it's possible that I socket error forgot something obvious, even though I've been seriously checking my code) Note that later I'll be implementing a second class to handle new connections so there are some parts of the code that are incomplete/arranged and I hope that this won't disturb you while trying to understand it. Here's my problem: The server and the client both seem to work fine (I'm always checking on my listen, bind, connect functions: no error) and I'm apparently able to send data with 10022 socket error the client but when I try to read it from the server, I get WSA error 10038 (which means that i'm executing the recv() on an invalid socket). I've been looking it up for a few days now and can't seem to find my mistake. Besides the tests in the code, I've used "netstat -an -p tcp" to check the state of the connection and everything appears fine but the server just won't receive the data. NB: I'm using Visual Studio 6 (Yup, it's old, but it's mandatory so...) and winsock, not winsock2. If I forgot something just ask, i'm trying to be as complete as possible but it's not impossible to forget something. Here are my source codes, i tried to cut it to the essential but i'm afraid that the mistake can be pretty much anywhere: CmTcpTransport.cpp /** Initializes the TCP connexion (socket) in CLIENT or SERVER mode. It does not connect yet. @param strIPAddress: IP Adress to reach nPort: Port to connect to hSocket: client Socket if SERVER mode nTcpMode: mode for this connexion SERVER(1) or CLIENT(2) @return an int to get the exit point of the function */ int CmTcpTransport::initialize(std::string strIPAddress, unsigned int nPort, SOCKET hSocket, int nTcpMode) { m_nTcpMode = nTcpMode; cout << "Creating TCP connexion..." << endl << endl; if (nTcpMode == 1) // SERVER { serveraddr.sin_family = AF_INET; // address family Internet serveraddr.sin_port = htons (nPort); // Port to connect on serveraddr.sin
Links and Website Archived Old Forum Files Links for VC and MASM 128553 Posts in 15254 Topics by 684 Members Latest Member: mottt The MASM Forum Archive 2004 to 2012 General Forums The Workshop (RESOLVED thanks tedd)Winsock Error Code: 10038 « previous next » Pages: [1] 2 Author Topic: (RESOLVED thanks tedd)Winsock Error Code: 10038 (Read 10665 times) blackwc Guest (RESOLVED thanks tedd)Winsock Error Code: 10038 « on: May 06, 2007, 05:28:56 AM » Code:scan proc uses edi invoke socket,AF_INET,SOCK_STREAM,0 .if eax != INVALID_SOCKET mov sock,eax .else invoke MessageBox,hwnd,NULL,addr error,MB_ICONERROR .endif invoke WSAAsyncSelect,sock,hwnd,WM_SOCKET,FD_CONNECT .if eax==SOCKET_ERROR invoke MessageBox,hwnd,NULL,addr error,MB_ICONERROR .endif ;------------------------------------ invoke GetWindowTextLength,hbox1 inc eax invoke GetWindowText,hbox1,addr target,eax ;------------------------------------ assume edi:ptr sockaddr_in mov [edi].sin_family, AF_INET invoke inet_addr,addr target mov [edi].sin_addr, eax invoke htons,80 mov [edi].sin_port,ax invoke connect,sock,edi,sizeof sockaddr_in .if eax==SOCKET_ERROR invoke WSAGetLastError invoke dwtoa,eax,addr buffer .if eax != WSAEWOULDBLOCK invoke MessageBox,hwnd,addr buffer,addr error,MB_ICONERROR .endif .else invoke closesocket,sock .if eax==SOCKET_ERROR invoke WSAGetLastError invoke MessageBox,hwnd,addr target,addr error,MB_OK .endif .endif assume edi:nothing retscan endpRight around "connect()" it returns 10038.Which is invalid or corrupt handle, What's wrong with it? « Last Edit: May 10, 2007, 06:24:02 PM by blackwc » Logged blackwc Guest Re: Winsock Error Code: 10038 « Reply #1 on: May 07, 2007, 06:12:20 PM » Any help would be greatly appreciated... Logged Tedd Procrastinator Extraordinaire Member Posts: 2210 Reality Bytes Re: Winsock Error Code: 10038 « Reply #2 on: May 07, 2007, 07:14:15 PM » Well you're checking for errors (good!) and displaying error message boxes (good) and then carrying on anyway (not good!!)If there's an error, then it's not a good idea to continue - you'll only get more errors (such as 10038: WSAENOTSOCK - which means the socket handle you're giving isn't a valid socket handle.) Logged No snowflake in