9003 Errors - Unable to bind ports

Since switching to the Enterprise version I have all kinds of issues actually opening the appliaction to add new scrapes. I have quite a few scrapes running throughout the day and as such when they are running i am unable to get into the application. I get the 9003 error which looks like the database has been locked.

This essentially only gives me a couple of hours in the working day to get into the app and make changes to any scrapes and add new ones. As you can imagine this is just not an acceptable state of affairs as It really hamstrings my ability to use this program effectively. I didn't have these issues in the Pro version as i could always get into the app. Is there a setting change i need to make or change the port number?

Please advise as this is just becoming an unuasable app for us.

Thanks

I looked closer, and figured

I looked closer, and figured out your issue. You need to:

  1. Stop screen-scraper (any scrapes, server, and workbench)
  2. Edit your screen-scraper.properties file in "screen-scraper home/resource/conf"
  3. Add the line:
    AllowMultipleSimultaneousInstances=true

This can cause some issues though as you will be able to edit a scrape/script that is currently running, and such a conflict can really corrupt your database. If you're careful though it can work fine.

I would guess that you have a

I would guess that you have a scrape that is causing screen-scraper to crash/stop unexpectedly. In that case, the program doesn't get the chance to close processes using the ports.

To check, look at your error.log. Ideally it should be empty, so if there are any errors therein, you should track them down and handle them. Odds are, in so doing you'll stop the crashing issue.

Richard, Is it possible that

Richard,

Is it possible that you are still running the Professional Edition installation? If so, uninstall Professional Edition and see if the problem goes away.

-Scott

I have checked the error logs

I have checked the error logs and sorted out a few issues. A get the odd issue which is unavoidable down to a url being too long.

I still have the odd issue but most of the time i just have to stop the *.jar application in teh taks manager.

I still have the pro version installed but i only use this occasionally when i can't get into the enterprise version. I don't have an scrapes running in this that are automated.