(4) KVOOP.exe *32 processes pegging cpu kview OOP APP on Idol Indexer Server

[TheWienerman]

We have had issues with our Idol Indexer server (Also our EAS server)
pegging the cpu at 100%. When we check it out its always 4 instances
of KVOOP.exe each using 25% of cpu. I believe that this is a process
that is responsible for opening up attachments from messages that are
being indexed, but im not positive. Anyway, this has happened many
times and it brings the server's performance to its knees.

One of the CapEx experts we enjoy working with mentioned that there
was a recent patch available for Indexer that could simply be copied
over the existing exe. Does anyone have any knowledge about this or
are any of you experiencing the issue?

Also, I'd like to know what the immediate fix is when this situation
occurs... just kill the 4 processes?

JON

[Ultan Kendrick]

kvoop.exe or kvoop32.exe seems to kick off when indexing is scheduled to run. The process can be killed manually for an immediate fix. I haven't heard about a patch for it, you should be able to kill the process "scriptomatically"

 

--
You received this message because you are subscribed to the Google Groups "Autonomy/Zantaz EAS Archive Forum" group.
To post to this group, send email to zantaz-eas-a...@googlegroups.com.
To unsubscribe from this group, send email to zantaz-eas-archive...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/zantaz-eas-archive-forum?hl=en.

[TheZenMaster]

I have the same issue even after updating to the latest
Idolindexer.exe 6.3.1.2 as you described. Stopping the indexer and
restarting the machine is the only fix I have found.

On Aug 24, 7:55 am, Ultan Kendrick <ukendr...@gmail.com> wrote:
> kvoop.exe or kvoop32.exe seems to kick off when indexing is scheduled to
> run. The process can be killed manually for an immediate fix. I haven't
> heard about a patch for it, you should be able to kill the process
> "scriptomatically"
>

[john roh]

Hi Guys :-)

It's an easy fix-

To resolve this situation follow these steps; in the IDOLIndexer
installation folder locate formats.ini and edit the file:

[FilterSDK_Config]

; To enable in-process filtering set default_inprocess to 1
default_inprocess=0
; To enable in-process autodetection set default_detect_inprocess to 1
default_detect_inprocess=0

Change these two items to 1 to enable in-process filtering

Restart the IDOLIndexerservice.exe

That will stop the multiple Kvoops from spawning and handle things a
different way

John - jr...@bishopit.com)
---------------------------------------------------------------------------------------------------------------

> > >http://groups.google.com/group/zantaz-eas-archive-forum?hl=en.- Hide quoted text -
>
> - Show quoted text -

[TheZenMaster]

Thanks I made the change as you suggested. Where did you find this
information?

On Aug 24, 12:00 pm, john roh <j...@rohbots.com> wrote:
> Hi Guys :-)
>
> It's an easy fix-
>
> To resolve this situation follow these steps; in the IDOLIndexer
> installation folder locate formats.ini and edit the file:
>
> [FilterSDK_Config]
>
> ; To enable in-process filtering set default_inprocess to 1
> default_inprocess=0
> ; To enable in-process autodetection set default_detect_inprocess to 1
> default_detect_inprocess=0
>
> Change these two items to 1 to enable in-process filtering
>
> Restart the IDOLIndexerservice.exe
>
> That will stop the multiple Kvoops from spawning and handle things a
> different way
>

> John - j...@bishopit.com)

> > > >http://groups.google.com/group/zantaz-eas-archive-forum?hl=en.-Hide quoted text -

[john roh]

I've worked for Bishop Technologies (bishopit dot com) since 2004.
EAS via Educom TS / Zantaz / Autonomy, has been a key product I've
supported for a long time - :-)
I just happend to see the question and recalled the article in my
personal KB section.

J :-)
-------------------

On Aug 25, 8:25 am, TheZenMaster <joemcgowa...@gmail.com> wrote:
> Thanks I made the change as you suggested.  Where did you find this
> information?
>
> On Aug 24, 12:00 pm, john roh <j...@rohbots.com> wrote:
>
>
>
> > Hi Guys :-)
>
> > It's an easy fix-
>
> > To resolve this situation follow these steps; in the IDOLIndexer
> > installation folder locate formats.ini and edit the file:
>
> > [FilterSDK_Config]
>
> > ; To enable in-process filtering set default_inprocess to 1
> > default_inprocess=0
> > ; To enable in-process autodetection set default_detect_inprocess to 1
> > default_detect_inprocess=0
>
> > Change these two items to 1 to enable in-process filtering
>
> > Restart the IDOLIndexerservice.exe
>
> > That will stop the multiple Kvoops from spawning and handle things a
> > different way
>
> > John - j...@bishopit.com)

> > ---------------------------------------------------------------------------­------------------------------------

> > > > >http://groups.google.com/group/zantaz-eas-archive-forum?hl=en.-Hidequoted text -
>
> > > - Show quoted text -- Hide quoted text -