Nova Scotia Flag

SCOTIA SYSTEMS BLOG




Fixed : Failed to determine if the store is in the crawl scope

December 10th, 2009 admin

This PC was showing various errors when loading applications such as Outlook, Word etc.

An example error was “not enough quota for this operation”.

In the event log – the following could be found:

Failed to determine if the store is in the crawl scope (error=0x8001010d).

There were also several errors relating to Windows Search which lead me to the following solution which involves rebuilding the WDS index:

  • Stop Indexing service “cmd: net stop wsearch” and check in TaskManager’s process list that SearchIndexer.exe was really stopped.
  • Delete %SystemDrive%\ProgramData\Microsoft\Search\Data\Applications\Windows (Vista) or %AllUsersProfile%\Application Data\Microsoft\Search\Data\Applications\Windows (XP) folder with all its files and subfolders.
  • Delete the following registry keys:
    - “HKLM\Software\Microsoft\Windows Search\Applications\windows”
    - “HKLM\Software\Microsoft\Windows Search\CatalogName\windows”
    - “HKLM\Software\Microsoft\Windows Search\Databases\windows”
    - “HKLM\Software\Microsoft\Windows Search\Gather\windows”
    - “HKLM\Software\Microsoft\Windows Search\Gathering manager\Applications\windows”
    - “HKLM\Software\Microsoft\Windows Search\UsnNotifier\windows”
    You’ll have to change reg key ownership and change permission first.
  • In registry in key “HKLM\Software\Microsoft\Windows Search” switch “SetupCompletedSuccessfully” subkey to “0″ – you’ll have to change reg key ownership and change permission first.
  • Start Indexing service back “cmd: net start wsearch”
  • Wait until “SetupCompletedSuccessfully” subkey switch back to 1. If it’s still “0″ after 5 minutes, it means the setup is failed again.


    • Posted in IT Hints and Tips | 1 Comment »

    • dpminusa

      Here is what we did to get rid of this problem. It seems odd as does the error.

      We had this error after an update was installed. We installed the update with a user that has administrator privileges.

      We tried the 101 under-the-hood tricks that are stored in an empty m&m jar on Bill Gates front-porch first without success. We then went to the Icon that is created in the Office Folder for Outlook, and edited the Shortcut -> Advanced Properties to run as administrator. This seemed to allow Outlook to finish a step that the implicit administrator privileges used during the update did not.

      After this step and launching outlook, it does not seem to matter if this property is chosen or not for further launches. We suspect this was an update oops, oops.

      Hope it works for you as well.


    Tags:



    What's New?