WDS3 indexing problem

WDS3 indexing problem

• Mohankrish

  Just wanted to add to the thread that I'm having the same problem with WDS3 that I installed when Outlook 2007 told me to. I've uninstalled & reinstalled, but same errors.
  
  The above link doesn't appear to even relate to WDS3   Sorry if I missed it.
  
  Matt
  
  

• nandinho

  Hello and I hope Im not barging in...

  I read this post because Im getting the same error in addition to some that I think are related to Small Business Server. I get an awful lot of time-outs it seems -- the computer pauses for no particular reason, no activity on the hard drive and no activity to speak of with the CPU and yet when I attempt to start an application, the system just doesn't respond. The catch If I soft-reset with ctrl-alt-del the system begins responding most of the time -- on the rarer occassions that it doesn't I can quickly press and release the reset button and it will re-awaken the system. If you have any information on this part of my problem I would appreciate it.

  As for uninstalling WDS I received an interesting notification from the uninstall app. The Uninstall warns that 40 program installations were discovered that may not operate properly if I continue with the uninstall. These apps ranged from MSOFFICE 2007 and SQL Server to SWF Image Creator, Web Weaver 2005, and many many more. The sheer volume and scope of programs seemingly affected was a little disconcerting, but I did it anyway -- I uninstalled WDS ...

  Im preparing to reboot from that right now :D

  Wish me luck

  Thanks

  Rob Walker

  
  
  

• ralex

  seems it doesn't work.

  I had WindowsDesktopSearch-kb911993-V2-x86-ENU.exe version before.

  Ok, I'd unistalled WDS3 completely, restarted computer, but file Windows Desktop Search\MSNLNamespaceMgr.dll was used anyway so I rename it and restart again (restartig explorer.exe without restarting of computer didn't help).
  I'd removed Indexing Service from Add/Remove Windows Component because I suspected that it breaks Snap-In. Removed successfully.
  
  Restarted again.
  
  I've installed WDS3 again. When I open Computer Manager I receive the same error - Can't initialize Indexing Service Snap-In.

  there are searchindexer.exe, searchprotocolhost.exe, searchfilterhost.exe in process list, but Outlook still doesn't return any results.

  Further recommendations

  
  

• Marc H. Young

  Same problem, I try the kb atricle, but nothing works.
  
  

• jens_essen

  Hello all,

  I've been unable to reproduce this problem, but after searching for a bit I found the following post:

  http://www.microsoft.com/communities/newsgroups/en-us/default.aspx query=%23msntb_toolbar_full_name%23&dg=&cat=en_US_d02fc761-3f6b-402c-82f6-ba1a8875c1a7&lang=en&cr=&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us

  As an FYI, this is not a Microsoft solution, but it does seem to be working quite successfully for several other people. Please use at your own risk.

  I hope this helps.

  Paul Nystrom - MSFT

  
  
  

• Ogedei

  Hello BeerBong,

  We've noted some problems with upgrading older versions of WDS (versions older than 2.6.5) to the 3.0 beta. I would suggest completely uninstalling the 3.0 beta and the 2.6.x versions of WDS. Once both of those have been removed you can try installing the 3.0 beta.

  Please let me know if this works for you.

  Paul Nystrom - MSFT

  
  
  

• Yatharth Gupta

  Hi BeerBong,

  Well it looks like this isn't one of the typical problems we run into during the 3.0 beta install. After doing some more research on the errors that were thrown I came accross the folling Microsoft KB article:

  http://support.microsoft.com/kb/910341/en-us

  This explains what causes the 0x800704dd error and even provides workarounds for the fix (for 2000 and XP). I would suggest starting here to see if that helps address your problem. The cause and solution discussed in the article seem consistent with the "The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist. " message you are seeing in your error logs.

  Please keep me posted on the results.

  Paul Nystrom - MSFT

  
  
  

• Gary Harrison

  Hello Matt,

  My apologies for the link above. I posted the search criteria instead of the actual thread.

  In final, this is a bug in Office 2007 beta 2. It has been fixed by our development team, but the fix will not be available until the next Office 2007 release. Unfortunately, there currently is no known workaround. If you need to use the indexing snap-in for some reason, it can be re-enabled by uninstalling WDS 3.0.

  If you would like to continue to use WDS please uninstall 3.0 beta and install 2.6.5. This will allow you to continue to search your desktop. When you start Outlook, however, you will receive a message asking you if you would like to enable instant search. Please select the no option or 3.0 will be reinstalled.

  Paul Nystrom - MSFT

  
  
  
• WDS3 indexing problem