Did you also create the necessary registry entry?
BCM cannot run on SQL Server 2000, only on MSDE.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
"Anonymous Coward" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm having the exact same problem. It appears the patch has no effect
> whatsoever. Naturally I've confirmed the patch is properley installed by
> cross-referencing all the DLL file versions as described in the KB831747
> article. Definitely using cached mode. Even created a brand new outlook
> profile to try and debug this. Maybe the patch thinks our SBS2003
exchange
> server is a "genuine" exchange server? We upgraded our SBS2000 to SBS2003,
> so is there a way for software (eg the DLLs) to determine what kind of
> Exchange 2003 server it is? If I use Exchange System Manager, looking at
> the server's properties, it naturally tells me:
> Name Type Edition Server Version Modified
> SERVER Basic Standard Version 6.5 (Build 6944.4) 7/04/2004 1:20 PM
>
> So, how to use SBS2003 exchange and Business Contact Manager together?
Has
> anyone here been successfull??
>
> I know it's probably designed so this can't be done, but is it possible
> somehow to get Business Contact Manager to use the SQL server engine on
the
> SBS2003 server rather than install a MSDE onto each client PC?
>
>