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

Question

Question

Quick field agent taking over CPU without any progress?

asked on August 7, 2014

Hi

 

I have a session that searches the repository and find documents that have now pages and are not OCRed.     When I run the session on its own manually via Quick Field Session everything works fine but if I run it through Quick Field Agent on it does not work as it should. 

 It produces 4 winword.exe session in task manager and CPU runs at 93 to 99 pre cent.  I think one winword.exe is running for each core  (we have 4 core on this server).   Each uses almost 25 per cent of the CPU and they never end and eventually I have to end them manually.  Even terminating session via QF agent does not stop them. 

If there are a lot of files to be processed I can see temp file piling up by roughly 10 gb.

 

I have even limited the total documents to 10000 and total queue to 5000 and it will run every 5 hours. 

 

I just can't get my head around this.  Is this a glitch with QF agent or I am missing something?    

 

Any help is appreciated...

0 0

Answer

SELECTED ANSWER
replied on August 7, 2014

The only thing in Quick Fields that could launch WinWord.exe is the Text Extraction process. But if you have image pages, I can't think of any reason why you would extract the electronic document from Laserfiche or run text extraction on it...

 

If you are running text extraction, it sounds like the Office IFilter is running into some issue with some of your documents. Under normal circumstances, all WinWord executables should shut down when they're done extracting text. Unfortunately, we have no control over that process. You could try narrowing down the documents where the issue occurs.

0 0

Replies

replied on August 7, 2014

Miruna,

 

I took away text extraction and it seems winword.exe hang up is gone away.  I will keep it off for next few days to see how this is progressing.  

 

Thanks

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

Sign in to reply to this post.