Outlook 2007 B2+TR Instant Search OLE Registration Error

[Braz Brandt]

I'm hoping someone else is having this problem with Outlook 2007 Beta 2
TR and Instant Search.

I just downloaded the Beta 2 TR yesterday, but this problem has
persisted for me through the entirety of my Beta 2 install as well. I
was hoping that the TR would resolve my problem, but it didn't.

When I try to perform an instant search, Outlook throws a dialog box
complaining about an OLE registration error, and says that the product
needs to be reinstalled. I have uninstalled Office 2007, Windows
Desktop Search 3 Beta, and reinstalled both. I've tried both the May
released of WDS3 and the August WDS3 Beta 2.

I've uninstalled just Outlook and reinstalled, as well as uninstalling
the entire Office 2007 suite. I've tried about every permutation of
uninstalling Outlook, Office and WDS3 I can think of.

Frustratingly, Instant Search works perfectly in OneNote 2007 Beta 2 TR
(and previously, the OneNote 2007 Beta 2 install).

I'm at a loss for what to try next.

Anyone else seen this type of problem? I'd be happy to provide any
logs, if I knew where to find Outlook Instant Search logs.

Thanks in advance from a frustrated user...

 

[Patrick Schmid]

Office 2007 B2TR with WDS3 Beta 2 should be the right combo.
When you have this combo installed, have you tried running Office
Diagnostics?
How about running Outlook in safe mode (start, run, "outlook /safe").
Which operating system?

Patrick Schmid

 

[Sue Mosher [MVP-Outlook]]

What's the exact text of the error message?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Braz Brandt]

Sue:

Thanks for replying.

The exact text is in a dialog box titled just "Microsoft Office
Outlook":

"An OLE registration error occurred. The program is not installed
correctly. Run setup again for the program."

As you can imagine, I've run the install and repair several times
trying to sort this out.

Thanks again in advance for your help...

 

[Braz Brandt]

Patrick:

Thanks for responding. I'm running XP Pro SP2, patched to the most
current security hotfixes.

Running Outlook in safe mode and trying to perform a search still
returns the same error. I included the exact text of the error message
in reply to Sue's response in this thread.

Lastly, Office Diagnostics reports no problems with my Office 2007
install; the Office Diagnostics event log reports that all the
components run successfully, and find no errors.

Is there some additional diagnostic logging Outlook and/or WDS3 can
produce? There aren't any useful error messages in the Office Sessions
or Application logs on my machine. I've got two other machines in the
office with me who experience no problems with Instant Search at all.
(As an aside, very frustrating, since those two users like to point and
laugh every time I forget that Instant Search is broken...)

As I look through the Application log, I do find this error relating to
WDS and MAPI, which might shed some light to someone more versed in the
magic of WDS than me:

Source: Windows Search Service
Category: Gatherer
Event ID: 3036

"The content source
<mapi://{s-1-5-21-1085031214-562591055-725345543-3619}/> cannot be
accessed.

Context: Windows Application, SystemIndex Catalog

Details:
A word breaker was not found for the given language. Check your
current language settings and ensure that search supports the current
language. If the problem persists,
reinstall search. (0x8004110a)"

Googling for that Event ID only returns SQL and SharePoint errors, so
that hasn't been much help. I don't know if putting my SID in instead
of my username is the expected behavior of WDS. As an FYI, I'm running
the US English version of XP and Office.

Lastly, since I just reinstalled WDS3 Beta 2 today, I just had an error
thrown when accessing the Computer Management console, and tried to
expand Services and Applications:

"Snap-in failed to initialize
Name: Indexing Service
CLSID{a nice long SID goes here}"

The Indexing Service control panel opens fine, however. I don't know
if that's an issue with WDS3 in general or if it's symptomatic of my
problem.

Thanks again in advance for any help...

 

[Sue Mosher [MVP-Outlook]]

Based on that and the other information you provided Patrick, I'd suggest rebuilding the index.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Braz Brandt]

Thanks, Sue. I've tried that in the past without success, but I'll try
it again and post the results.

 

[Braz Brandt]

Sue:

Tried rebuilding the index with not success. What's odd is when I look
at the Indexing Status, it says that I have no items indexed, and the
Computer Management MMC still returns an error when I try to open
Services and Applications.

I'll try a reinstall of WDS3 Beta 2, but I suspect that won't work,
either.

 

[Sue Mosher [MVP-Outlook]]

Do let us know. If we get more troubleshooting info, I'll post back to this thread.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Braz Brandt]

Sue:

No luck. I've tried to reindex, reinstall of everything and the like.

No Instant Search in Outlook 2007 B2TR.

 

[Braz Brandt]

Sue:

No luck. I've tried to reindex, reinstall of everything and the like.

No Instant Search in Outlook 2007 B2TR.