The content source <iehistory: a bunch of #s] cannot be accessed.

Hi:

I get a bunch of these in Event Viewer as Warnings.  Not sure if I am having problems because of them or not.  Everything seems to work OK to me. 

Here is a list:

#1: 

The content source <csc://{S-1-5-21-2723294298-985905923-1236732326-1000}/> cannot be accessed.

Context: Windows Application, SystemIndex Catalog

Details:  (HRESULT : 0x80004005) (0x80004005)

#2:

The content source <iehistory://{S-1-5-21-2723294298-985905923-1236732326-1000}/> cannot be accessed.

Context: Windows Application, SystemIndex Catalog

Details:  (HRESULT : 0x80004005) (0x80004005)

#3:

The content source <mapi://{S-1-5-21-2723294298-985905923-1236732326-1000}/> cannot be accessed.

Context: Windows Application, SystemIndex Catalog

Details:  (HRESULT : 0x80004005) (0x80004005)

#4:

The content source <file:C:/Program Files (x86)/Microsoft Office/Office14/Visio Content/> cannot be accessed.

Context: Windows Application, SystemIndex Catalog

Details:  The object was not found. (HRESULT : 0x80041201) (0x80041201)

#5:

The content source <csc://{S-1-5-21-2723294298-985905923-1236732326-1000}/> cannot be accessed.

Context: Windows Application, SystemIndex Catalog

Details:  (HRESULT : 0x80004005) (0x80004005)

#6:

The content source <iehistory://{S-1-5-21-2723294298-985905923-1236732326-500}/> cannot be accessed.

Context: Windows Application, SystemIndex Catalog

Details:  (HRESULT : 0x80004005) (0x80004005)

 

Some of the above are repeated 3 to 4 times. I noticed that the 1000 changes to 500 in some of them.

 

When first booting up, these error messages appear.  Not sure if they are part of the problem or not.

#1

The gatherer is unable to read the registry URL.

Context: Application, SystemIndex Catalog

Details: (HRESULT : 0x0) (0x00000000)

#2

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

Details:

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

#3

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)

It is then rebuilt:

Windows (3524) Windows: The database engine has successfully completed recovery steps.

 

Any ideas of what to do?  Or is this just "normal" during bootup?

Thanks, Rick

 

Question Info


Last updated July 11, 2019 Views 19,532 Applies to:
Answer
Answer

 

Hi,

Are you facing any issue while working with programs?

Note:

The event logs that you have posted here refer to some errors with the Search Index in your computer. These are not fatal errors. However, they definitely point to the fact that some of the indexed locations in your computer are not accessible to the search mechanism due to different errors. These errors should go away once you have performed the following steps.

 

Method 1:

You may run the fixit from the following link and check for the issue:

Fix Windows Desktop Search when it crashes or not showing results

http://support.microsoft.com/mats/windows_search/

Method 2:

You may try rebuilding the index to see if it works:

Change advanced indexing options

http://windows.microsoft.com/en-US/windows7/Change-advanced-indexing-options

 

Let us know if it helps!

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.