> Trying to install CD2 of Microsoft Office 2007 with Business Contact
> Manager, gets about 1/3 of the way thru when i get error message.
[quoted text clipped - 22 lines]
> warranty. CD1 with Office 2007 installed without a hitch. CD2 with
> Business Contact Manager is the problem.
When Sql fails to install correctly your best bet is to try installing
Sql Server 2005 SP2 by itself.
BCM setup suppresses Sql's setup ui, which is a good thing in general,
but not helpful when the Sql install fails.
KyeLani - 29 Feb 2008 18:28 GMT
I had this trouble too.
My initial install of Outlook with BCM only installed Outlook. BCM failed to
install and I spent a full day uninstalling the SQL components and deleting
directories, making sure files weren't encrypted or compressed in an effort
to get to the bottom of it.
Each time I tried again to install, or when I tried to install standalone
SQL 2005 Express during the process of working around it, the whole process
failed to install MSXML6 and everything else failed too.
Roughly 24 hours later...
I decided to remove MSXML6 while I was in there removing the SQL parts
(again!). I seemed to have a bit of a gremlin because there were two
instances of it and one of them wouldn't uninstall using Add/Remove programs
- I got a message saying that operation could only be performed on an
installed item(?!), so I figured that might be the root of the problem.
Bearing in mind that I have no other apps installed that make use of SQL
Server 2005, here's how MY version of this problem was finally resolved:
1. Use Windows Install Clean up utility to remove MSXML 6.0 Parser and any
SQL server items from the list
2. Delete MS SQL 2005 directory from Program Files
3. Install standalone version of MSXML
4. Install standalone version of SQL 2005 Express
5. Run Outlook w/BCM installer again
I sincerely hope that helps someone :)
Jammers - 01 Mar 2008 15:54 GMT