Exporting Scraping Sessions Fails
I am attempting to export a valid scrape from Screen-Scraper Professional 4.0. The resulting document is named appropriately, but has a file size of Zero KB - which is obviously incorrect.
Does anyone have a suggestion to resolve this problem?
Thanks in advance.
Interesting...
I'm unsure about why that would be happening...
Which platform are you running screen-scraper on? I hesitate to assume anything :P
Usually these sorts of problems are caused by some unexpected factor, like an external program (virus protection, etc) that just gets in the way at the wrong time.
Is there anything that you've changed about your computer? Updates, on-access virus scanners, etc, etc?
Are you trying to overwrite an existing exported scrape of the same name, or are you only trying to save a brand new file?
Are you saving to some remote location, or to a local drive?
I'm just typing "out loud", trying to decide what could possibly affect the process of exporting. If screen-scraper doesn't throw any error, then I'm curious if anything else might be interfering.
Tim
I'm running Mac OS X 10.5.4.
I'm running Mac OS X 10.5.4. I'm not re-writing over an existing file, nor have I made any notable changes to my system that could affect this.
I've since installed Screen-Scraper Enterprise 4.0. I am able to successfully export from this version, to the same destination on the same machine.
One suggestion I have is to
One suggestion I have is to make sure that you're character encoding is set to UTF-8 or ISO-8859-1. If the export fails because of the encoding, though, screen-scraper should warn you.
Does that change anything when you try to export?
Problem Solved
Character encoding was and is still set to ISO-8859-1. I upgraded to the latest unstable version(4.0.21a), attempted the export and it was successful.
The problem is solved, although I am still not sure what caused it in the first place.
Thank you for the suggestions.
That's interesting that the
That's interesting that the update to the alpha version fixed the problem. We thought of suggesting doing as much, but thought it best to just start with the character encoding.
I'm glad you figured it out! Most changes made in the alpha versions stay in the code for major releases. Hopefully this bug will not return to future versions!
Tim