This topic contains 4 replies, has 2 voices, and was last updated by  aklock 2 months, 2 weeks ago.

  • Author
    Posts
  • Participant
    aklock
    Member
    Member since: 11.05.2018
    Number of posts: 15

    Hi all,

    I’m trying to get to the bottom of an issue that is occurring with some of our PDF uploads (using multipart/form-data). From the response we see:

    {"code":400,"message":"[error.validation.verifyDocument.documentExtractError]","messageKey":"error.validation.verifyDocument.documentExtractError","name":"Validation Error"}

    And in the server logs we see:

    2019-02-19 11:55:26.677 [20819]ERROR  : Could not find search string [SIGNATURE OF CONTRACTING OFFICER].
    2019-02-19 11:55:26.677 [20819]ERROR  : Command [ExtractMultiTextAnchor (file: /tmp/20190219/ffd0fee0-033b-412f-b717-30f493a4dd85-5711-
    ...
    [2/19/19 11:55:26:733 CST] 000002a8 OperationResp W   Operation update returned error error.eslx.inputValidation.documentExtractError

    So my guess is, inside the PDF there is a signature object “SIGNATURE OF CONTRACTING OFFICER” which is declared somewhere and not not found, thus throwing the error.

    I’m told that if we use the exact same JSON and PDF and load it via Postman it works fine. I’m going to attempt to reproduce the error inside my sandbox account, but was hoping that your trained eye will be able to spot something obvious and lead me into the right place.

    I appreciate any help. Thank you!

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 828

    Score

    0

    Hi aklock,

    From the server log, it looks like in your JSON, you have an extractAnchor with text of “SIGNATURE OF CONTRACTING OFFICER” while when doc engine was trying to find it in uploaded document, the string can’t be found.

    Another question is, are you in on-premise environment? Because when I was testing on this issue, I can reproduce the same error message in SaaS 11.18 version but not in SaaS 11.23 version. So this issue should also related to instance version because of the release updates.

    Duo


    Duo Liang
    OneSpan Junior Technical Evangelist
    Participant
    aklock
    Member
    Member since: 11.05.2018
    Number of posts: 15

    Score

    0

    Thanks Duo Liang. That’s great that you were able to reproduce it. We are on-premise and still waiting to hear back from our admin about versions, but was able to get the following from sysinfo:

    {"frontend":{"version":"16.3.11-usps","cachebuster":"1515794728407","builddate":"2018-01-12 17:02:13 EST"},"backend":{"schema":"16.10.4","version":"16.6.17","timestamp":"2018-02-02 15:43+0000"}}

    Not sure how those versions match up with the SaaS ones, but does it still seem like it could be a version issue?

    Thanks again!

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 828

    Score

    0

    Hi aklock,

    I just talked with our Technical Consultant who had a screenshare with you guys this morning about your issue and have known more about your workflow. I was told that your version seems to be 11.3.3 Classic UI.

    If you were using a PDF generator that fills in data into PDF file and then your application used that PDF file to upload to OSS, could you check whether the PDF was properly generated before sending?

    Duo


    Duo Liang
    OneSpan Junior Technical Evangelist
    Participant
    aklock
    Member
    Member since: 11.05.2018
    Number of posts: 15

    Score

    0

    Thank you for the version! I’m sort of outside of those two teams so I wasn’t on the screenshare this morning. I think verifying the PDF is properly generated before sending is a great idea. But, this is where I get confused though, since the JSON and PDF being sent in the request seem to be correct. And the maddening bit is that it seems to work fine in Postman, so I’m sort of at a loss as to what’s going on. I’m still building a test case (we are calling the REST API via Oracle’s UTL_HTTP) to see if I can get it to reproduce. Will keep you posted! Thanks again Duo.

    Andy K

You must be logged in to reply to this topic.