I googled this, but didn't find a definitive solution. I harvest using about 250000 keywords, after like 700000 harvested URLs I get this error:
Access violation at address xxxxxxx in module 'scrapebox.exe'. Read of address 00000008.
then Scrapebox crashes.
I use 100 private proxies with 20 connections (multi-threaded harvester). My VPS runs Windows Server 2008 with 2GB RAM and 2.26 GHz quad core CPU. I only run Scrapebox, so it should have enough RAM and CPU. I also have free disk space. Using the latest Scrapebox.
By the way how can I resume the harvesting session after a crash? I see the harvester sessions folder, but how can I resume the harvesting (using only those keywords which left)? If I hit the Harvest button again, it will start over.
Most generally when there is an access violation its that some outside program is interacting with scrapebox and causing it to crash. 1 instance of scrapebox is going to be fine on 2GB of ram, "probably". Windows probably sucks 500-800MB of memory and whats left is about 1.5-1.3GB of memory and thats pretty decent. SB can cap at 1.8 being a 32 bit app, but your in a good range.
Things like firewalls, anti-virus, sandboxie etc... and other programs can hook the process or mess with the sockets etc... and cause SB to crash. Try killing everythign except core windows processes and services and and/or just shut them down one by one till you find the culprit. Add allow rules in security programs.
I always update my Scrapebox.
According to Scrapebox that "made up" url is indexed in Bing.
When checking manually its not even listed.
Im not completely sure how SB reads the data in the response from bing, but I grabbed the response code and sent it along with the issue to the developer. Same thing happens to me in .59. Im sure they will fix it up.
Anyone else using the OBL checker? I have to use that quite often and it makes it hell to use. First of all, it memory leaks. The process grows in memory by about 100 megs for each 1500 checked links. You need a gig and a half of spare memory if your list is 10k URLs long. If you have to check 2 million URLs, then all you can do is split that into 10k lists and run these one at a time. That's the only way I find is working for me. Imagine the time spent on this task. Anyone here doing it more effectively?
Another thing is, whether I set it to 25 connections or at 80, it spits out entire blocks or Timeout-ed URLs. Probably a sixth of all the URLs will get a timeout and these have to be repeated. Another time waster. I need to add here that for instance I don't get any timeouts in the Blog Analyzer or other addons that I use. It's only the OBL checker that has a problem. It seems to me like it's buggy and for some reason it was overlooked for a long time from getting an update
I don't use it much, but you have to remember that everythign it does, it does in memory. So as it goes along, its holding all prior data, along with loading what could be Massive pages and then trying to read them, and extrapolate data, all in memory in real time. So if you load in 10K 10MB blog engine pages, imagine trying to load those, grab data, store data and continue to load.
Are you loading in randomized lists? IF you are not then its trying to load a bunch of urls from the same domain at once, which could cause the end server to ignore your request as it things your hammering, and/or it could just be to slow to respond. Also if you hit a site that has a fast enough server but hit a ton of large pages, your internet connection and/or DNS might not be able to resolve/load the pages in the timeout allotment.
Id say its not got an update because its fairly straight forward and likely wouldn't need updates. When I have used it, it seems to work fine for me.