You are viewing limited content. For full access, please sign in.

Question

Question

Quick Fields Error writing XML. %s

asked on February 11, 2018

Hi Guys

Can anyone guide me on this, I have a QuickFields session running on the same server as the Repository. I Use Laserfiche Capture Engine, pulling Documents from the Repository and sending them back after processing. It was working until I upgraded to Rio 10.3. 

 

The documents are now not getting processed by Quickfields, and the Error is"Error writing XML. %s"

 

Can anyone give me an indication as to what I can try looking at? I have reset up the session and still no luck.

 

Thanks for the Help in advance.


Regards

Christo

1 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on June 26, 2018 Show version history

This issue has been fixed in a hotfix for Quick Fields 10.3

3 0

Replies

replied on February 12, 2018

Hi Christo, we have filed Bug# 60648 for this issue. The workaround is to either de-select "Keep each entry as a separate document" or select "If the entry already has Laserfiche pages, overwrite them".

1 0
replied on February 12, 2018

Thanks for feedback working now. 

0 0
replied on February 19, 2018

HI Steven,

By doing this have a problem my Quickfields then doesn't use the metadata on the retrieved Entry. 

 

Any News on the FIX for Bug# 60648? Really big problem for me.

 

Regards

0 0
replied on February 19, 2018

Hi Christo,

I'm sorry this is such a hassle for you. We have a fix slated for the next hotfix. I can update this post when we have an ETA on that.

For the workaround, it looks like one of the workaround options (deselect "keep each entry as a separate document") doesn't capture templates and fields successfully. Have you tried the other workaround, selecting "If the entry already has Laserfiche pages, overwrite them"?

I've attached a set of LFCE > Document Content options that can scan in electronic document with fields. They are the default options + "If the entry already has Laserfiche pages, overwrite them". You may have to use a variation if you also need to capture image or text from the document. Let me know if this works or if your configuration is more complicated

2018-02-19_1154.png
0 0
replied on February 19, 2018 Show version history

The above workaround is for scanning e-docs with LFCE. If you're scanning image documents with LFCE, you can try some other workarounds:

1) removing pre-classification processes (or moving them to Page Processing)

or

2) using QF Scanning

Also, you can use QF 10.1 with a 10.3 repository without this issue, if you would prefer to wait for the hotfix instead of using the workarounds

1 0
replied on February 19, 2018

Hi Pieter,

 

Thank you for the in the detailed response to my problem. 

I have made a temp workaround to my problem, please let me know on ETA for the hotfix.

 

Thank you yet again, your response is appreciated.

 

Regards

 

0 0
replied on March 23, 2018

We are waiting for this hotfix

0 0
replied on April 30, 2018

Is there an update on when a hotfix will be released for this issue? 

0 0
replied on May 2, 2018

Hi, 

The Quick Fields team is actively working on a hotfix for this issue. We will update this post as soon as the hotfix is available. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.