Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331674 - Unrecognized Windows Sockets error: 10106: create
Summary: Unrecognized Windows Sockets error: 10106: create
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: Subversive
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Igor Burilo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-02 09:44 EST by Radu CLA
Modified: 2010-12-08 14:05 EST (History)
2 users (show)

See Also:

Attachments
screenshot of errors (34.67 KB, image/png)
2010-12-02 09:46 EST, Radu CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Radu CLA 2010-12-02 09:44:06 EST 
Build Identifier:  20090619-0625

I get this error when trying to Synchronize an SVN repository or when trying to update Eclipse 

Reproducible: Always

Steps to Reproduce:
1.Help>Install new software>All sites
Message:
  Unable to read repository at http://download.eclipse.org/technology/epp/packages/galileo/content.xml.
  Unrecognized Windows Sockets error: 10106: create
Comment 1 Radu CLA 2010-12-02 09:46:22 EST 
Created attachment 184354 [details]
screenshot of errors
Comment 2 Radu CLA 2010-12-02 09:47:40 EST 
I already searched the forums, some of the guys say that we should set environment variable SystemRoot to c:\windows; tried this, no luck ...
Comment 3 Roy Ganor CLA 2010-12-08 06:43:11 EST 
this is probably related to the subversive project
Comment 4 Alexander Gurov CLA 2010-12-08 14:05:09 EST 
Sorry, guys, but this is obviously system-level issue. Below you can see short description for this problem. Hope it will help you to solve problems with your operating environment. :)

WSAEPROVIDERFAILEDINIT
10106

Service provider failed to initialize.

The requested service provider could not be loaded or initialized. This error is returned if either a service provider's DLL could not be loaded (LoadLibrary failed) or the provider's WSPStartup or NSPStartup function failed.