Soundbyte

I am trying to revive a previous thread "Desktop search does not think Outlook is installed" (http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=892743&SiteID=1).


Re: Windows Desktop Search Development Reviving: Desktop search does not think Outlook is installed

David Peng - MSFT

Have you try Outlook 2003 repair option Also, 3.0 is recommended for users with Office 2007. If you are running Office 2003, it's best to use WDS 2.6.5. There is an updated version to this as well which brings up the version to 2.6.6 that contains bug fixes.

Let me know,

David Peng (MSFT)





Re: Windows Desktop Search Development Reviving: Desktop search does not think Outlook is installed

Nick Evans

I have the same problem but I am already using the latest version of Windows Desktop Search 2.6.6. It works well for all other documents but will not recognise Outlook 2003 (as part of Office 2003) is installed Could this be linked to Exchange Server access problems as it is a corporate email account Any other suggestions or solutions





Re: Windows Desktop Search Development Reviving: Desktop search does not think Outlook is installed

Rob MacFadyen

I am also having this problem. Same thing...WDS was working fine - no problems - and then stopped indexing my Outlook files - about 2-3 weeks ago ( ).

I am on XP Pro x64 edition - MS Outlook 2003 (SP2) - and WDS 3.0 ( which I believe is required for x64).

I have noticed the following errors in my application event log:

Right after boot:

Event Type: Error
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3102
User: N/A
Description:
The per-user filter pool for session 0 could not be added.

Details:
The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist. (0x800704dd)

and then...

Event Type: Error
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3083
User: N/A
Description:
The protocol handler Search.OutlookExpressHandler.1 cannot be loaded. Error description: Class not registered

(Note: I do not use Oulook Express) ... and then...

Event Type: Warning
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3036
User: N/A
Description:
The content source <mapi://{s-1-5-21-1643212158-3222574970-3811797088-500}/> cannot be accessed.

Context: Windows Application, SystemIndex Catalog

Details:
Unspecified error
(0x80004005)

These errors tend to repeat (over and over and over) I assume everytime WDS tries to index

Please HELP! I love WDS and had to wait for 3.0 for my x64 machine during which time I had to use a "lesser" product that I really don't want to reurn to.





Re: Windows Desktop Search Development Reviving: Desktop search does not think Outlook is installed

justsml

I am having the same issue. (With Event log "Search.OutlookExpressHandler.1" messages, et al.)

I cannot even open the Windows Desktop (Standalone) Search app (from the Windows Desktop Search Start Menu shortcut). It just gives me the following Error Message Box:
===
Title:
search-ms: query=
Body:
search-ms: query=
Application not found
[Ok]
===




Re: Windows Desktop Search Development Reviving: Desktop search does not think Outlook is installed

David Peng - MSFT

Please try to reinstall your Office 2003 and/or Outlook Express. Some files used by WDS to detect Outlook installation may got corrupted/replaced by another version from another software install. If you are indexing corporate email using exchange, make sure that your email is cached locally.

Let me know,

David Peng (MSFT)





Re: Windows Desktop Search Development Reviving: Desktop search does not think Outlook is installed

Rob MacFadyen

Thanks for the suggestion, but re-installing office in the hope that it might fix the problem is not an option. I have the feeling that I'm just going to spend a lot of time and lose personal settings etc. just to still have a problem (if not a new one).

I don't think I'm alone in feeling that a desk top search (especially when the PC is for business) has become a "mission critical" tool. I simply can't not have one. I have returned to the Google search tool and will stay with it unless I have problems with it or I can be assured that WDS has "figured out" its problems.

Thanks for your time.