Home » Forums » screen-scraper » screen-scraper public support

Input output error when running from a .bat file

I have a scrape that we normally run from a .bat file on our server and it is working. I need to make some adjustments and when I try to run it locally from a .bat i get the following error in the log file.

An input/output error occurred while connecting to 'https://mydomainname.com/search.cgi'. The message was mydomainname.com.

I get this error anytime i try to run a scrape from outside the UI, it normally works fine from inside the application, but this scrape was not designed to run that way.

I am currently on version 3.0.67a enterprise edition

Thanks

‹ Force multi-part? setting dynamic parameters ›
jgardner on 01/21/2008 at 1:48 pm

Input output error when running from a .bat file

jgardner,

Thanks for sharing. We also have an FAQ on what particular ports screen-scraper uses if you need to modify your firewall settings.

http://www.screen-scraper.com/support/faq/faq.php#ServerRefusingConnections

-Scott

 swilsonmc on 01/31/2008 at 12:05 pm

Input output error when running from a .bat file

Thanks for the reply, I finally got it working. The problem was not with screen-scraper, it seems that although the UI had no problem getting through my firewall, the application was being blocked when run from a .bat. I recently removed Norton Antivirus and switched to Windows OneCare and the problem went away instantly. So if anyone else is having this issue try temporarily disabling your antivirus/firewall and see if that fixes it.

Good luck.

 jgardner on 01/30/2008 at 11:32 pm

Input output error when running from a .bat file

jgardner,

It sounds like the problem resides in the batch file itself. Could you post the contents of the batch file; as well as, the log that is generate?

My guess is that you need to encapsulate the url string using a different delineator (double-quote rather than single quote or vice-versa) and/or escape out the forward slashes of the url (looking like https:\/\/mydomain.com\/search.cgi). Likely the former, though, since a string properly encapsulated should not require characters to be escaped except for the delineating characters themselves.

One more thought, are you running Vista?

Also, I would encourage you to back up your work and upgrade to the latest version, 4.0 that was released just yesterday.

Let us know.

Thanks,
Scott

 swilsonmc on 01/22/2008 at 11:28 am