Jump to content

Windows MS Search


amiek

Recommended Posts

First of all, I've been using CCleaner for many years now and never had a complaint about the program. Unfortunately now I do. Somewhere in the end of Sempteber there was an update of CCleaner and then the problem began. My log files were filled with critical errors about Windows Search. Every day the database was corrupt. I tried everything I knew, rebuilding the database, new indexing, removing IE from the list of indexing, but nothing worked. Every day my logfiles filled after startup with this:

(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 have Windows 7 Home premium, 64-bit.

 

Then it occured to me, that it only happed after using the cleanup from CCleaner, which I ususally do before shutting down my computer.

And after I looked into CCleaner/Applications/Windows I found MS Search. After I ticked it of, the errors in my log files disappeared. No more database corruption.

Could someone please look into this?

Thanks so much.

Link to comment
Share on other sites

Is search continuing to function after being cleaned with CCleaner? If it isn't; then it could be a problem with the Windows service(s) responsible for monitoring the filesystem.

 

Go to Start --> Run.

Type "cmd.exe" to open the command prompt.

Type "sfc.exe /scannow" into the command prompt and press Enter.

 

Then attempt to rebuild the database; purge it with CCleaner, reboot etc to see if the issues persist.

I'm Shane.

Link to comment
Share on other sites

Is search continuing to function after being cleaned with CCleaner? If it isn't; then it could be a problem with the Windows service(s) responsible for monitoring the filesystem.

 

Go to Start --> Run.

Type "cmd.exe" to open the command prompt.

Type "sfc.exe /scannow" into the command prompt and press Enter.

 

Then attempt to rebuild the database; purge it with CCleaner, reboot etc to see if the issues persist.

 

Search is still working and sfc /scannow does not solve everyting, in this case is does nothing.

 

This is caused by MS Search in Applications - Windows

 

I know that, I wrote that. The only thing is that I reported it, so someone can do something about it to fix it. ;)

Link to comment
Share on other sites

It seems better to me (but who am I) that they leave it unchecked and let the user decide if he/she wants to check it or not. Now, when I install it on other computers I have to remember to uncheck it everytime.

Link to comment
Share on other sites

  • 3 weeks later...

This is interesting.

I don't really use MS Search, however, as Locate32 is instant.

 

Locate32 builds a 1 time index of all your files, so any future searches are instant. Instead of searching your entire drive each time & wasting time.

Locate32 does find as you type as well.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.