Rob--
I don't have anything to add that hasn't been posted already, but to remind
you--forgive me if this is a "beentheredonethat":
1) Check that you have 3 services on at least manual and started or if you
don't mind CPU sharing when you're not using Outlook on to automatic and
started:
MSSQL$MSFTBCM
Server (Supports file, print, and pipe sharing over the network)
SQLAgent$MICROSOFT BCM
You do not need to have MSSQLServerADHelper running for ordinary
installations, but I wouldn't speak to special SQL or other server
situations.
After making sure these are turned on, then go either to Help About Add-ins
and try to add it in or the entry under File for Data Bases and try to add
it in.
2) Be careful that you are not using a concomittant .net framework that is
newer than the one deployed by the first version of BCM. The reason I say
that is that a number of applications now are starting to use .net
frameworks, and if you are using a beta or one that has a newer .net
framework than the BCM requires, you can have problems getting the data base
engine up.
See All of Alexander Gorlach's helpful posts and his site here with tips
and his patch:
Unofficial patch:
http://blogs.officezealot.com/gorlach/archives/000858.html
And you should watch Patricia Cordoza's site here for any new developments
and helpful tips:
http://blogs.officezealot.com/cardoza/
Also be sure to apply these new patches, but that's probably not part of the
solution to this particular problem:
1) BCM Service Pack 1:
http://support.microsoft.com/?kbid=839881
2) Description of the Business Contact Manager for Outlook 2003 Security
Update: June 8, 2004
http://support.microsoft.com/?kbid=842496
Also for reference since XPSP2 is close to RTM:
FAQ: How Windows XP Service Pack 2 (SP2) Affects SQL Server and MSDE May 24,
2004
http://www.microsoft.com/sql/techinfo/administration/2000/security/winxpsp2faq.asp
hth and good luck,
Chad Harris
___________________________________________________________
