I installed Windows Desktop Search and cannot find adequate help documentation on a number of features. I have a Server 2003 Enterprise SP1 OS.
Complaints:
(1) Desktop Search replaced my Windows Search which I was familiar with. But it's much more complex to operate.
(2) It's nice that it searches email, but the fact that it does so by default is a pain in the neck
(3) The setup of desktop search is single-setup for all profiles. I have 4 people using this computer, and they should have different search setups, but WDS only allows a single one as far as I can tell. The single index for all profiles is stored in the "all users" profile. Let me know if you think this is not the case.
(4) There is no documentation on ifilters that I can find. Windows Search Service was causing a bunch of application errors, so I disabled it for a while. Then my search did not work, and since WDS replaced my Windows search I could not search at all. Then I found an article in this forum that said if I disabled the .pdf ifilter they would go away. It seems to have worked. But I would like to know what an ifilter is, how to get new ones, how to uninstall and install an ifilter, and other things like that. For example one person suggested that a previous version of the .pdf ifilter works (version 5 rather than 6).
Elementary questions about Desktop Search - please help
Yngwie
More Application log messages. I thought this first one was not supposed to happen if the .pdf ifilter was disabled, but it happened anyway.
Note: Some of the errors are repeated five-ten times. How do I stop these from occurring
------------------------------------------------------------------------------------------------------------------------------
Event Type: Error
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3102
Date: 11/23/2006
Time: 7:28:39 AM
User: N/A
Computer: KGROSS03
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)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
------------------------------------------------------------------------------------------------------------------------------
Event Type: Error
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3013
Date: 11/23/2006
Time: 7:29:36 AM
User: N/A
Computer: KGROSS03
Description:
The entry <C:\WINDOWS\DEBUG\USERMODE\CHKACC.BAK> in the hash map cannot be updated.
Context: Windows Application, SystemIndex Catalog
Details:
Unspecified error
(0x80004005)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
------------------------------------------------------------------------------------------------------------------------------
Event Type: Warning
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3036
Date: 11/23/2006
Time: 7:30:18 AM
User: N/A
Computer: KGROSS03
Description:
The content source <outlookexpress://{s-1-5-21-620536925-2914786619-4216609410-1024}/{76079644-8178-4a81-b6c3-73d4eafcf461}/> cannot be accessed.
Context: Windows Application, SystemIndex Catalog
Details:
(0x81270005)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
------------------------------------------------------------------------------------------------------------------------------
Event Type: Error
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3024
Date: 11/23/2006
Time: 7:30:19 AM
User: N/A
Computer: KGROSS03
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.
Context: Windows Application, SystemIndex Catalog
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
------------------------------------------------------------------------------------------------------------------------------
Plum117
I forgot to include some details:
1. I installed the 3.0 version of desktop search.
2. another complaint: WDS will not search for Office 2007 documents - the doctype does not seem to be included in the filetype list under indexing options in the control panel.
warble
Hi Anzol,
1. WDS 3.0 has a much simpler and easy to use interface which is conveniently located on your taskbar. You can practically search just about anything from this point of entry.
2. You can always disable it not to search email by going to it's options and uncheck email indexing. However, it is a very nice feature to have your emails indexed and available for search.
3. Yes, WDS 3.0 maintains only 1 index files for all users but would gives different results based on the user who currently logs in.
The errors that you see are all known issue and has been fixed by the final release of Office 2007. If you are still running Office 2007 Beta, this might still be the case. However, not all users are experiencing the same problem with Office 2007 Beta. You can try to repair your Office 2007 installation and see if this will fix it. Also make sure that you are running the latest WDS 3.0 which can be downloaded from: http://support.microsoft.com/Default.aspx kbid=917013.
As for the .pdf iFilter, this is also a known issue. Please download the latest Adobe Acrobat v.8 from http://www.adobe.com where the iFilter is now compatible with WDS 3.0.
Let me know,
David Peng (MSFT)
Vegar Imsland
More problems:
I am getting the following exceptions reported in the application log from Windows Search Service as it tries to re-index. Why on earth does WDS complain in the application log when it can't get access to things This was the reason I disabled it in the first place because hundreds of these log entries are created, turning my whole application log bright red. What were Microsoft staff thinking
Event Type: Warning
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3036
Date: 11/23/2006
Time: 5:35:16 AM
User: N/A
Computer: KGROSS03
Description:
The content source <mapi://{s-1-5-21-620536925-2914786619-4216609410-1024}/> cannot be accessed.
Context: Windows Application, SystemIndex Catalog
Details:
A server error occurred. Check that the server is available. (0x80041206)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-------------------------------------------------------------------------------------------------------------------------------------------------
Event Type: Error
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3024
Date: 11/23/2006
Time: 5:35:17 AM
User: N/A
Computer: KGROSS03
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.
Context: Windows Application, SystemIndex Catalog
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-------------------------------------------------------------------------------------------------------------------------------------------------
Event Type: Warning
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3036
Date: 11/23/2006
Time: 5:37:12 AM
User: N/A
Computer: KGROSS03
Description:
The content source <mapi://{s-1-5-21-620536925-2914786619-4216609410-1024}/> cannot be accessed.
Context: Windows Application, SystemIndex Catalog
Details:
A server error occurred. Check that the server is available. (0x80041206)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-------------------------------------------------------------------------------------------------------------------------------------------------
Event Type: Error
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3013
Date: 11/23/2006
Time: 5:40:59 AM
User: N/A
Computer: KGROSS03
Description:
The entry <C:\DOCUMENTS AND SETTINGS\KEN\RECENT\TEAMFOUNDATION.DOC.LNK> in the hash map cannot be updated.
Context: Windows Application, SystemIndex Catalog
Details:
Unspecified error
(0x80004005)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
John CHLee
I have the same problem, but it's not on beta. I have a clean install of Windows Vista Business, Office Enterprise 2007, logged on a domain with SBS 2003 R2... all clean and fresh, all updates just installed. A LOT of windows search errors like the ones posted by Anzol. Thought of downgrading Office to 2003 ... i'll let you know if that makes any difference. Otherwise, I have to downgrade my client back to XP Pro... it's been a total nightmare.
One note: I only installed three computers with Vista: two upgrades and a clean install, all Vista Business. The upgrades work fine... but the clean install is the messiest around, crashing all applications 10 times a day and lots of errors in event log. And btw, these are the most unintelligible kind of errors i've ever seen on any computer system.
Sincerely,
Mark V.
Kishaloy
I was running the released version of Office 2007, not the pre-release. I subsequently opened a case with Microsoft to investigate. It was not possible to fix these errors. The errors are due to WDS, not to Office, which we established with multiple tests in the Microsoft case.
The problems with WDS3.0 were so bad, I finally had to uninstall it. And I do not plan to use WDS again until I can get a version that can be installed in a business network environment and supported by a large company. My impression is that the current version is only suitable for home users, and maybe not even. This is the most disappointing product I have seen from Microsoft in a while.
The Admiral
Thanks for the info.
I to am seeing an number of Event 3013 errors running WIndows 2003 SP2, WDS 3.01, and MS Office 2003
sugrhigh