I have a few gajillion of these entries in my Windows Event Viewer. Judging
by the timestamps it seems to be happening about fifty times at once every
thirty seconds. Freezes my computer for a few seconds each time.

Source: Outlook
Category: None
Type: Error
Event ID: 35

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

crawl scope sounds like an indexing error. do you have windows desktop
configured to scan outlook?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:



"Jon Davis" wrote in message
...
I have a few gajillion of these entries in my Windows Event Viewer. Judging
by the timestamps it seems to be happening about fifty times at once every
thirty seconds. Freezes my computer for a few seconds each time.

Source: Outlook
Category: None
Type: Error
Event ID: 35

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

I don't know. I didn't install windows search until a month or two after I
installed Outlook, and then I thought I disabled it because it kept taking
over my machine.

Jon

"Diane Poremsky [MVP]" wrote in message
...
crawl scope sounds like an indexing error. do you have windows desktop
configured to scan outlook?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:



"Jon Davis" wrote in message
...
I have a few gajillion of these entries in my Windows Event Viewer.
Judging by the timestamps it seems to be happening about fifty times at
once every thirty seconds. Freezes my computer for a few seconds each
time.

Source: Outlook
Category: None
Type: Error
Event ID: 35

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

I have the same problem and I think it was caused by the fact that
Vista crashed unexpectedly and after I rebooted I received an error
from Outlook telling me that it did not shutdown correctly and was
running a scan. After that, that error kept popping up in the Event Log
every 20-30 seconds.

I tried a few things, including deleting my OST file. This actually
made it worst as the frequency of the error increased to every second
for about 10 minutes and reverted back to every 30 seconds.

I also tried disabling the Windows Search service to stop the errors. I
restarted Outlook and it appropriately informed me that the Quick
Search was no longer available. However, once Outlook was restarted the
errors returned. Something is seriously broken.

Vista and Office 2007 have both RTM'ed. Why are we still in beta
testing mode?

Jon Davis wrote:

I have a few gajillion of these entries in my Windows Event Viewer. Judging
by the timestamps it seems to be happening about fifty times at once every
thirty seconds. Freezes my computer for a few seconds each time.

Source: Outlook
Category: None
Type: Error
Event ID: 35

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

I have the same thing going on, only I'm constantly getting them if
Outlook is open - usually between 10-20 errors a second. I also
noticed a couple of weeks ago that the inline search for Outlook
stopped working, and when I do hit enter for it to search, it is
extremely slow, but I have just now had time to look into it. When I
try to open Indexing Options in Control Panel, it just sits there with
"Waiting to receive indexing status...", and I've left it for a long
time. Indexing everywhere else seems to be working fine. Anyone know
how to repair the index for Vista?

In case anyone else has this same issue, or anyone above has not found
it, I finally managed to fix the problem thanks to David Peng and
Google!

The fix came from the MSDN forums he
http://forums.microsoft.com/MSDN/Sho...14407&SiteID=1

Specifically:
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 (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.

I too had the same problem however I noticed my mob phone was connected which
has outlook on it. Once I disconnected the mobile phone the event
occurrences stopped completely.

Check that you do not have a similar device conncted, mob,pda etc and if so
disconnect and check your event log.

" wrote:

In case anyone else has this same issue, or anyone above has not found
it, I finally managed to fix the problem thanks to David Peng and
Google!

The fix came from the MSDN forums he
http://forums.microsoft.com/MSDN/Sho...14407&SiteID=1

Specifically:
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 (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.

Thank you this was just what I needed to solve my problem, and the directions
were easy to follow.

Joel

" wrote:

In case anyone else has this same issue, or anyone above has not found
it, I finally managed to fix the problem thanks to David Peng and
Google!

The fix came from the MSDN forums he
http://forums.microsoft.com/MSDN/Sho...14407&SiteID=1

Specifically:
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 (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.

This looks usefull. I will try it out tomorrow and then report.

" wrote:

In case anyone else has this same issue, or anyone above has not found
it, I finally managed to fix the problem thanks to David Peng and
Google!

The fix came from the MSDN forums he
http://forums.microsoft.com/MSDN/Sho...14407&SiteID=1

Specifically:
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 (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.

Hey I did the whole procedure twice...I noticed i will get these errors as
soon as i do a defrag on the drive..... The repair works fine until then.

"Roger" wrote:

This looks usefull. I will try it out tomorrow and then report.

" wrote:

In case anyone else has this same issue, or anyone above has not found
it, I finally managed to fix the problem thanks to David Peng and
Google!

The fix came from the MSDN forums he
http://forums.microsoft.com/MSDN/Sho...14407&SiteID=1

Specifically:
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 (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.