Problem did not disappear (Indexing)

Hello David Peng, Eric Wolz, Ari Polsky and whoever else does support there at MS-WDS

please take a look at the following threads:

http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=1319399&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=1297957&SiteID=1

I, as well as some others, posted quite some information regarding this issue. It was the information you requested initially but we still can't see that any one at your site seriously takes care of that problem. Why

This goes on for over six months now and we still cannot use WDS here at my site.

In the meantime there is a workaround. Please create the following DWORD registry value:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\FolderRedirection

set its value to 0

The effect of this change is that Search will no longer automatically find a redirected My Documents folder. So if you change the location of My Documents after setting this value, Search will not automatically find the new location (you can still add it manually through the Indexing control panel applet if it's not already in the search scope). If you don't use redirected My Documents (or if you use it but don't change the location after setting this value) then there is no impact.

Directions for adding the value to the registry:

Go to Start -> Run (or Windows Key + R), type regedit and click ok.

In the navigation pane on the left, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search.

Right-click on the Windows Search key on the left and click New -> DWORD value. Type FolderRedirection as the name of the new value. Double-click on the newly created value on the right and type 0 as its value.

Please post back here and let us know if this worked for you or not.

This solution looked good. I had high hopes! But alas, this did not correct my problem. I have the same symptoms (original posting included here).

----ORIGINAL PROBLEM DESCRIPTION ----

WDS has successfully indexed all it has to (as far as I can tell). I index 162,530 items in Outlook 2007, OneNote 2007, and My Documents, including some HUGE .pst mail archive files. Searching works great! Almost everything is as it should be. HOWEVER, every time I restart Windows, the "Items left to scan" rises to maybe 35,000 and pounds the *** out of the machine - making the restart take a LONG time (unless I manually stop it). Then once it reaches the "top", it counts back down to 0 - without the "Items indexed so far" rising a bit. Almost like it is scanning lots of entries only to find they do not need indexing - but that's just a WAG.

This is nuisance.

Brand new ThinkPad, Win XP Pro and Office 2007 - all fresh install with all updates.

TIA.

I've done a bit more digging and the workaround that I posted earlier will not work. Please try this instead:

Go the Indexing Options control panel applet and click the Modify button. In the file tree, expand C: and UNCHECK the Documents and Settings folder. Expand Documents and Settings and select each subfolder under it that corresponds to a user whose files you want to be indexed. Click OK.

While this will not completely solve the problem it should mitigate it considerably. Instead of recrawling all the files on C: it should recrawl only the files in your user directory, which should have a negligible impact on performance. What I mean by recrawl is not a complete reindexing, it is just revisiting each file to see if it's been updated since it was indexed. Doing this to only the files in your user directory should not impact performance noticeably.

Please post back here and let us know if this worked or not.

The workarounds described by Ari Polsky did not show any effect. As Gerald Haslhofer assumed, I index network shares. And meanwhile, for testing purposes, only network shares (because these are the most important for me), no local files, no outlook folders.

As once suggested, I also deactivated all of the filetype plugins to see if one of those would be responsible for this behaviour, but that did not change anything.

I' m not quite sure about the usual behaviour of WDS at this moment: How does WDS keep track of updates of files Is it by recrawling all indexed items or by querying the USN-journal Which means: Is it normal for WDS to set up all indexed items as "left to check" at startup and to recrawl everything, and thus is it just a thing of adjusting the workload on the local machine Or is WDS normally only checking the files that have changed effectively

Hello MS-Staff,

it would be great if you told us what is going to happen with this problem.

Do you need us to try out some things to narrow down the problem

Will some fix be included in an upcoming version and when

Hope dies last. But it is feeling rather sick already... ;-)

Assuming I want to hang on, how would one find this 31.08.2007 build

TIA.

Sorry to double up, esepcially with a seemingly dumb question, but now that I think of it how do I FIND the version of WDS I am running

Thanks again.

Outstanding. Thanks. Now, how do I find the 31.08.2007 build alluded to earlier in this thread FYI, the version I am running now is 03.01.6000.72