Failed to cleanup the Windows Socket Interface
25 Feb 2005 5:41:00 UTC
Topic 187977
(moderation:
I keep getting a " Failed to cleanup the
Windows Socket Interface" BOINC GUI Error. I am running Windows
XP SP2 on an Intel 2.8 GHZ Hyper threading processor. Any suggestions?
If I restart my processor BOINC seems to work, but at some later time I get this error appearing, and BOINC doesn't appear to run if I try to restart it, I get the described error each time I try.
Failed to cleanup the Windows Socket Interface
)
> I keep getting a " Failed to cleanup the
> Windows Socket Interface" BOINC GUI Error. I am running Windows
> XP SP2 on an Intel 2.8 GHZ Hyper threading processor. Any suggestions?
> If I restart my processor BOINC seems to work, but at some later time I get
> this error appearing, and BOINC doesn't appear to run if I try to restart it,
> I get the described error each time I try.
This is a new error message for me. What version of the BOINC client are you using? Is it 4.19?
Director, Einstein@Home
'Failed to cleanup the
)
'Failed to cleanup the Windows sockey interface' usually is caused by trying to start the client a second time. Look in your start up folders for extra enteries. If you are running as a service there should be no BOINC in the start up.
BOINC WIKI
BOINCing since 2002/12/8
You got it spot on there.
)
You got it spot on there. This is usually caused by trying to run 2 instances of BOINC.
However I have also seen it when trying to run BOINC in XP SP2 under a user that does not have permission to run the software. ie installed as admin but no permission set on its files for restricted users.... this is usually accompanied by another error about BOINC being unable to open stderr.txt for writing so I doubt thats wht the problem is here.
Reason for running 2 instances? I've come across a couple so far...
1. AS mentioned, if BOINC has been installed as a service and is still in the the 'Start Up' folder in XP. (usually All users -> Start Menu -> programs -> startup). Windows will start BOINC at boot and then attempt to start it again at log in.
Resolution: Step 1: Confirm BOINC is installed as a service and set to start automatically. Step 2: Remove icon from Startup.
2. When BOINC is running from Startup only, the BOINC icon sometimes 'dissapears' from the system tray when XP is starting up / Logging in and so appears not to be running. If you check Task Manager you will see that it is still taking CPU time so it is actually running fine. Anyway, if you didn't check Task Manager, and just went ahead and clicked on the BOINC icon in your start menu, you will actually be trying to launch a second instance of BOINC an you will get the error described. Ususally after you get this message the BOINC icon reappears in the system tray and so everything seems OK (except you got that error message)
Resolution? Run BOINC as an automatic service or delay its startup for a few seconds after log in so that the rest of the system has started before BOINC tried to. (this works!)
Maybe a simple addition for BOINC future version? An optional start delay of xx seconds?
cheers,
Paul.
Wanna visit BOINC Synergy site? Click my stats!
Join BOINC Synergy Team
I have also seen this error
)
I have also seen this error once on a machine where I installed the client as a different user than I then tried to run it. Might be a problem with access right, too, tough unlikely on XP (Home at least).
BM
BM
> I have also seen this error
)
> I have also seen this error once on a machine where I installed the client as
> a different user than I then tried to run it. Might be a problem with access
> right, too, tough unlikely on XP (Home at least).
>
> BM
>
>
it is likely - it happens - with XP home! the only way I can find to get around it is to start BOINC as a system service... or else always log in to the account what installed it in the first place. (makes XP accounts kinda useless!)
ps. its much easier to sort out in XP pro.
Wanna visit BOINC Synergy site? Click my stats!
Join BOINC Synergy Team
> > I have also seen this
)
> > I have also seen this error once on a machine where I installed the
> client as
> > a different user than I then tried to run it. Might be a problem with
> access
> > right, too, tough unlikely on XP (Home at least).
> >
> > BM
> >
> >
>
> it is likely - it happens - with XP home! the only way I can find to get
> around it is to start BOINC as a system service... or else always log in to
> the account what installed it in the first place. (makes XP accounts kinda
> useless!)
>
> ps. its much easier to sort out in XP pro.
>
The administrator can change the rights for user groups to directories. Right click on the BOINC directory, properties, security, Add..., Enter "Users" into the edit field, click check names, Click OK, Select Modify and Write, click ok.
BOINC WIKI