none
Windows Search / ESENT errors after every reboot

    Question

  • I recently noticed that after every restart, windows search is rebuilding the search index. Looking in the event viewer, it would appear that I have an issue with ESENT attempting to open a log file which does not exist.

    There are multiple entries in the event log, which are sequentially listed and as follows:

    (the first log entry source is from ESENT, all subsequent ones from Search)

    -----------------------------------------------------------

    Windows (3236) Windows: Error -1811 occurred while opening logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS001DF.log.

    -----------------------------------------------------------

    The Windows Search Service cannot open the Jet property store.

    Details:
     0x%08x (0xc0041800 - The content index database is corrupt. (HRESULT : 0xc0041800))
     -----------------------------------------------------------

    The search service has detected corrupted data files in the index {id=4700}. The service will attempt to automatically correct this problem by rebuilding the index.

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    ------------------------------------------------------------

    The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    ------------------------------------------------------------

    The Windows Search Service cannot load the property store information.

    Context: Windows Application, SystemIndex Catalog

    Details:
    The content index database is corrupt. (HRESULT : 0xc0041800) (0xc0041800)

    -------------------------------------------------------------

    The plug-in in <Search.JetPropStore> cannot be initialized.

    Context: Windows Application, SystemIndex Catalog

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    --------------------------------------------------------------

    The plug-in in <Search.TripoliIndexer> cannot be initialized.

    Context: Windows Application, SystemIndex Catalog

    Details:
    Element not found. (HRESULT : 0x80070490) (0x80070490)

    ---------------------------------------------------------------

    The gatherer object cannot be initialized.

    Context: Windows Application, SystemIndex Catalog

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    ----------------------------------------------------------------

    The application cannot be initialized.

    Context: Windows Application

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    ----------------------------------------------------------------

    The index cannot be initialized.

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    -----------------------------------------------------------------

     

    I really hope someone will be able to help me with this, I tried resetting the search service, forcing a rebuild of the search database and looking the other way, none  of which seemed to make a difference.

    Windows 7 Ultimate 64bit



    • Edited by thoh Tuesday, September 13, 2011 4:19 AM
    Tuesday, September 13, 2011 4:05 AM

Answers

  • I recently noticed that after every restart, windows search is rebuilding the search index. Looking in the event viewer, it would appear that I have an issue with ESENT attempting to open a log file which does not exist.

    There are multiple entries in the event log, which are sequentially listed and as follows:

    (the first log entry source is from ESENT, all subsequent ones from Search)

    -----------------------------------------------------------

    Windows (3236) Windows: Error -1811 occurred while opening logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS001DF.log.

    -----------------------------------------------------------

    The Windows Search Service cannot open the Jet property store.

    Details:
     0x%08x (0xc0041800 - The content index database is corrupt. (HRESULT : 0xc0041800))
     -----------------------------------------------------------

    The search service has detected corrupted data files in the index {id=4700}. The service will attempt to automatically correct this problem by rebuilding the index.

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    ------------------------------------------------------------

    The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    ------------------------------------------------------------

    The Windows Search Service cannot load the property store information.

    Context: Windows Application, SystemIndex Catalog

    Details:
    The content index database is corrupt. (HRESULT : 0xc0041800) (0xc0041800)

    -------------------------------------------------------------

    The plug-in in <Search.JetPropStore> cannot be initialized.

    Context: Windows Application, SystemIndex Catalog

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    --------------------------------------------------------------

    The plug-in in <Search.TripoliIndexer> cannot be initialized.

    Context: Windows Application, SystemIndex Catalog

    Details:
    Element not found. (HRESULT : 0x80070490) (0x80070490)

    ---------------------------------------------------------------

    The gatherer object cannot be initialized.

    Context: Windows Application, SystemIndex Catalog

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    ----------------------------------------------------------------

    The application cannot be initialized.

    Context: Windows Application

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    ----------------------------------------------------------------

    The index cannot be initialized.

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    -----------------------------------------------------------------

     

    I really hope someone will be able to help me with this, I tried resetting the search service, forcing a rebuild of the search database and looking the other way, none  of which seemed to make a difference.

    Windows 7 Ultimate 64bit




    ***UPDATE***

    I would like to inform persons viewing this post, that it seems I was able to find the cause of this issue.

    Being a long-time user of Piriform CCleaner, it appears one of the recent updates changed or added an item labled "MS Search" under 'Applications' > 'Windows'.

    Upon unchecking this option in the settings of CCleaner, I am no longer experiencing the symptoms posted above.

    Thank you to everyone for their help. 

     

     

    • Marked as answer by thoh Monday, October 10, 2011 2:35 AM
    Monday, October 10, 2011 2:35 AM

All replies

  • This problem is caused by a error in the Windows Search Indexing Service, a file is probably corrupt.

    Follow this instructions:
    1) Start > Run > cmd
    enter this: sfc /scannow

    2) Start > Run > regedit
    Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\SetupCompleted
    Check if it
    s been set to "0", if so then set it to "1" (DWORD)

     

    If the issue persists, try to perform an in-place upgrade to fix the issue:

    http://support.microsoft.com/kb/2255099

     

    Hope that helps.

     

    Regards,

    Leo   Huang

     

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, September 15, 2011 6:14 AM
    Moderator
  • Crap guide, after the restart the "1" is back!
    How do I permanently turn off indexing at all!? I do not need this s*it!
    • Proposed as answer by Justin Stock Thursday, September 05, 2013 2:38 PM
    Sunday, September 25, 2011 6:57 PM
  • I recently noticed that after every restart, windows search is rebuilding the search index. Looking in the event viewer, it would appear that I have an issue with ESENT attempting to open a log file which does not exist.

    There are multiple entries in the event log, which are sequentially listed and as follows:

    (the first log entry source is from ESENT, all subsequent ones from Search)

    -----------------------------------------------------------

    Windows (3236) Windows: Error -1811 occurred while opening logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS001DF.log.

    -----------------------------------------------------------

    The Windows Search Service cannot open the Jet property store.

    Details:
     0x%08x (0xc0041800 - The content index database is corrupt. (HRESULT : 0xc0041800))
     -----------------------------------------------------------

    The search service has detected corrupted data files in the index {id=4700}. The service will attempt to automatically correct this problem by rebuilding the index.

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    ------------------------------------------------------------

    The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    ------------------------------------------------------------

    The Windows Search Service cannot load the property store information.

    Context: Windows Application, SystemIndex Catalog

    Details:
    The content index database is corrupt. (HRESULT : 0xc0041800) (0xc0041800)

    -------------------------------------------------------------

    The plug-in in <Search.JetPropStore> cannot be initialized.

    Context: Windows Application, SystemIndex Catalog

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    --------------------------------------------------------------

    The plug-in in <Search.TripoliIndexer> cannot be initialized.

    Context: Windows Application, SystemIndex Catalog

    Details:
    Element not found. (HRESULT : 0x80070490) (0x80070490)

    ---------------------------------------------------------------

    The gatherer object cannot be initialized.

    Context: Windows Application, SystemIndex Catalog

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    ----------------------------------------------------------------

    The application cannot be initialized.

    Context: Windows Application

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    ----------------------------------------------------------------

    The index cannot be initialized.

    Details:
    The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

    -----------------------------------------------------------------

     

    I really hope someone will be able to help me with this, I tried resetting the search service, forcing a rebuild of the search database and looking the other way, none  of which seemed to make a difference.

    Windows 7 Ultimate 64bit




    ***UPDATE***

    I would like to inform persons viewing this post, that it seems I was able to find the cause of this issue.

    Being a long-time user of Piriform CCleaner, it appears one of the recent updates changed or added an item labled "MS Search" under 'Applications' > 'Windows'.

    Upon unchecking this option in the settings of CCleaner, I am no longer experiencing the symptoms posted above.

    Thank you to everyone for their help. 

     

     

    • Marked as answer by thoh Monday, October 10, 2011 2:35 AM
    Monday, October 10, 2011 2:35 AM
  • Thanks for that tip.  It is exactly what was happening to me too! Prob solved.

    But do we really need all that indexing going on?

    Cheers,

    • Proposed as answer by melen1717 Monday, July 07, 2014 10:08 PM
    Wednesday, October 19, 2011 9:05 PM
  • Thank you Thoh! Had exactly the same problem, and am also using Ccleaner for quite some time.

    Thanks for posting the solution.

    Sunday, November 06, 2011 5:23 PM
  • Thank you! Worked for me!

    RR IT Professional

    Friday, June 21, 2013 9:53 AM
  • thanks for the tip.  It appears to have solved the same problem on my computer.

    Cheers.

    Wednesday, September 25, 2013 5:11 AM
  • Saludos Leo y gracias por tu ayuda...

    Una pregunta, que ocurre o como podré hacerle si se presenta el error indicado, al realizar el scannow no presenta errores de integridad y al buscar la liga en RegEdit no existe?

    Gracias y espero puedas ayudarme.

    Saludos

    Raul Coss

    Wednesday, October 23, 2013 5:42 PM
  • Esta usando la programa CC Cleaner? ¿ Si su respuesta es 'si',  ha tratado de implementar lo que dicen arriba
    Saturday, April 12, 2014 8:26 AM
  • Hi...

    Just what the doctor ordered.... did as you suggested with Ccleaner and "abracadabra" the problem is solved. Who would of know but you.... thanks for the valuable tip........

    Monday, July 07, 2014 10:11 PM