Asynchronous Socket Error 10013
Contents |
Symptoms Whenever a Socket Error 10013 is present you will know it. Usually this error means that you cannot access your Windows mail messages. You will be able to open the socket error 10013 windows live mail e-mail program itself, but you will not be able to send or receive any
Socket Error 10013 Error Number 0x800ccc0e
e-mail messages rendering your program useless. Socket Error 10013 Causes A Socket Error 10013 can and will occur if there are
Windows Socket Error 10013 Pidgin
settings on your computer that are not properly configured. In many instances it is an anti-virus software that will either not scan the e-mails properly or will take too long to scan them and thus prompt
Unexpected Socket Error 10013
the error. Other possible causes can be a corrupt registry, misconfigured files with your firewall protection, or possibly a virus. Socket Error 10013 Fixes The easiest way to deal with a Socket Error 10013 is to disable the anti-virus scanning capabilities. Mostly speaking, a scan of your e-mails is an unnecessary step that can eat up CPU usage and cause a slowing and/or timing out of your PC which will cause unexpected socket error 10013 filename unspecified line number 0 the Socket Error 10013 to occur. Steps: Uninstall your anti-virus program. Restart your computer. Reinstall you anti-virus program in “Custom Mode.” When offered the choice for “E-mail Scanning” select no or uncheck the box. Complete setup. Restart your computer to allow effects to take hold. See Also Dealing with Socket Error 10013 « wiki-errors.com Socket Error 10013 - Microsoft Community Socket 10013 error when trying to connect some programs ... How To Fix Socket Error 10013 Error Number 0x800ccc0e. Errors ... C++: Windows Socket Error 10013 – Stack Overflow What Are the Common Causes of Socket Error 10013? python - socket.error: [Errno 10013] An attempt was made to ... TCP error code 10013: An attempt was made to access a socket ... socket.error: [Errno 10013] Port forbidden access permissions socket error 10013 when starting hpsum on 2008r2 - Hewlett ... Personal tools Namespaces Article Search Our Products Main Page Applications .Net Framework Error AOL Browser Errors Installer Errors Internet Explorer Macro Errors Media Player MS Outlook Network Errors Outlook Express Windows Live Articles DLL Errors Exe Errors Ocx Errors Operating Systems Windows 7 Windows Others Windows Vista Windows XP TuneUp Tips Browser Tuneup Computer Tuneup Pages About Us Cat List Support Contact Us Help Center How to Uninstall Refund Policy Legal Disclaimers P
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 socket error 10013 fix & platforms Xamarin ASP.NET C++ TypeScript .NET - VB, C#, F# Server Windows goagent socket error 10013 Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search socket error 10013 battlefield 3 Microsoft Search Windows 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 http://wiki-errors.com/dealing-with-socket-error-10013/ 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 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx 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 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
Search Search Forums Advanced Search Go to Page... Thread Tools Display Modes #1 04-09-2014, 02:52 PM briank Registered User Join Date: May 2006 https://forums.vandyke.com/showthread.php?t=11460 Location: Northbrook, IL Posts: 6 Unexpected socket error: 10013 [Solved] After upgrading from SecureCRT 7.2.1 to 7.2.3 under Windows 8.1 Update and Norton Internet Security 21.2.0.38, I was getting the error "Unexpected socket error: 10013" when attempting to connect to a remote host. Inspired by the discussion at https://forums.vandyke.com/showthread.php?t=11256, I tried the following fix, which worked: Under Norton Internet Security > Settings socket error > Network > Smart Firewall > Program Rules > Configure, change the entry for SecureCRT Application from "Auto" to "Allow" and click Apply. briank View Public Profile Visit briank's homepage! Find all posts by briank #2 04-09-2014, 03:02 PM bgagnon VanDyke Technical Support Join Date: Oct 2008 Posts: 2,716 Hello briank, Thanks for posting an update. Since these two posts socket error 10013 deal with different error codes, but similar issues, I will make a note in the other thread to direct people to this info also. This link is a resource from Microsoft that documents these error codes (10013 and 10093). __________________ Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 bgagnon View Public Profile Find all posts by bgagnon Tags error, firewall, norton internet security, socket « Previous Thread | Next Thread » Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) Thread Tools Show Printable Version Display Modes Linear Mode Switch to Hybrid Mode Switch to Threaded Mode Posting Rules You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is On HTML code is Off Forum Rules Forum Jump User Control Panel Private Messages Subscriptions Who's Online Search Forums Forums Home General File Transfer Scripting Secure Shell SecureCRT on the Mac All times are GMT -7. The time now is 06:30 AM. Contact Us - VanDyke Software - Archive - T