Hi,
I'm attempting to extract tabular data to Excel format. I have used the recognize/analyze feature and revised the layout to match what I want to extract. When I click "export" I get two warnings (which I understand) about language and a suggestion to obtain a higher resolution image. This question is about an error: "Export Error: FENExportPageOperation".
I don't know the cause of this error and I have no strategies for avoiding the error.
Does anyone have experience with this error? Can you provide suggestions for next steps?
Thank you!
Andrew
Comments
16 comments
I am also facing the same issue. Whenever I try to export after recognize, ABBYY Finereader quit unexpectedly. Any solve to this issue will be highly appreciated.
I have the same problem, but ABBYY Finereader for Mac doesn't quit, it just gives the error "Operation Stopped: FENExportPageOperation." The export commences, prompts for the Excel filename and location, but then nothing happens other than the error shown above in the status box.
I am also attempting to export tabular data to Excel. It worked flawlessly for some two dozen exports but now suddenly has stopped working.
Did either of you find a solution? This is suddenly happening to me, too, and I don't see a workaround. But the program does little good if you can't export the PDFs you create.
I have no solution for this problem.
Hello,
I would like to inform you that the reported error message appears after adding/changing the separators in the Table areas. The issue is known to our Research and Development department. Our developers are working on the fix of the issue.
As a possible workaround, I suggest using automatic conversion without editing the Table area.
Accept our apologies for the inconvenience caused.
I have the same error, but I'm afraid suggesting that a workaround is to use the automatic conversion doesn't help as if I use the automatic recognition it's missing columns on the table so the data is unuseable...
Dear Richard,
The only option currently available to avoid the error message is to allow FineReader PDF to automatically analyze the page, rather than manually adding separators. We apologize for the inconvenience and for not being able to offer an alternative solution or fix at this time. Please rest assured that our developers are actively looking into the issue.
And as mentioned already, that option doesn't work, because Finereader fails to read the page properly and the tables are all messed up. it is absolutely essential to add the manual separators to be able to OCR the page.
"Please rest assured that our developers are actively looking into the issue."
Really? This original report is THREE YEARS OLD so clearly this isn't a priority to you, but to your users this renders the application totally unfit for purpose.
If there is no workaround - even not after 3 years - this means that ABBYY is unfit for use. I want my money back!
100%.
This is ridiculous.
A fundamental feature of the software. It literally has dedicated buttons on the toolbar to add and remove the table lines manually.
It simply doesn’t work
Won't recognise the tables automatically
Won’t let you define the tables manually
Therefore TOTALLY UNUSEABLE and DOES NOT FUNCTION AS ADVERTISED
Time to hit the socials and spread the message wide
The software doesn’t work and the developers don’t care
STILL NO UPDATE - STILL NOT WORKING AS ADVERTISED
This software is NOT FIT FOR PURPOSE
I am having this problem too. I only want to export to PDF. But my PDF has tables. Please fix this!
Hi! Please wait for the reply in the ticket #652167.
I'm still having this problem as well (Open Support request #658752). I reached out to the support team and was given the same response of "Don't use manual separators," which as has been pointed out, defeats the purpose of this software. The whole reason most, if not all of us use this, is to be able to manually assign the table parameters. Given all of this, I still have no choice but to use this software (for now) and have found the following things tend to help with exporting to .xlsx. 1) Move row and column separators rather than deleting and replacing. 2) Add/ delete as few separators as possible. 3) Worst case scenario, break the file into smaller chunks (I had to use a single, separate file per page in the most extreme situation). This is far from acceptable and I hope the dev team takes this seriously in the next update, but I was able to export all of my pages by doing the steps above. Hope this helps!
Is this bug EVER going to be fixed? I have a single page which fails 100% of the time when I add a single horizontal table separator which FineReader failed to add when it analyzed the page. There is no mechanism I can find to correct this error and have the page exported. Even converting the table to be text will still generate this error when exported once FineReader has gone into this error condition.
Hi RD Payne! I’ve created a support ticket based on your comment. One of our support representatives will be in touch with you shortly.
Please sign in to leave a comment.