Thanks Luther for response.
After Getting the warning that BCM 2003 had issues with Vista, the
installation continues and completes without problems. When I run Outlook
2003 I get the "Do you want to integrate BCM with this outlook Profile, then
the error pops up about no being able to connect to the database engine.
The sp4 patch will not install and doesn,t create a log file.
Also checked the event log no Application or any other evnt notification
shows up for this time period.
I suspect something wrong with SQL, not SQL Familiar, - Server is running "
MSSQL $MICROSOFTBCM STARTED" However "MSSQLServerADHelper not started.
Roger
- Show quoted text -
The basic problems with running BCM 2003 lies in the permission
differences. BCM and MSDE (Sql Server 2000) operated under the
assumption that if a user is an administrator, then their processes
will be able to do whatever an administrator is allowed to. On Vista,
a UAC prompt pops up in those situations, and older apps aren't
prepared to handle that.
The BCM issue can be somewhat mitigated by running Outlook as an
administrator, but MSDE is more problematic.
BCM 2007 and BCM 2003 SP4 address those problems by launching actions
that require admin privileges as separate apps (e.g. to open the
firewall when sharing is turned on) and those separate apps are
prepared to handle the UAC prompt. They also change some folder
permissions to allow the sql process to read and write database files.
And most importantly they work with Sql Server 2005 SP2 which is
compatible with Vista (I believe any release of Sql Server 2005 will
work with BCM, but because of some issues that don't affect BCM, Vista
warns users when installing pre-SP2 Sql).
So, you will need either BCM 2007 or 2003 SP4 to run on Vista.
What is the problem with the SP4 patch? Did you download it first and
then try running it? Check for logs concurrent with the Setup failure
in c:|users\<yourlogin>\AppData\Local\Temp.