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

Question

Question

Workflow failing with 9086 Error

asked on February 15, 2017

My client is currently having a workflow fail during its search repository activity. It is returning an error 9086, which leads me to believe it is a syntax error, but the users say nothing in regards to the query has been changed, and it was run successfully yesterday. I even copied the query run yesterday and attempted to manually test it, and I got the same error. Here s the custom query(sensitive information omitted):

{[New Account Application]:[Document Type]="Transfers In Misc", [Document Sub-Type]="TA *"} & {LF:Name="*", Type="DB"} & {LF:Created="%(DateTokenCalculator_yesterday)"} & ({LF:Creator="QFScan"}) & {LF:LOOKIN="ClientRepoName\Client Files"}

 

I modified the LF:LOOKIN portion to have a leading backslash("\ClientRepoName\Client Files"), as recommended by this answers post(https://answers.laserfiche.com/questions/78866/Search-Repository-just-keeps-running#78898 ), but that did not resolve the issue so I was hoping if someone could point me in the right direction. They are on LF 9.2.1. Thanks!

Messages.PNG
Messages.PNG (56.81 KB)
0 0

Replies

replied on February 15, 2017 Show version history

What type of sensitive information was omitted?

Your path should start with the repository name. No backslash is needed at the beginning of it.

When you say you tried manually running it, you mean from the LF Client? Did you replace the date with the correct one? Have you tried removing criteria to see which one is causing the problem?

If you look in the "Activities" tab for the search activity, what was its duration?

0 0
replied on February 15, 2017

I only changed the name of the repository near the end of the query, everything else is the same in regards to what I omitted.

By manually I mean I ran the workflow manually in the workflow designer

I will try it in the client and see if the same thing happens, and test out the various criteria as well, my only concern is that no changes have been made to the workflow of LF and it was working yesterday and yet will not work today.

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

Sign in to reply to this post.