Data Loss Prevention

  • Private Community
 View Only

  • 1.  IDM index fails with protect error 1001

    Posted Dec 12, 2011 04:24 AM

    Hi

    I'm trying to index a share and after a long wait without the server saying anything i recieve this error:

     

     

    General

    Type

    Severe

    		  

    Time

    Dec 12, 2011 9:11:01 AM

    Server

    Enforce Server

    		  

    Host

    127.0.0.1

     

    Message

    Code

    3000

    Summary

    Protect Error 1001: Unexpected indexing error occurred.

    Detail

    Protect Error 1001: Unexpected indexing error occurred. Document profile wasn't created.

     

    The user is Administrator with full rights. The index stops at 500 files and the logfiles from tomcat says nothing about what may cause the error. It just writes that the share is successfully mounted and unmounted.

    Does anyone know what error 1001 means? I have gone through support and all forums, kbs and other resources without any answer.



  • 2.  RE: IDM index fails with protect error 1001

    Trusted Advisor
    Posted Dec 13, 2011 02:26 AM

    hello,

     

     Unfortunately i never found the "true" reason of this but usually to solve it i restart all enforce services (or at least vontu manager)

     

    I suppose (at least for us) it was due to a weekly database stop without stopping enforce services and it seems some service or connexion to DB wasnt reinitialized correctly.

     

    Hope it will help you.



  • 3.  RE: IDM index fails with protect error 1001

    Posted Dec 13, 2011 04:23 AM

    Since i cannot/are not allowed to look in the directory getting indexed i asked the customer to give the size i  realized quite fast that the error occured because of this. Strange because it normally lets you know if its to big but not in this case. So this solves the question but not the issue. Thanks for the help anyway Stephane!



  • 4.  RE: IDM index fails with protect error 1001

    Posted Dec 20, 2011 04:44 AM

    Ask you customer to put all files in one zip archive and try to upload it by enforce this can help you.



  • 5.  RE: IDM index fails with protect error 1001

    Posted Jan 03, 2012 04:08 AM

    Unfortunately the share is too big. Still i have gone past this problem after tweaking indexing.properties as told by the support and now it indexes the documents. Then a new problem surfaced. None of the detection servers can handle the "big" size now. Support is silent...

    I cant be the only one with this problem?



  • 6.  RE: IDM index fails with protect error 1001

    Posted Jan 26, 2012 04:36 PM

    lind311, you are not alone, i just contacted support about the exact same thing.  i sent the logs and waiting.  again, it is a really big directory.  it usually dies at 13,000 files, which is weird cause i have another indexing job that works that is ~15,000.  stopping and starting the services doesn't help.  did you ever get anywhere with this?  with support?



  • 7.  RE: IDM index fails with protect error 1001

    Posted Jan 31, 2012 05:11 AM

    Unfortunately our customer got sick of wasting time on a problem that didnt really have any solution to it so had to quit the case i had opened. Still i asked the support to keep looking for the problem cause i bet more will get or even have the problem. The senior support technician told me he would but havnn't heard anythin since. Hopefully they realise what problems this causes and finds a solution for it. Maybe in version 12 if we're lucky!

    Since the issue wasn't resolved i reverted all the changes and split the index in several smaller ones. BIG hassle i might add. From my minimal share at 3,7GB (after filtering) i now have 7 indexes. And thats just a small one...



  • 8.  RE: IDM index fails with protect error 1001
    Best Answer

    Posted Feb 08, 2012 02:21 AM

    There's a known issue with IDM index in version 11.1.x.x

     

    Problem Summary
     
      Unable to index IDM in V11.  Error in tomcat log: 

     

    26 Sep 2011 23:03:05,920- Thread: 14 SEVERE [com.vontu.profiles.manager.InfoSourceIndexCreator] Error during document indexing

    Cause:
    com.vontu.cracker.ContentExtractorException: TimeoutExceptionoccurredd, Exception thrown from : FilterTextExtractor.cpp(63)
    com.vontu.cracker.ContentExtractorException: TimeoutExceptionoccurredd, Exception thrown from : FilterTextExtractor.cpp(63)
     at com.vontu.cracker.jni.NativeTextExtractor.filterText(NativeTextExtractor.java:28)
     at com.vontu.cracker.NativeTextExtractorAdapter.filterText(NativeTextExtractorAdapter.java:18)
     at com.vontu.cracker.TextExtractionDelegate.getTextForFile(TextExtractionDelegate.java:39)
     at com.vontu.profiles.manager.document.CrackingProcessor.crackDocument(CrackingProcessor.java:30)
     at com.vontu.profiles.manager.document.DocumentSourceIndexCreator.putDocumentInIndexer(DocumentSourceIndexCreator.java:333)
     at com.vontu.profiles.manager.document.DocumentSourceIndexCreator.doIndex(DocumentSourceIndexCreator.java:227)
     at com.vontu.profiles.manager.document.DocumentSourceIndexCreator.indexInfoSourceOnManager(DocumentSourceIndexCreator.java:123)
     at com.vontu.profiles.manager.InfoSourceIndexCreator.indexListOfDataSources(InfoSourceIndexCreator.java:138)
     at com.vontu.profiles.manager.document.DocumentSourceIndexJob.index(DocumentSourceIndexJob.java:9)
     at com.vontu.profiles.manager.InfoSourceIndexJob.execute(InfoSourceIndexJob.java:46)
     at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
     at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:543)
    26 Sep 2011 23:03:05,954- Thread: 14 SEVERE [com.vontu.profiles.manager.InfoSourceIndexCreator] Protect Error 1001: Unexpected indexing error occurred.

     

    Solution
     
      There is an issue when the Content Extractor fails.  The IDM indexer is not catching the failure correctly, and the index fails as a result.  This is an issue in V11 and has been fixed in V11.5

     

    Check the tomcat's logs, if you get the same error then you need to upgrade to 11.5 which is already available to download on Symantec Fileconnect.