I posted this in the BCM and the Office setup groups and it got no response.
Audrey T. [MSFT] monitors and participates in the BCM group, so I assume she
is part of a team that owns some of BCM.  I read one of Audrey's posts on
another install question where this update caused a problem opening BCM, but
there was nothing new in her suggestions except to delete a registry value
(I tried this with no help):And yeah,  Milly if you read it, I'm scratching
my head.

HKCU > Software > Microsoft > Office > 11.0 >Outlook > Option > General and
delete the PONT_STRING value present.

This is intentionally double posted which I do rarely because I consider
this a BCM problem, and a setup problem and it is very difficult to tell
that anyone from MSFT pays much attention to BCM, ever has, or ever will.

It was sad to return to this group after initially helping some with BCM
association with Outlook only to find that things have gotten no better
during the entire course of Office 11 with MSFT ready to launch a $125
million PR campaign for MSFT before the Vista onslaught of publicity and the
Office 12 publicity.  I hope BCM in Office 12 will correct all the problems.
I hope someone from MSFT who owns BCM occassionally monitors this group, but
from the looks of things, probably not. MSFT seems very ambivalant about
whether they actually want to support this product.

I'm on an XPP SP2 box with Office 2003 and BCM associated and working fine
with Outlook.  Every time I try to install the recent
OfficeSBMESP2-KB911051-FullFile-ENU.EXE released Jan 20, 2006 here:

Service Pack 2 for Business Contact Manager Update and Small Business
Accounting
http://www.microsoft.com/downloads/details.aspx?familyid=96A7C105-568B-41B0-9F45
-045876CBE9A3&displaylang=en

which MSFT Update doesn't seem to be picking up despite the hype that it
would update Office now, I get the error that

"the expected version was not found on your system"   The expected version
may not be found by this install, but it is on my system and it works.  I
have already applied MOS 03 SP2 when it released.

I did not open Outlook while installing the update, and I have never seen
that to be necessary in applying any Outlook update in any version of
Office.

Does anyone know a solution?  Is this a wide-spread error say like the
pandemic that ensued with the source engine induced problems of MOS 03 SP1
that showed up all over the setup group?

Best and Tia,

Chad Harris