My scrapebox - Help me....

It's not that you don't see the picture, it's that SB becomes a black window with this kind of error :D

Anyway, I noticed that the problem seems not depend from the remote desktop connection, but it just happens between 1k-2k total comments. SB window just freezes, and becomes black if I disconnect and then reconnect to the remote server.
 
same problem here, im still trying to figure out why its doing that.
 
There should be a blog that causes the problem so i would suggest splitting the list into parts (1000 or so) and find which part causes the problem.
Run bloganalyzer, outbound link checker or anything that actually visits the page.

It might be due to a virus too so maybe you should run the anti-malware plugin.
 
Last edited:
that screen. means your scrapebox is trying to load something enormous, so all you can do is wait honestly.
once it gets done doing whatever its doing, it will look better
 
Hi guys, thats a problem with a url that scrapebox is facing. One of the urls causes it to choke and die. Cut your lists in small pieces and run them one at a time. Lists that do not crash scrapebox can be merged together and reconstruct the original one. When a list crashes the server, brake that list to chunks until you find the problematic url. Once that is done, delete it and start merging the list again with the successfull small lists. It should take a while of your time but once done you have a clean list. There is no other way afaik, so patience is a virtue in this case ;)
 
It takes a lot of time, man.
How about running the list through Blog analyzer and Malware Filter? Is it enough?
 
Bro the problem is not with a malware site or anything like that. Its just a site in that lists that screws up scrapebox engine, be it with java or html or some bad/buggy code in it that causes scrapebox to crash. So its not spamlist filtering you need or something like that, its manual filtering.

In the case of the OP, lets say that you have 10k links. Download Notepad++ or any other FREE editor that displays Line Numbers. Since your list has 10k links, that means it will have 10k lines. Select everything from line 1 to line 2k and save the selection as list1.txt then from line 2k to 4k and save it as list2.txt and so on from 4 to 6k from 6k to 8k and from 8k to 10k.

Now you have 5 lists.
Start posting with the first list in scrapebox. If it works fine, Keep it aside. Lets say it works for arguments sake. Then proceed with list2.txt and use that on scrapebox. Lets say it crashes. Either note where it crashes, around what link number and copy everything before that number to the previous success list OR brake the list in chunks of 500 links and blast through each of them. This way proceed with the lists till you find the problematic url/urls. Then you merge all the OK lists and recreate your original one.

I have encountered this problem many times, one of the reasons that xrumer is king and scrapebox is still trying is that Scrapebox Crashes alot. Dont take me wrong, its a very good tool. But I use it for its addons mostly and not for its posting abilities. For posting i use xrumer. For work with links I use scrapebox and its awesome collection of addons. But lets not deviate from the thread. :)

It really does not take much time to clean the list. Somethings need to be done by hand also plus there is no such thing as a free meal. Either accept the fact that scrapebox is buggy and breaks with some sites, or be prepared to step in and take control of things yourself. I preffer the second approach :)
 
Last edited:
and what you do with 500k url list? I cannot split that in small parts. Also, I hadnt this problem before 1.15.3 or soemthing like that...
 
What is the problem in splitting a 500k list? Start by splitting it on 5 pieces of 100k links and so on. And if your problem is about not being able to work with huge files, there is a gread Free editor that can open gigantic files, counted in GB of sizes. Its name is JuJuEdit. Google it, get it and open/edit any filesize you ever wished but other editors could not.

Guys, dont just say IT CANT BE DONE. It can be done, it is being done, and sorry but YOU ARE LAZY TO DO IT is more true :P (not a personal comment, a generic one so dont be offended)
 
Thank you very much for your help, Kensai.

But say I'm running a 10k blog list and SB encounters this problem freezing, is there a way to recover the list of successfull posted blogs before the crash?

Unfortunately when this bug happens my SB window becomes black, so I can't see the post count (not to mention I use randomize posting to avoid mini-DDOS attack to the same blog, basically making impossible to recognize the broken URL by the comment posted counter).
 
Hey friends, Even i am with xsserver.eu and i had the same problem. Actually Scrapebox freezes when u log off. Try checking modification time of crashdump logs, u will see its the same when u logged off. This bug is called "Session Hangs During Logoff" and is a accepted bug by win 2008 team. There is a solution for it. . After this patch the problem gets solved. Also, scrapebox ver 1.15.5 is mostly crashing, so i am using 1.15.2, and crashing has been reduced considerably.

Please read this thread before you execute the patch.
Code:
http://redmondmag.com/Articles/2006/06/01/Speed-Up-Terminal-Server.aspx


Code:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\
Main]
"Force Offscreen Composition"=dword:00000001

[HKEY_CURRENT_USER\Software\Microsoft\Office\Common]
"QMEnable"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
LanmanWorkstation\Parameters]
"UseLockReadUnlock"=dword:00000001

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\
FileSystem]
"NtfsDisableLastAccessUpdate"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
Lanman Server\Parameters]
"IRPStackSize"=dword:0000000f
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service\
Lanman WorkStation\Parameters]
"UtilizeNTCaching"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
Session Manager\Memory Management]
"DisablePagingExecutive"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
LanmanServer\Parameters]
"SizReqBuf"=dword:0000ffff

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
Lanmanserver\Parameters]
"MaxWorkItems"=dword:00002004
"MaxMpxCt"=dword:00000800
"MaxRawWorkItems"=dword:00000200
"MaxFreeConnections"=dword:00000064
"MinFreeConnections"=dword:00000020
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
Lanmanworkstation\Parameters]
"MaxCmds"=dword:00000800
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\
Session Manager\Configuration Manager]
"RegistryLazyFlushInterval"=dword:0000003c

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
SessionManager\Memory Management\PrefetchParameters]
"EnablePrefetcher"="3"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\
CurrentVersion\Winlogon]
"DeleteRoamingCache"=dword:00000001
 
Last edited:
The bug mentioned above has nothing to do with the scrapebox, it has to do with the whole Remote desktop session. Scrapebox will crash also on your desktop pc or without you logging out of the server at all. Also, that is a bug from 2003-2004, we are now on 2011 so the bug is for ancient systems that have not been patched in eons!! :P

Also, do not logg off from the server if you want the programs that are working to continue doing so.

Instead, try pressing ctrl+alt+end and it will bring a window where you can LOCK your desktop. Esentially it saves your session and you can continue in it when you loggon again without the need to restart anything.

Try it!

@franky: man then you need to cut the list into smaller ones and start blasting them one by one. As far as I know the only thing you can save when scrapebox crashes is the work it had done so far in harvesting new links, in the Scrapebox\Harvester_Sessions folder. Nothing you can save from other jobs. Maybe programmers will add such functionality at some point.


For the record:
I am a sysadmin for 2 decades now, have administered OSes ranging from *nix to BSD, and from HPUX to Solaris and Windows to anything in between, so I have seen pretty much everything from bugs and problems in servers. That being said I pretty much know what I am talking about when I say something related to operating systems and servers.
 
Last edited:
@kensai, there is an addon doing this (called crashdump), it saves posted and failed when scrapebox is running. So you dont loose your work. Imma do some test, this is very a very bad bug -.-
 
I can say that Posing with Xrumer is very stable, but the successful rate is very low, compared with SB.
Not quite sure that there is a good Xas_AI to deal with Blog posting. :)
 
Xrumer is forum king, Scrapebox is blog king. With mods xrumer can be better than scrapebox, but out of the box and in general xrumer is used for forums and scrapebox for blogs. Xrumer success with profiles is very good. With blogs is way lower
 
I guess you have to wait a little bit before updating each time so that you're sure it isn't buggued
 
so we all just wait for an update???? I tried and split it in 1k list, the first five are buggy, like the others. crap.
 
Well, it seems they don't recognize this as a bug of their application. This is what they replied to me after 2 days (in my message I pointed them to this very topic):

"Hello,

When this happens, it's either caused by a remote desktop connection issue and ScrapeBox is still running fine but you no longer see the GUI being painted or a resource issue on the VPS and Windows can't paint the GUI anymore.


I bet when it's black like that, if you could connect a monitor to the VPS and view it directly instead of over RDP it would still be working fine with no black GUI.


Regards, ScrapeBox Support."

I think we should all send email to the support pointing out what Kensai wrote, otherwise this bug won't be solved at all.
 
Back
Top