Snap-in failed to initialize

Snap-in failed to initialize

• MaryJaneF

  I think I have found the reason for the initial problems uninstalling WDS 3.0, a program I and many others run called CCleaner which cleans junk files from your system. Unfortunately if you are not careful it will remove uninstallers as well! Below is a log of what CCleaner removed relating to WDS 3.0 - dont know if this may be helpful in resolving the above problems or not, but it certainly explains why WDS would not uninstall in the first place. (I have shortened the log as it is rather long)

  C:\WINDOWS\$NtUninstallKB917013$\kb917013.cat 27.63KB
  C:\WINDOWS\$NtUninstallKB917013$\reg00004 8.00KB
  C:\WINDOWS\$NtUninstallKB917013$\reg00005 8.00KB ......etc

  ( the above entries continue in numeric order until they reach  -  C:\WINDOWS\$NtUninstallKB917013$\reg00686 8.00KB)

  C:\WINDOWS\$NtUninstallKB917013$\spuninst\spuninst.exe 0.20MB
  C:\WINDOWS\$NtUninstallKB917013$\spuninst\spuninst.inf 46.29KB
  C:\WINDOWS\$NtUninstallKB917013$\spuninst\spuninst.txt 122 bytes
  C:\WINDOWS\$NtUninstallKB917013$\spuninst\updspapi.dll 0.35MB
  C:\WINDOWS\$NtUninstallKB917013$\spuninst\wss_SpCustom.dll 0.24MB
  ------------------------------------------------------------------------------------------

  I,m pretty sure that if you try running CCleaner with the "hotfix uninstallers" checkbox ticked then try uninstalling using the information from the "Outllook 2007 - WDS 3.0" thread mentioned above that you will be able to recreate the problems I have been experiencing. Unfortunately I'm not the only one having these problems, as CCleaner is a popular freeware program and the hotfix uninstallers check box is ticked by default (I think).
  

   

  
  

• Tryin2Bgood

  Thank you for your reply, unfortunately the indexing service does not appear to be the problem. The service is already running according to the "services" panel that you directed me to. However if I go to "services" under "computer management" and try to expand "services and applications" by clicking on the "+" sign in front of it then I get the "snap in failed..." message.

  There is however one service in the services panel which is not running that I believe should be - the "Windows Search Service" and if I try to start it using the play button on the toolbar then I get the following error -

  Could not start the Windows search service on local computer.

  Error: 1613 This installation package cannot be installed by the Windows Installer Service. You must install a windows service pack that contains a newer version of the Windows Installer Service.

  I find this message a bit confusing as I am running Windows XP Home with Service Pack 2, and the Windows Search Service was working perfectly before the install and uninstall of WDS 3.0.

  Any ideas why this might be happening I should probably also mention that I had some difficulty with uninstalling WDS as it did not appear in the add/remove area of my computer and the uninstall program $NTUninstallKB917013$\ spuninst\ spuninst.exe was also absent. I ended up using a method to uninstall which is outlined in another thread in this forum - "Outlook 2007 - WDS3.0" by Peter.Keyjob.

  Possibly this method of uninstalling has confused things somewhat but I was desperate and could find no other way of removing the software which was not working and generating constant errors in event viewer.

  Any idea as to how to proceed from here

  
  

• coolarian

  Interesting. Starting the service worked on two different machines for me. In addition, the Windows Search Service should not be running after uninstalling WDS 3.0. Are you able to stop that service If you can, do so and see if that helps.

  I'll try reinstalling 3.0 and uninstalling according to the instructions in the thread you referenced. I'll then see if I can reproduce the error.

  Paul Nystrom - MSFT

  
  
  

• Jonathan Upton

  Hello robmad,

  The beta version of 3.0 stops a service called Indexing Service. You can fix this problem by starting the service.

  To do this go to the control panel and select Performance and Maintenance. Then select Administrative Tools. From there start the Services application. Select Indexing Service and click the play button in the toolbar. Now that the indexing service is running you should no longer run into this error.

  The good news is that this problem will be fixed with the production release of WDS 3.0.

  Paul Nystrom - MSFT

  
  
  

• Corey Velan

  You mention that the Windows Search Service should not be running after uninstalling WDS 3.0 -

  here's a quote from the explanation given in my services panel...

  Services (local)

  Windows Search Service

  Description:

  Provides content indexing and property caching for file, email and other content (via extensibility APIs). The service responds to file and email notifications to index modified content. If the service is stopped or disabled, the explorer will not be able to display virtual folder views of items, and search in the explorer will fall back to item-by-item slow search.

  This explanation is what led me to believe the service should be running, but if that is not correct then that's one less problem! However it is the Search service which is generating most of my event viewer error messages - even though it's not running.

  Here is one such message...

  The registry does not match with the expected <4020000>, or the registry cannot be accessed because the service account does not have the correct permissions. Uninstall the previous version before installing the new one.

  And another...

  Performance monitoring cannot be initialized for the gatherer service, because the performance counters are not loaded or the shared memory object cannot be opened. This only affects the availability of the perfmon counters. Restart the computer.

  Obviously restarting the computer is no help.

  Thank you for all your help with this.

  
  
• Snap-in failed to initialize