An Udp Protocol Error Occurred Windows Sockets Connect Failed
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
Socket Error 10054
Bing Application Insights Languages & platforms Xamarin ASP.NET C++ TypeScript .NET what is a socket error - VB, C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students
Socket Error Codes Linux
Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges socket error 10054 connection reset by peer Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps Get started 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 Explore What’s new for Windows socket error 10053 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps Get started 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
Register Basket Products MDaemon Private Email Server MDaemon Hosted (Cloud) Email SecurityPlus AntiVirus for MDaemon Outlook Connector for MDaemon SecurityGateway for Email Servers RelayFax Network Fax Manager MailStore Archive Server http://www.altn.com/Support/KnowledgeBase/KnowledgeBaseResults/?Number=KBA-01196 Purchase MDaemon Private Email Server SecurityPlus AntiVirus for MDaemon Outlook Connector for MDaemon ActiveSync for MDaemon SecurityGateway for Email Servers RelayFax Network Fax Manager MailStore Archive Server MailStore Upgrade/Renewal Coupons/Promos eLearning Technical Support Agreement Upgrade/Renew License Renewal Sync Licensing Overview Referral Program Downloads MDaemon Private Email Server SecurityPlus AntiVirus for MDaemon Outlook Connector for MDaemon BlackBerry for MDaemon SecurityGateway for Email Servers RelayFax Network Fax socket error Manager MailStore Archive Server Support Request Support Literature Knowledge Base Product FAQs Product Web Help eLearning Video Of The Month Webinars Community Forums Beta Group Alt-N's Blog Alt-N's Idea Engine Technical Support Agreement Phone Support Security Update Blog Partners Technology Partners MDaemon Hosted Email Providers Find A Partner Become A Partner Partner Portal Security Threat Center Transportation Partners Company Management Press Room Associations socket error 10054 Policies and EULA Careers Contact Us Home > Support > Knowledge Base > Knowledge Base Results KBA-01196 Winsock Error Descriptions Winsock Error Descriptions
WSABASEERR (1000) No ErrorNo Error. There's at least one WinSock implementation that will occasionally fail a function and report this as the error value, even though the function succeeded. You should simply ignore this error when it occurs.WSAEINTR (10004) Interrupted system call A blocking operation was interrupted by a call to WSACancelBlockingCall. An asynchronous signal (such as SIGINT or SIGQUIT) was caught by the process during the execution of an interruptible function. If the signal handler performs a normal return, the interrupted function call will seem to have returned the error condition. Developer suggestions: You need to be prepared to handle this error on any functions that reference blocking sockets, or any calls to blocking functions, if you allow the user to cancel a blocking call. Whether to handle it as a fatal error or non-fatal error depends on the application and the context, so it's up to you to decide. WSAEBADE (10009) Bad file numberA file descriptor argument was out of range, referred to no open file, or a read (write) request was made to