Error The Descriptor Is Not A Socket
Contents |
360 games PC games socket error bad file descriptor Windows games Windows phone games Entertainment All Entertainment
Socket Descriptor 0
Movies & TV Music Business & Education Business Students & educators
Socket File Descriptor Exceeds Limit
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Socket File Descriptor C
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 Lumia All socket descriptor in unix 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
IDProjectCategoryView StatusDate SubmittedLast Update0003211SOGoBackend Generalpublic2015-05-08 15:552015-11-03 14:47ReporterwimmerAssigned ToludovicPriorityhighSeveritycrashReproducibilityalwaysStatusclosedResolutionfixedPlatform[Server] LinuxOSDebianOS Version8 (Jessie)Product VersionTarget VersionFixed in Version2.3.3Summary0003211: "[ERROR] descriptor is socket descriptor in linux not a socket descriptor" by using gnustep-base1.24Descriptionsogod child processes lose socket error 10038 their "port 20000" listening on Debian 8 with gnustep-base1.24. They stay running, but they are unusable. After what is a socket error while when sogod master process has no child listening on port 20000, SOGo goes to endless loop and fills log with lot of error messages: May https://support.microsoft.com/en-us/kb/819124 08 17:20:41 sogod [14360]: [ERROR] <0x0x7ff1727c5cd0[WOHttpAdaptor]> http server caught:
Sign in Pricing Blog Support Search GitHub This repository Watch 64 Star 264 Fork 152 rabbitmq/rabbitmq-dotnet-client Code Issues 16 Pull requests 0 Projects 0 Pulse https://github.com/rabbitmq/rabbitmq-dotnet-client/issues/23 Graphs 'Descriptor is not a socket' when running on Mono #23 Closed skolima opened this Issue Jun 25, 2014 · 4 comments Projects None yet Labels None yet Milestone http://www.altn.com/Support/KnowledgeBase/KnowledgeBaseResults/?Number=KBA-01196 n/a Assignees No one assigned 4 participants skolima commented Jun 25, 2014 Every now and again, I'm getting the following exception when running on Mono: System.Net.Sockets.SocketException: The descriptor socket error is not a socket at System.Net.Sockets.Socket.SetSocketOption (SocketOptionLevel optionLevel, SocketOptionName optionName, Int32 optionValue) [0x00000] in
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 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 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 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