Hi: That's only one problem. Here are two more related problems:
1. The specs state that WDS3.01 will snooze - stop indexing - when another activity is initiated by the user. Reality: WDS3.01 keeps going regardless, hogging resources and seriously slowing the computer despite generous RAM of 2GB
2. The specs also state that WDS3.01 will stop indexing when the computer is on battery power. Reality: indexing keeps going while on battery power causing fast power drain.
I'd be grateful for any help for all three problem. TXS, EM
Eric Wolz - MSFT wrote:
Can you try and disable the .XML file extension in the "Indexing Options" control panel and see if that helps with your performance issues?
It doesn't Work there is another thread "WDS Rescan issue" and people have been screaming but no one from MS is looking at it anymore. Its a widespread problem / Bug and MS is not interested to research/answer anymore.
I, on my installation, only experienced this problem with network locations. I just reinstalled WDS and tried again, set up one network folder for indexing, let WDS index it, up to 23,279 files, then rebooted.
After rebooting, the WDS status window showed 23,279 indexed files, then counted the "files still to check" (I work with the german version, so this is roughly translated) rapidly up to 23,400 and began to rescan. I think WDS is really scanning the elements rather than reindexing them, because network traffic is much smaller the second time. While WDS puts about 40% load on my 100MBit Ethernet connection at building the index the first time, this is only about 1-4% when rescanning/reindexing.
While counting up numbers after reboot, there is something about zero network traffic.
Have exact same issue with both PCs. It starts Building the index from zero to max and hogs the drive utilization, every time PC is rebooted. It does complete the Re-index bit faster than the original first time Index creation, but it still takes good 30-50 minutes to re-index about 85,000 items.
Eric Wolz - MSFT wrote:
Can you try and disable .XML extension from indexing?
I tried this before and tried again today: Disabled xml files, WDS started to build a completely new index, when it had finished I rebooted the system. Then the same behavior begins as I described before, WDS starts to count up new items and then starts to reindex / rescan them.