Failed To Get Crawl Scope Manager Error
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 13:50:56 GMT by s_ac15 (squid/3.5.20)
2008 Likes Received: 0 Hi I've noticed the error in the subject line appearing in my event log
Failed To Get The Crawl Scope Manager Outlook 2010
every time I start Outlook 2007 on my XP Pro SP3 failed to get the crawl scope manager with error=0x8007043c PC. It is followed by Failed to determine if the store is in the crawl scope (error=0x8001010d). failed to determine if the store is in the crawl scope outlook 2016 I am also getting Windows Search Service warnings and wonder if these are related? Any ideas anyone? SouthendSupporter, Aug 8, 2008 #1 Advertisements Ian Administrator Joined: http://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook-mso_windows8/outlook-2010-crawl-scope-manager-error/93cccb48-5f26-4893-985c-841b8903a164 Feb 23, 2002 Likes Received: 354 It looks like this could be the answer: Try to rebuild the index when you have WDS installed. If that doesn't solve it the do these steps: 1. Stop Indexing service "cmd: net stop wsearch" and check in TaskManager's process list that SearchIndexer.exe was really stopped. 2. Delete %SystemDrive%\ProgramData\Microsoft\Search\Data \Applications\Windows http://www.pcreview.co.uk/threads/failed-to-get-the-crawl-scope-manager-with-error-0x8001010d.3590886/ (Vista) or %AllUsersProfile%\Application Data \Microsoft\Search\Data\Applications\Windows (XP) folder with all its files and subfolders. 3. 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. 4. 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. 5. Start Indexing service back "cmd: net start wsearch" 6. Wait until "SetupCompletedSuccessfully" subkey switch back to 1. If it's still "0" after 5 minutes, it means the setup is failed again.Click to expand... Ian, Aug 8, 2008 #2 Advertisements SouthendSupporter Joined: Jul 31, 2008 Likes Received: 0 Thanks Ian -- This looks promising. Closed Outlook, Followed the instructions, restarted Outlook, --- No Errors as yet. I'll keep an eye on this and see how it goes. Thanks again. SouthendSupporter, Aug 8, 2008 #3 rawbobb Joined: Aug
loading applications such as Outlook, Word etc. An example error was "not enough quota for this operation". In the event log - http://www.scotiasystems.com/blog/it-hints-and-tips/fixed-failed-to-determine-if-the-store-is-in-the-crawl-scope/ 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 failed to 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. the crawl scope 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: Windows October 2016 M T