Crawl Scope error since KB946041

Since yesterday, each time I open Outlook 2007 two error entries appear in
the log "failed to determine if the store is in the crawl scope
(error=0x8001010d)". The event ID is either 34 or 35 for the two entries.
Outlook appears to run ok but I would sooner stay away from a hole rather
than fall in later.
I installed a bunch of MS updtaes yesterday and wonder if one of those is
the culprit -- and if so how to fix the error.
The relevant updates are KB947801 - Office 2007 security, KB946983 - Outlook
2007 security and KB946041. It was right after these installed that this
started to happen.
Am I alone here or has anyone else got this?

--
Hopefully

Simpleuser

Try posting this message to the Microsoft Outlook discussion group. The
Outlook experts there will be aware of all the current issues with that
software. Here is the link to that group.

http://www.microsoft.com/communities...public.outlook

--

Ronnie Vernon
Microsoft MVP
Windows Desktop Experience


"Simpleuser" <> wrote in message
news:83FAE3DA-A172-4264-95FD-...
> Since yesterday, each time I open Outlook 2007 two error entries appear in
> the log "failed to determine if the store is in the crawl scope
> (error=0x8001010d)". The event ID is either 34 or 35 for the two entries.
> Outlook appears to run ok but I would sooner stay away from a hole rather
> than fall in later.
> I installed a bunch of MS updtaes yesterday and wonder if one of those is
> the culprit -- and if so how to fix the error.
> The relevant updates are KB947801 - Office 2007 security, KB946983 -
> Outlook
> 2007 security and KB946041. It was right after these installed that this
> started to happen.
> Am I alone here or has anyone else got this?
>
> --
> Hopefully

I did originally post it on the Outlook area but have had no reply.
Still got the problem.
--
Hopefully


"Ronnie Vernon MVP" wrote:

> Simpleuser
>
> Try posting this message to the Microsoft Outlook discussion group. The
> Outlook experts there will be aware of all the current issues with that
> software. Here is the link to that group.
>
> http://www.microsoft.com/communities...public.outlook
>
> --
>
> Ronnie Vernon
> Microsoft MVP
> Windows Desktop Experience
>
>
> "Simpleuser" <> wrote in message
> news:83FAE3DA-A172-4264-95FD-...
> > Since yesterday, each time I open Outlook 2007 two error entries appear in
> > the log "failed to determine if the store is in the crawl scope
> > (error=0x8001010d)". The event ID is either 34 or 35 for the two entries.
> > Outlook appears to run ok but I would sooner stay away from a hole rather
> > than fall in later.
> > I installed a bunch of MS updtaes yesterday and wonder if one of those is
> > the culprit -- and if so how to fix the error.
> > The relevant updates are KB947801 - Office 2007 security, KB946983 -
> > Outlook
> > 2007 security and KB946041. It was right after these installed that this
> > started to happen.
> > Am I alone here or has anyone else got this?
> >
> > --
> > Hopefully
>

Ronnie - to clarify my earlier post. I had put my question in
public.outlook.general but I now see your link is to New Users, so I have
posted there as well. Hopefully someone will be able to help. Thanks anyway.
--
Hopefully


"Ronnie Vernon MVP" wrote:

> Simpleuser
>
> Try posting this message to the Microsoft Outlook discussion group. The
> Outlook experts there will be aware of all the current issues with that
> software. Here is the link to that group.
>
> http://www.microsoft.com/communities...public.outlook
>
> --
>
> Ronnie Vernon
> Microsoft MVP
> Windows Desktop Experience
>
>
> "Simpleuser" <> wrote in message
> news:83FAE3DA-A172-4264-95FD-...
> > Since yesterday, each time I open Outlook 2007 two error entries appear in
> > the log "failed to determine if the store is in the crawl scope
> > (error=0x8001010d)". The event ID is either 34 or 35 for the two entries.
> > Outlook appears to run ok but I would sooner stay away from a hole rather
> > than fall in later.
> > I installed a bunch of MS updtaes yesterday and wonder if one of those is
> > the culprit -- and if so how to fix the error.
> > The relevant updates are KB947801 - Office 2007 security, KB946983 -
> > Outlook
> > 2007 security and KB946041. It was right after these installed that this
> > started to happen.
> > Am I alone here or has anyone else got this?
> >
> > --
> > Hopefully
>

Try restarting Windows search by changing this value in your registry. All
normal caveats to editing the registry apply.
HKEY_LOCAL_Machine\Software\Microsoft\Windows Search\SetupCompleted Change
the value from "1" to "0". This will re-initialize the search function. This
parameter is in the Windows Search folder not a subfolder!

I found this solution by searching the windows vista forum last year. The
problem was created by a registry cleaner program that deleted some registry
values for Outlook search. I brought it to the attention of the software
company. The problem was some of the registry entries paths for Outlook
ended with an "*" and some didn't. The cleaner deleted the ones without the
"*" and search crashed. I edited necessary entries to include the "*" and
registry cleaner ignored them. I have since stopped using any registry
cleaners with Vista as recommended by others.


"Simpleuser" <> wrote in message
news:E9141370-3C5C-4FC8-93AA-...
> I did originally post it on the Outlook area but have had no reply.
> Still got the problem.
> --
> Hopefully
>
>
> "Ronnie Vernon MVP" wrote:
>
>> Simpleuser
>>
>> Try posting this message to the Microsoft Outlook discussion group. The
>> Outlook experts there will be aware of all the current issues with that
>> software. Here is the link to that group.
>>
>> http://www.microsoft.com/communities...public.outlook
>>
>> --
>>
>> Ronnie Vernon
>> Microsoft MVP
>> Windows Desktop Experience
>>
>>
>> "Simpleuser" <> wrote in message
>> news:83FAE3DA-A172-4264-95FD-...
>> > Since yesterday, each time I open Outlook 2007 two error entries appear
>> > in
>> > the log "failed to determine if the store is in the crawl scope
>> > (error=0x8001010d)". The event ID is either 34 or 35 for the two
>> > entries.
>> > Outlook appears to run ok but I would sooner stay away from a hole
>> > rather
>> > than fall in later.
>> > I installed a bunch of MS updtaes yesterday and wonder if one of those
>> > is
>> > the culprit -- and if so how to fix the error.
>> > The relevant updates are KB947801 - Office 2007 security, KB946983 -
>> > Outlook
>> > 2007 security and KB946041. It was right after these installed that
>> > this
>> > started to happen.
>> > Am I alone here or has anyone else got this?
>> >
>> > --
>> > Hopefully
>>