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

Question

Question

Workflow- RM Search Repository Activity in Workflow throwing 9008 error

asked on December 24, 2024

Hello,

We have a RM Workflow that uses a Search Repository activity. When we run the WF with this activity we receive a "General Database Error-9008".

If we test the search syntax used in the WF, we get a normal search result response.

Below is the search syntax that we are using (I used Customer Name instead of our real customer name for the folder path):

({LFRM:DispEligibilityAction="A",EligibilityDate<="%(Date)"} | {LFRM:DispEligibilityAction="D",EligibilityDate<="%(Date)"} | {LFRM:DispEligibilityAction="T",EligibilityDate<="%(Date)"}) & {LF:LOOKIN="Customer Name\Central Services\Records Management\Physical Records"}

We have used this same syntax for multiple customers without issue.

Note-Below are the Additional Properties we have selected that we need for their token values.  We unchecked the box for "Total Document Size" and we were able to successfully run the WF.  Like I stated we have used the same search syntax and additional properties for multiple customers and have not encountered this issue.

If anyone has some insight, we would appreciate it.

Thanks,

Jeff Curtis

0 0

Answer

SELECTED ANSWER
replied on January 5

Hi Jeff,

Now the "Total Document Size" column was included in search results. This column is known to cause performance issues and if not needed is recommended to not be included.

If the column is needed, SQL maintenance may help improve performance of this column search, but failing that, you can reach back out for an option to include in the database to increase the timeout.

Thanks

2 0

Replies

replied on December 24, 2024

Will you receive the same error when you running the exactly the same search in LF web client or desktop client on the same repository as Workflow connected with? How many entries are there in the folder "Customer Name\Central Services\Records Management\Physical Records"?

0 0
replied on December 30, 2024

Hey Juan,

We do not encounter any errors running the syntax search in the LF Windows or Web Client.

There are 20 entries in the folder we are searching in.

Thanks,

Jeff

0 0
replied on December 30, 2024

Hi Jeff, as you mentioned uncheck property 'Total Document Size' in Workflow makes it running smoothly. When you performed test in LF client, was the column 'Total Document Size' listed in the search result pane? If not, please go to LF Client, run the search, and in the search result pane, right click on the column header, add the column Document -> Total Document Size. After that, perform the search again to see if there is any error. Thanks.

0 0
replied on January 3

Hello Juan,

Our Engineer tested the search syntax using the Windows Client with the "Total Document Size" column added and it works when searching the entire repository, but when they use the same setttings to search a sub-folder it throws the SQL Error like the WF does.  Doesn't matter which sub-folder is selected.

Thanks,

Jeff

0 0
SELECTED ANSWER
replied on January 5

Hi Jeff,

Now the "Total Document Size" column was included in search results. This column is known to cause performance issues and if not needed is recommended to not be included.

If the column is needed, SQL maintenance may help improve performance of this column search, but failing that, you can reach back out for an option to include in the database to increase the timeout.

Thanks

2 0
replied on January 6

Thanks Juan

0 0
replied on February 21 Show version history

Hey Juan,

We need to generate a large list of documents which includes the "Total Document Size" as a column. We keep running into the same timeout error. What is the recommended SQL option to increase the timeout limit?

Thank You,

Zach Merrill

0 0
replied on February 21

Zach, please have your solution provider go through Tech Support for that infomation.

1 0
replied on February 25

Thanks Miruna. We reached out to our solution provider, OPG-3, and have this addressed. 

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

Sign in to reply to this post.