Error 10091
Contents |
360 games PC games error code 10091 Windows games Windows phone games Entertainment All Entertainment synapse error 10091 Movies & TV Music Business & Education Business Students & educators wsa error 10054 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet error 10050 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
Winsock Error 10091
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
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search
Error 10091 Wsastartup
Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website error 10091 xp Testing Store Headlines Experts Exchange > Questions > Winsock error : 10091 Want to Advertise Here? Solved Winsock error : 10091 Posted error 12007 on 1998-09-22 C 1 Verified Solution 4 Comments 1,795 Views Last Modified: 2008-03-10 I'm using Winsock 2 on my win95 and I got this error while I call WSAStartUp. My value for LOBTYE(wVersionRequested) and HIBYTE(wVersionRequested) are both https://support.microsoft.com/en-us/kb/819124 2. The returned values in LPWSADATA seems to be okay to me, but WSAStartUp still returns with the value 10091. I'm sure the DLLs that are used are the correct ones. The documentations say this error means "network subsystem unusable". So what does it mean? What else should I check? Thanks. 0 Question by:totoro030898 Facebook Twitter LinkedIn Google LVL 86 Best Solution byjkr As there's no Winsock 2.2, use wVersionRequested = MAKEWORD( 2, 0 ); https://www.experts-exchange.com/questions/10083093/Winsock-error-10091.html err = WSAStartup( wVersionRequested, &wsaData ); specifying wVersionRequested = MAKEWORD( 2, 2 ); will lead to an error Go to Solution 4 Comments LVL 1 Overall: Level 1 Message Expert Comment by:marvinm1998-09-23 WSASYSNOTREADY (10091) Network subsystem is unavailable. This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check: · that the appropriate Windows Sockets DLL file is in the current path, · that they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one WINSOCK DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded. · the Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly 0 LVL 86 Overall: Level 86 C 28 Message Accepted Solution by:jkr1998-09-23 As there's no Winsock 2.2, use wVersionRequested = MAKEWORD( 2, 0 ); err = WSAStartup( wVersionRequested, &wsaData ); specifying wVersionRequested = MAKEWORD( 2, 2 ); will lead to an error until MS publishes Winsock 2.2 ;-) 0 Message Author Comment by:totoro0308981998-09-23 Hi jkr, In the Windows Sockets 2 Application Programming documentation (Revision 2.2.2, Aug 7 1997), there is an example under WSAStartup,
computer or another computer on the local network or on the Internet. When you attempt to verify your network configuration https://sourceforge.net/p/synalist/mailman/message/4058303/ by using the TCP/IP Ping.exe command-line utility (Ping Localhost or Ping 127.0.0.1), you may receive the following command-line error message: PING: transmit failed, error 10091 error code 10091 Cause: This issue can occur if an incorrect Windows Sockets dynamic link library (DLL) file is in the current path or there is more than one simultaneous Windows Sockets implementation. If there is more than one Winsock.dll file on your computer, be sure error code 10091 the first one in the path is appropriate for the network subsystem currently loaded. This issue can also occur if the Windows Sockets implementation is not currently installed or is configured incorrectly. Resolution: 1. Recover winsock32. Check this page Troubleshooting Winsock2 Issue 2. Remove and then reinstall your networking components. To do this, follow these steps: Step 1: Remove Networking Components and Dial-up Networking Step 2: Remove Network Registry Keys Step 3: Reinstall Networking Components and Dial-up Networking Related Topics PING: transmit failed, error code PING: transmit failed, error code 10050 or PING: Transmit failed, error code 65 PING: transmit failed, error code Articles PING: transmit failed, error code 65 - case study This web is provided "AS IS" with no warranties. Copyright © 2002-2015 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.