Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1255
  • Last Modified:

Indexing Service MMC Snap-In fails to initialize

Hello All:

I am running Windows XP SP2 with auto-update enabled.

The system has a large amount of disk space (> 1 Tbyte) in one Raid 5 array (880 Mbyte), one Raid 0 array (150 Mbyte) and two independent disks (200 and 250 Mbytes respectively).  I use it to manage my photographic image collection which consists of over 200 Mbytes of primary images and several hundred Mbytes of secondary (modified) images that are deleted periodically.  The primary image store grows by 1-10 Mbytes/month.

I am running Diskeeper 10 Professional Premier.  

I have the indexing service enabled and noticed that it was chewing up many of my CPU cycles (if I pause it the average CPU utilization drops by 20-30%).

I wanted to modify the drives/directories that the indexing service accesses, so I went to  Administrative Tools --> Computer Management ---> Services and Applications.

I received the following message:

Snap-in failed to initialize.  Name: Indexing Service  CLSID: {.......}

I opened an instance of MMC and went to File--> Add/remove snap-in --> Add

I got a list of stand-alone snap-ins which included the Indexing Service (which was displayed as a generic folder icon w/o any information in the 'Vendor' column - most of the other snap-ins were displayed as unique icons with 'Microsoft Corp' as vendor).

When I clicked on the Indexing Service, I got the 'Snap-in failed to initialize.....' message as above, with the same CLSID.

I think I need to reinstall the Indexing Service snap-in.

Am I correct and, if so, how do I do that?

Is there something else going on, perhaps related to Diskeeper?

Thanks in advance,

wb

0
warrenbuckles
Asked:
warrenbuckles
  • 8
  • 3
1 Solution
 
johnb6767Commented:
cisvc.exe is the executable that runs in memory for the indexing service. You might have a corrupt file, which could be corrected with a System File Check

Start>Run>
SFC /purgecache (this is optional, as it only clears out cached protected files)
SFC /scannow (this is the command that ititiates a system fiole scan and looks for corrupted files.

0
 
johnb6767Commented:
Alternatively it could be the snapin itself...
C:\WINDOWS\SYSTEM32\CIADV.MSC

Might even want to try and expand just a single file under Start>Run >Msconfig>Expand File

0
 
johnb6767Commented:
How are other Snap ins working?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
johnb6767Commented:
Are you also seeing any errors in the event logs?
0
 
johnb6767Commented:
And have you recently uininstalled Office 2007 Beta by any chance?
0
 
warrenbucklesAuthor Commented:
Johnb6767:

Your Q's, in order:

SFC /scannow demands the XP SP2 install disk to copy .DLL files.  I put it in the CD and it rejects it as the incorrect disk.  Legal MS sourced disk, not a copy.  As a result I cannot complete SFC scan.  I rebooted and tried again, same result.

CIADV.MSC is present.  

I expanded and replaced it.  --> same result

Other snap-ins are working (disk mangler, for instance)

No event log errors that I can relate to this - some (5) paging errors from 5 AM on my Raid5 but the array is still available and passes an integrity check.  I had a BSOD error yesterday, 0x....7A, Kernel_data_inpage_error long before (12 hrs) the paging errors.  Submitted to MS - return report related it to a device driver, possibly the HighPoint 2310 controller that supports the Raid5 array.  BSODs are VERY rare on this system - 2-3 in nine months on a machine that runs 24/7, all device driver related - pool data or paging errors, as above.

Orifice 2007 Beta ---> it's installed, yes.  It has not been uninstalled but I recently installed the Beta 2 version (en_office_2007_beta2_techrefresh.exe) on top of existing version.  It is functioning properly (well, as properly as a Beta can...it's not crashing as it was months ago).

I have not tracked down the CSID cited in the error message (yet).  

wb

0
 
johnb6767Commented:
I have seen some searches, regarding a Windows Search installed with the Beta. Is that listed under Add/Remove Programs? If so, might try uninstall it.....
0
 
warrenbucklesAuthor Commented:
johnb6767:

Yes, I remember it nattering at me about a search feature I was supposed to install.  I think it quit after the Beta 2.  

Looking at my install of Office07Beta2, I removed the 'Research Explorer Bar'
No change in error message on trying to access Indexing Service mmc

I also have IE7 installed.  It offered some magic search 'feature,' too.  I have not installed or activated that.

Do you have any way of getting around the .DLL problem in SFC (see above)?

wb
0
 
johnb6767Commented:
If it isnt the right disk, I dont think anything will help....
0
 
johnb6767Commented:
This is what I was referring to (to make sure I gave you the right info about teh search functions in 2007..).

Think it might be something different from the Research Bar......

Snap-In Failed to Initialize - Indexing Service
http://dotnettemplar.net/SnapInFailedToInitializeIndexingService.aspx

After scratching around a bit I found that uninstalling Windows Search (that Outlook 2007 insists on having) would fix it.  I did, and Indexing Services got better
0
 
warrenbucklesAuthor Commented:
johnb6767:

Glory be, that fixed it.  Thanks.

I turned Indexing Service back on and it no longer hogs my CPU, either.

The curse of the Beta.


wb
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 8
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now