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

Question

Question

search repository

asked on March 12, 2015

Hi,

Is there a limit on the number of entries returned from Search Repository?

The Search Query below returns 9,133 rows

{[Grants]:[Document Type] <> ""} & {[Grants]:[Grants - Doc Date]<>""} & {[Grants]:[Grants - Proposal #] <> ""} & {[Grants]:[Grants - Sponsor Name]=""}

When I looked in Workflow Administration, I see the error "The Writer is closed or in error state" -- what does it mean?

When I modified the Search Query to look for a particular Proposal ID, the workflow works.

Thanks,

Teng

0 0

Answer

SELECTED ANSWER
replied on July 23, 2015

I have resolved the error The Writer is closed or in error state.

I have workflows that target specific time period.  I had no problem running the workflow that process documents that were created/modified in the last 365 days.  I got The Writer is closed or in error state error when I tried to process documents that were created/modified in 2014.  So I concentrate on document created/modified between 2014/01/01 and 2014/07/21.  Eventually I found that there is a document created/modified on May 23, 2014 that I can’t copy it, can't rename it, but I can open it and also delete it.  When I tried to copy it, I got the error Move/Copy Error  Could not copy document.  Could not connect to the Laserfiche Server. [797].  To solve the error The Writer is closed or in error state, we removed the document and re-imported  it.  The workflow ran successfully after that.

 

0 0

Replies

replied on March 12, 2015

What version of Workflow are you using?

0 0
replied on March 12, 2015 Show version history

Version 9.0.2.236

 

In Search Repository, I have the error "The Writer is closed or in error state" when I specified one of the following in the Results To Return:

 

First 2000

First 3000

First 4000

First 5000

All results

 

When I specified First 1000, my workflow completed successfully.

 

Is there something that controls how many rows can be returned by Search Repository?

0 0
replied on March 13, 2015

In Search Repository, I have the error "The Writer is closed or in error state" when I specified one of the following in the Results To Return:

 

First 2000

First 3000

First 4000

First 5000

All results

 

When I specified First 1000, my workflow completed successfully.

 

Is there something that controls how many rows can be returned by Search Repository?

replied on March 13, 2015

In Search Repository, I have the error "The Writer is closed or in error state" when I specified one of the following in the Results To Return:

 

First 2000

First 3000

First 4000

First 5000

All results

 

When I specified First 1000, my workflow completed successfully.

 

Is there something that controls how many rows can be returned by Search Repository?

replied on March 13, 2015

There is no limit and we've tested it with hundreds of thousands of results. The results are written to an XML file on disk on the Workflow Server, so it sounds like there is something going wrong with that part. If you're not running out of space on the hard drive, it's probably best that you have your reseller open a case with Tech Support so we can take a closer look.

0 0
replied on July 23, 2015

I have resolved the error The Writer is closed or in error state.

I have workflows that target specific time period.  I had no problem running the workflow that process documents that were created/modified in the last 365 days.  I got The Writer is closed or in error state error when I tried to process documents that were created/modified in 2014.  So I concentrate on document created/modified between 2014/01/01 and 2014/07/21.  Eventually I found that there is a document created/modified on May 23, 2014 that I can’t copy it, can't rename it, but I can open it and also delete it.  When I tried to copy it, I got the error Move/Copy Error  Could not copy document.  Could not connect to the Laserfiche Server. [797].  To solve the error The Writer is closed or in error state, we removed the document and re-imported  it.  The workflow ran successfully after that.

 

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

Sign in to reply to this post.