Search-Service Error Messages

Please forgive this long post, but I need help with my Windows 7 program
encountering the following succession of problematic Event Log entries
related to the Search Service each time I boot up (they appear right
after the ESENT message that: ”Windows (4844) Windows: The database
engine (6.01.7601.0000) started a new instance (0).”

Source: ESENT Event ID 455 - Windows (4844) Windows: Error -1811
occurred while opening logfile
C:\ProgramData\Microsoft\Search\Data\Applications\ Windows\MSS00780.log.

Source: Search Event ID: 9000 - the Windows Search Service cannot open
the Jet property store. Details: 0x%08x (0xc0041800 - The content index
database is corrupt. (HRESULT : 0xc0041800)

Source: Search Event ID: 7040 -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)

Source: Search Event ID: 7042 -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)

Source: Search Event ID: 9002 -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)

Source: Search Event ID: 3029 -The plug-in in Search.JetPropStore
cannot be initialized. Context: Windows Application, SystemIndex
Catalog. Details: The content index catalog is corrupt. (HRESULT :
0xc0041801) (0xc0041801)

Source: Search Event ID: 3029 -The plug-in in Search.TripoliIndexer
cannot be initialized. Context: Windows Application, SystemIndex
Catalog. Details: Element not found. (HRESULT : 0x80070490) (0x80070490)

Source: Search Event ID: 3028 -The gatherer object cannot be
initialized. Context: Windows Application, SystemIndex Catalog.
Details: The content index catalog is corrupt. (HRESULT : 0xc0041801)
(0xc0041801)

Source: Search Event ID: 3058 -The application cannot be initialized.
Context: Windows Application. Details: The content index catalog is
corrupt. (HRESULT : 0xc0041801) (0xc0041801)

Source: Search Event ID: 7010 -The index cannot be initialized.
Details: The content index catalog is corrupt. (HRESULT : 0xc0041801)
(0xc0041801)

Source: Search Event ID: 1013 -Windows Search Service stopped normally.

Source: Search Event ID: 1088 -The Windows Search Service is starting
up and attempting to remove the old search index {Reason: Index
Corruption}.

The above Event log error messages are then followed by three messages
that “The Windows Search Service has successfully removed the old search
index”, “The Windows Search service is creating the new search index
{Reason: Index Corruption}“ and the ESENT message that “Windows (5864)
Windows: The database engine (6.01.7601.0000) started a new instance
(0)”. These are followed by a couple more Search “warning” messages
that “The content source file:C:/Program Files (x86)/Microsoft
Office/Office14/Visio Content/ cannot be accessed”.

All of the above happens each time I reboot, as if something during the
boot process is trying to access the Windows Search feature or something.

Any ideas?

On Thu, 09 Aug 2012 07:30:50 -0500, TMitchell wrote:

Please forgive this long post, but I need help with my Windows 7 program
encountering the following succession of problematic Event Log entries

I can't help with your problem, but let me encourage you.

It's always a good idea to provide too much rather than too little
information. Many people don't provide enough info for even the
knowledgeable denizens to help, and some of them even resist requests
for more info.

So thanks for your long post...

--
Gene E. Bloch (Stumbling Bloch)

TMitchell wrote:
Please forgive this long post, but I need help with my Windows 7 program
encountering the following succession of problematic Event Log entries
related to the Search Service each time I boot up (they appear right
after the ESENT message that: ”Windows (4844) Windows: The database
engine (6.01.7601.0000) started a new instance (0).”

Source: ESENT Event ID 455 - Windows (4844) Windows: Error -1811
occurred while opening logfile
C:\ProgramData\Microsoft\Search\Data\Applications\ Windows\MSS00780.log.

Source: Search Event ID: 9000 - the Windows Search Service cannot open
the Jet property store. Details: 0x%08x (0xc0041800 - The content
index database is corrupt. (HRESULT : 0xc0041800)

Source: Search Event ID: 7040 -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)

Source: Search Event ID: 7042 -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)

Source: Search Event ID: 9002 -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)

Source: Search Event ID: 3029 -The plug-in in Search.JetPropStore
cannot be initialized. Context: Windows Application, SystemIndex
Catalog. Details: The content index catalog is corrupt. (HRESULT
: 0xc0041801) (0xc0041801)

Source: Search Event ID: 3029 -The plug-in in Search.TripoliIndexer
cannot be initialized. Context: Windows Application, SystemIndex
Catalog. Details: Element not found. (HRESULT : 0x80070490) (0x80070490)

Source: Search Event ID: 3028 -The gatherer object cannot be
initialized. Context: Windows Application, SystemIndex Catalog. Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

Source: Search Event ID: 3058 -The application cannot be initialized.
Context: Windows Application. Details: The content index catalog is
corrupt. (HRESULT : 0xc0041801) (0xc0041801)

Source: Search Event ID: 7010 -The index cannot be initialized.
Details: The content index catalog is corrupt. (HRESULT : 0xc0041801)
(0xc0041801)

Source: Search Event ID: 1013 -Windows Search Service stopped normally.

Source: Search Event ID: 1088 -The Windows Search Service is starting
up and attempting to remove the old search index {Reason: Index
Corruption}.

The above Event log error messages are then followed by three messages
that “The Windows Search Service has successfully removed the old search
index”, “The Windows Search service is creating the new search index
{Reason: Index Corruption}“ and the ESENT message that “Windows (5864)
Windows: The database engine (6.01.7601.0000) started a new instance
(0)”. These are followed by a couple more Search “warning” messages
that “The content source file:C:/Program Files (x86)/Microsoft
Office/Office14/Visio Content/ cannot be accessed”.

All of the above happens each time I reboot, as if something during the
boot process is trying to access the Windows Search feature or something.

Any ideas?

A poster here, found a setting in Piriform CCLeaner was the culprit.

http://social.technet.microsoft.com/...-d512ff642db5/

Paul

Paul wrote:
TMitchell wrote:
Please forgive this long post, but I need help with my Windows 7
program encountering the following succession of problematic Event Log
entries related to the Search Service each time I boot up (they appear
right after the ESENT message that: ”Windows (4844) Windows: The
database engine (6.01.7601.0000) started a new instance (0).”

Source: ESENT Event ID 455 - Windows (4844) Windows: Error -1811
occurred while opening logfile
C:\ProgramData\Microsoft\Search\Data\Applications\ Windows\MSS00780.log.

Source: Search Event ID: 9000 - the Windows Search Service cannot
open the Jet property store. Details: 0x%08x (0xc0041800 - The
content index database is corrupt. (HRESULT : 0xc0041800)

Source: Search Event ID: 7040 -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)

Source: Search Event ID: 7042 -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)

Source: Search Event ID: 9002 -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)

Source: Search Event ID: 3029 -The plug-in in Search.JetPropStore
cannot be initialized. Context: Windows Application, SystemIndex
Catalog. Details: The content index catalog is corrupt.
(HRESULT : 0xc0041801) (0xc0041801)

Source: Search Event ID: 3029 -The plug-in in
Search.TripoliIndexer cannot be initialized. Context: Windows
Application, SystemIndex Catalog. Details: Element not found.
(HRESULT : 0x80070490) (0x80070490)

Source: Search Event ID: 3028 -The gatherer object cannot be
initialized. Context: Windows Application, SystemIndex Catalog.
Details: The content index catalog is corrupt. (HRESULT : 0xc0041801)
(0xc0041801)

Source: Search Event ID: 3058 -The application cannot be
initialized. Context: Windows Application. Details: The content index
catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

Source: Search Event ID: 7010 -The index cannot be initialized.
Details: The content index catalog is corrupt. (HRESULT : 0xc0041801)
(0xc0041801)

Source: Search Event ID: 1013 -Windows Search Service stopped normally.

Source: Search Event ID: 1088 -The Windows Search Service is
starting up and attempting to remove the old search index {Reason:
Index Corruption}.

The above Event log error messages are then followed by three messages
that “The Windows Search Service has successfully removed the old
search index”, “The Windows Search service is creating the new search
index {Reason: Index Corruption}“ and the ESENT message that “Windows
(5864) Windows: The database engine (6.01.7601.0000) started a new
instance (0)”. These are followed by a couple more Search “warning”
messages that “The content source file:C:/Program Files
(x86)/Microsoft Office/Office14/Visio Content/ cannot be accessed”.

All of the above happens each time I reboot, as if something during
the boot process is trying to access the Windows Search feature or
something.

Any ideas?

A poster here, found a setting in Piriform CCLeaner was the culprit.

http://social.technet.microsoft.com/...-d512ff642db5/


Paul


Thank you. That hint solved the problem.