TomK21

The SearchIndexer.exe process is utilizing near 100% of one of my CPUs. Opening the Indexing Options from the Control Panel strangely reveals that "Indexing is reduced due to user activity". I have left my computer in this state overnight only to find no progress the following morning. Little to no more items are indexed, status is still "Indexing speed is reduced..." and CPU usage of SearchIndexer.exe is still near 100%.

Searching this forum and other sources, many suggest unchecking certain file types or rebuilding the index or Restoring Defaults. I have done all to no avail.

Any assistance on this is most appreciative!

Regards,

TomK

(Windows Vista Enterprise)



Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

David Peng - MSFT

Do you have iTunes installed If you do, please disable .xml file indexing from the advanced options. Also, which anti-virus software do you have running on your machine





Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

TomK21

I have disabled .XML filter from the Advanced Options. No go. I even rebuilt the index. I had hope as it appeared to be indexing normally and the CPU usage was down. It then hit "763 items indexed" and stopped. Status is still "Indexing speed is reduced..." and SearchIndexer.exe is pegged again near 100%, but the # of items indexed remains the same.

I am running an Symantec Antivirus 10.2 Build 276.

Thank you again for your help.

TomK





Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

Eric Wolz - MSFT

What platform is this on XP or Vista




Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

TomK21

Vista (Enterprise)



Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

TomK21

I've made some good progress and think I almost have it!

I'm running MS Sysinternals Process Monitor ( http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx ) filtering on ProcessName = 'SearchProtocolHost.exe' and Operation 'ReadFile'

When the CPU gets pegged, the files that are consistently being addressed by the process are Outlook files. Specifically 'outlook.ost', 'archive.pst' and a Hotmail PST file.

Upon removal of these files, the Indexer no longer exhibits the problem! I've even let this run overnight with Outlook open (to prevent outlook.ost from reforming, i uncheck the "Use Cached Exchange Mode" option in the Account settings) ... and the problem never came back.

Upon recreaing the outlook.ost file, the problem reoccurs. I am unable to exclude the folder containing this file, as well, in the Indexer Options.

Any thoughts or assistance on this is most appreciated!

TomK





Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

TomK21

Now I'm very confused. I never noticed that, by default, .OST and .PST files are UNCHECKED in the Indexing Options ... but SearchProtocolHost.exe surely appears to be hung on these files

The only other thing I can think of doing is moving these files to a location that I can exclude from the Indexing Options

Your help is most appreciated.

Much obliged!

TomK





Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

DaveWood_MS

We index the contents of .Ost and .Pst files through Outlook, using the Mail API {MAPI}. So if you want to disable indexing of Outlook mail you can use the indexing control panel and uncheck the Microsoft Office Outlook location.

However I'm not sure whether your original high-cpu was expected. Does the Indexing Control Panel report the number of items increasing If you leave it does it complete indexing and then CPU drop back to zero





Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

TomK21

Number of items do not increase, despite indexer saying it is running, and searchindexer.exe running near 100% CPU. I have left my computer in this state overnight with no change.



Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

DaveWood_MS

Hmm, this doesn't sound like a known issue. You could try finding in TaskManager the process that is using 100% CPU {SearchIndexer.exe or Search ProtocolHost.exe} and right clicking and using the Create Dump File option. Then you could mail the resulting file to me at davewood@microsoft.com.

Is it having the Outlook OST that is causing this problem, or is the Hotmail integration needed too





Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

Wayne Drury

I too have been exhibiting this problem and found the Task Manager does not list the SearchIndexer.exe. I had to run Vista's Resource Monitor to find the cause on my constant 45->50% CPU hog.

SearchIndexer.exe (Microsofts Windows Search Indexer) has no been running at 45-50% CPU usage for nearly 3 days now and I cannot fathom how to abort, reset or find its cause.

I have tried:
- Rebooting the PC.
- Having no applications running.
- Leaving machine on for 2 days in the hope the indexing will complete.

All to no avail. Any further help much appreciated.

*Update 11:39am: SOLVED *
Have now killed off task and after a short while it restarted, but now its NOT stuck in 45-50% CPU usage. Therefore cured problem, but love to know what caused it

Wayne





Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

TomK21

Dave --

The DMP file is almost 200MB ... I've compressed it to 55MB, but my work account will still not allow me to send it. My Hotmail acct. fails to allow me to upload it. My Gmail account throws an error saying the ZIP file contains an executable and will not allow me to attach.

Public file sharing sites are giving me the same problem. Any suggestions

TomK

*Update*

Friend gave me access to his RapidShare acct. I've emailed you a link to where you can download the file. Let me know if there is anything further I can do.





Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

TomK21

Dave -- I want to thank you for your assistance. I realize that my problem may be a unique one which, appropriately, means resources should be placed on more common problems. I have one last question, then:

Upon analyzing my DMP file, you mentioned my NlsData0011.dll may be corrupted. Perhaps a simpler method than analyzing my DLL, would be if I could replace it from a working colleague's machine.

Unfortunately, some assistance on this is required. I have turned off Account Control and attempted to unregister this DLL (error came back leading me to believe that it is NOTa registered DLL to begin with). ... At any rate, I am unable to rename or replace this file.

Any assistance on this matter would be greatly appreciated.





Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

DaveWood_MS

Hi Tom,

We are looking at this issue internally. I can reproduce it myself by taking your version of NLSData0011.dll and copying it onto my machine. Then when I index a Japanese document I see the 100% CPU usage like you do.

For reference, NLSData0011.dll is the Word-breaker for Japanese text. So when you have a Japanese e-mail / document etc. the text that comes our of the document is passed to the relevant word-breaker to split it into words which are then put in the index and can be searched over.

I'm working with the Natural Language team at Microsoft who write the word-breaker dlls to try and understand how this issue can happen - it's very odd that system dlls get corrupted or aren't the same on all machines so I'm at a little bit of a loss here. Do you know of anything unusual that might have been installed or run on this machine that might be related to this

To fix this, don't try and call regsvr32 on the dll. You best bet is to run the sfc.exe tool {from an elevated command prompt}. Sfc.exe / will give you the options for the tool and:

sfc.exe /scanfile=C:\windows\system32\NLSData0011.dll

should repair the file I think. Let me know how you get on ...

Dave





Re: Windows Desktop Search Help searchindexer.exe utilizing near 100% CPU usage; suggestions from this forum tried to no avail

TomK21

thanks for your prompt reply!

Running the scan produced the result:

Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log.

I will email you this file if you think it will assist you.

Lastly, you asked if anything unusual had happened. A couple of weeks ago, my harddrive was exhibiting signs that it had "bad sectors" on it (this description coming from our hardware support staff). Accessing, copying, moving, or deleting certain files would cause the harddrive light to remain on while no (or little) physical activity was occurring on the drive itself. (We did not investigate the files themselves, as merely the sound my drive was making was indicative enough to our support center that it was the drive itself.) A scan/repair tool was run on my harddrive, which confirmed the problem and seemed to fix the issue entirely. I however, was asked that for good measure it would be worth getting a new drive altogether as, apparently, my old drive would have a greater chance of being susceptible to such a condition in the future.

I crated an imaging using the Backup and Restore center in Vista. Then used the "Repair" option found in Vista's installation disc to restore this image to a new drive.

It was around this time that the problem described from this thread began. While I was not so naive to think the problems could be related, my initial research into forums like these showed similar issues w/ resolutions ... considering the alternative would be to rebuild my machine with no guaranteed results, versus this further investigation which was proving promising ... i became quite bias to what we were finding here.

I apologize for not mentioning this earlier ... I think once i narrowed it down to a file or two causing the problem, i blocked the HDD failure as a cause, as I believed the situation would have been a lot more grave if the incident caused corrupted files.

soooo... not sure where this leaves us, or, more importantly, my best course of action at this point.

If there's a legitimate case of the HDD incident creating corrupted files, do i have an alternative to a rebuild Is there a means by which I can scan system files/others to look for corruption Is there a chance the corrupt DLL is an isolated case

I appreciate your patience. Looking forward to your suggestion.