Scrapebox error "control socket abort"

zacatictac

Power Member
Joined
May 2, 2010
Messages
660
Reaction score
805
Anybody elese get the "control Socket abort exception!" error when posting alot of comments with scrapebox? I cant get through my whole list because it happens every 20 minutes or so. Any one have any ideas on how to fix this?
 
same thing here ... I tried to ask this before but got no answer from anyone... sorry

but yes... happens to me as well
 
Oh well. Still an amazing program regardless. Would be nice to get a fix of some sort for this but i can live without. Just figured I'd ask.
 
Well I searched that and came up with the below. Maybe you can find something useful in there.

Code:
http://www.google.com/search?client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&channel=s&hl=en&source=hp&q=%22control+Socket+abort+exception!%22&btnG=Google+Search

I personally have not got that error before.
 
this happens to me when im using xrumer AND scrapebox
try using less conecctions and close your p2p softs maybe
 
Same here, I don't see why Scrapebox developers couldn't fix it. They come up with fixes every other day it seems.
 
I have had this too.

The only thing that stopped it was a reboot. I think that if you keep the desktop and scrapebox open for too long it gets flooded. I had this socket error then started to have memory errors.

I rebooted and turned off every background program except my antivirus. I unistalled everything that opened up on startup, which included ico mounting disks, TomTom and all sorts of junk.

I have now have been working all week and not seen the errors again.
 
From the SB support:
The socket abort exception comes from Windows, when a socket times out and winsock fails to abort it the background exception occurs. It's not proxy related, it can happen with or without proxies and is only happening to a small amount of users.
 
The socket abort exception comes from Windows, when a socket times out and winsock fails to abort it the background exception occurs. It's not proxy related, it can happen with or without proxies and is only happening to a small amount of users.

Doesn't seem like small amount of users to me...

I have had this too.

The only thing that stopped it was a reboot. I think that if you keep the desktop and scrapebox open for too long it gets flooded. I had this socket error then started to have memory errors.

I rebooted and turned off every background program except my antivirus. I unistalled everything that opened up on startup, which included ico mounting disks, TomTom and all sorts of junk.

I have now have been working all week and not seen the errors again.

Many of us run Scrapebox and Xrumer at the same time.
 
meh.. just started getting the same error.. it's really annoying :/
 
OMG..I didn't get that error.Cz I couldn't update to new version.I think that's new version error.
 
I get this too.. And this IMO is not a small number of users for sure,,
 
Does enabling fast poster connection balancing help? (under settings). Cause windows does produce this error. Winsock is built into your windows and it is the problem. Scrapebox is merely asking windows to create a lot of connections, windows isn't managing those connections properly and thus the errors occur.

Curious, what operating systems and what service pack are you using? I have never really had this error that I recall. However I only use windows 7 latest service pack and windows server 2008 R2, which is the latest service pack. There is certainly something to be said for using the the most up to date version of windows.
 
Back
Top