I have been getting an error upon launch since upgrading to 4.09. The error number is -108, then when closing the window, I get a second error indicating that BOINC could not "clear the windows sockets" or something to that extent.

The thread linked below appears to discuss this same problem (hence my posing it in this forum, and not Questions / Problems...)

http://setiweb.ssl.berkeley.edu/forum_thread.php?id=4726

The conversation that followed the post above did not seem to address the socket error, and it seems that for the poster, reinstalling solved the issue. I've reinstalled to no avail.

This happens each time I start BOINC (e.g. each time my computer boots up)

Other info:
- Running CP, LHC, and SETI
- Recentely received an email from CP asking me to update the client_state.xml file - did this right about the same time as the 4.09 upgrade
- OS: Windows XP Pro

Any insight into resolving this error would be greatly appreciated!

Thanks all

I think the socket error happens when you have a second user log on after user switching. At least this is what I am finding. Previous versions seemed to produce a different error code.

> I think the socket error happens when you have a second user log on after user
> switching. At least this is what I am finding. Previous versions seemed to
> produce a different error code.

If that is the case, the problem should be clearable with a reboot.
<p>
For BOINC Documentaion: Click Me!

Thanks for the feedback to date.

I only have one user logging on to my system - so no user switching here.

I've rebooted many times (I don't leave this particular PC running full time...) the error happens each time.

I will try the suggestion to uninstall and delete all references and see what happens - will probably take me a day or two to get to that, I'll let you know what happens. In the meantime, there are no apparent problems with BOINC running WU's, uploading, reporting, and downloading more. Just get the error everytime BOINC starts.

I have to agree with Julian Rouse in saying that the only time I have seen the "Failed to clean up sockets" error is when I have two users on one system, one using the system via remote desktop, so the first instance of Boinc is the reason the second one can't clean up.

No remote users here - also not using BOINC Spy or any of the other add-ons.

> Thanks for the feedback to date.
>
> I only have one user logging on to my system - so no user switching here.
>
> I've rebooted many times (I don't leave this particular PC running full
> time...) the error happens each time.

Well, I did say Should ... :)

I have seen windows get confused over file permissions too ... and they were so bad once the administrator account was told he did not have enough privelege to do anything with the file ...
<p>
For BOINC Documentaion: Click Me!

I to have had this error opn all of my computers at some time (NT4, Win2000, XP). It happens when after you log on the BOINC icon does not show up in the System tray but is running. If you then try to start the BOINC_GUI.EXE program again it loads the incon into the tray and gives the sockets error.

Andrew - thanks for the post - got my mind working. I was so fixed on the fact that the error started happening when I edited the client_state.xml file upon request from CP.net, that I wasn't thinking about anything else.

Turns out I had a shortcut to BOINC_gui.exe in the windows "startup" folder in both my XP profile, and the "All Users" profile. While only one icon appears in the actual start menu, apparently, the app tries to launch twice...

Deleted one of the shortcuts and the error has stopped happening.

Thanks all!