If there is searchable text inside the pdf, that is extracted. Otherwise the whole PDF/TIFF is OCR'd. No Zonal OCR.
Got this message (with other db names listed as well) on the server: db: "graham" {make object! [ code: 329 type: 'script id: 'bad-bad arg1: "ODBC" arg2: {[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified} arg3: none near: [dbase: open join odbc:// db] where: 'forever Something wrong here, doesn't seem working for me. What did I miss?
I did. I have the same ODBC DSN name and database path as your instruction, so I didn't change this line: "remr" %/c/emr/server/cache-listener
Just let it run and see if it happens again. Amazon just announced a change to their API .. I hope that is not the cause. But I've seen that error one before and it just then goes away.
Have you setup the queue details in Settings/User/Fax Inbox/SQS Queue? Have you started sending files using FaxImport.exe ?
Does the sync-faxboxes.exe have to be in the same folder as synapse-server? Now: Build time: 13-Sep-2009/11:44:36+12:00 db: "remr" {make object! [ code: 329 type: 'script id: 'bad-bad arg1: "ODBC" arg2: "[ODBC Firebird Driver]unavailable database" arg3: none near: [dbase: open join odbc:// db] where: 'forever ]} waiting in outer forever loop for 5 mins I logged in Chat
Says it can't connect to your ODBC source. No, it doesn't have to be in the same directory I'm on chat now.
fixed ODBC, now: Edit: nevermind, I forgot to sign up for SQS, now it's working! I suppose I don't need to keep the client FaxImport running, I can just run it when needed right? Now when I go to Inbox-Faxes, it just says "loading...", what do I do next?
If they never load, it may mean you have way too many in your inbox. I'll have to check the code to see whether I limit to 50 or 100.
I've released server 60 ... which limits the fax inbox to 100. If that is still too much, I'll reduce it again ... it's probably the ocr text that is too much.
I've released server 60 ... which limits the fax inbox to 100. If that is still too much, I'll reduce it again ... it's probably the ocr text that is too much.
