Errors installing Business Contact Manager

Hi,

have you tried reregistering MSI?

Start > Run > msiexec.exe /unreg
Reboot
Start > Run > msiexec.exe /regserver

If that doesn't help, try updating to the latest Installshield Engine as described here:
http://consumerdocs.installshield.com/selfservice/viewContent.do?externalId=Q108322&sliceId=1

Good luck.

OK,

 I registered MSI but had the same issue.

Went to the article you suggested but there is one problem, my version of the installer is 3.0.6912.0 and there is no mention of that installer in the article, it mentions less than 2.0 and the jumps to version 6.  What do you think?  

I also attached the latest failed log file
Summary.txt

So based on the log file it seems I need sqlncli.msi

I tried extracting the sql portion separately and received a similar error that sqlncli.msi could not be found.  

so now I am downloading a new version of sqlexpr from http://www.microsoft.com/downloads/details.aspx?familyid=220549b5-0b07-4448-8848-dcc397514b41&displaylang=en

 and I will let you know what happens

Thanks !

after downloading and installing sqlexpr it gives the exact same error message as does the sql installer in on the contact manager disk, unable to install native client because a valid sqlncli.msi could not be found.  Any ideas on how to get that msi package separate ?

When you say, your version of the installer is "3.0.6912.0", do you mean your version of MSI? Because it sounds plausible to have a MSI version 3.0 or 3.1 on a XP machine (Vista would use 4 up to 4.5).

The document I quoted refers to the version of Setup.Exe / Update.Exe / Install.Exe in the temporary installation folder of the application you wish to install. Are you sure you didn't mix this up?

As to sqlincli.msi: this seems to belong to the SQL 2005 installation files. I don't think you can get it from anywhere else. Is there a chance the installation media got damaged?

Sorry, misread a file name here. (SQLINCL instead of SQLNCLI) - my bad.

This refers to the MS SQL Server Native Client. Try uninstalling it before proceeding with the installation.

Ok, so here we go.  I was able to get the SQL problem squared away, downloaded the client from microsft separately, installed it, good to go.  The installation of business contact manager made it past the SQL portion but then failed again later in the install.  Attached is the log file for the installation.

As for the setup version,  its the version of the setup.exe on the install media.  The MSI was the same version, which is weird I guess?  I just double checked to be sure and its as I stated above and its definitely the setup.exe file.  Thanks !
MBSsetuptmp1BF.log

Hello?  Anybody have any ideas on this?  Thanks!

It looks like this is the failure portion of the log:   Any Ideas???

MSI (s) (68:9C) [14:07:09:201]: Assembly Error:Strong name signature verification failed for assembly '%1'.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key.
MSI (s) (68:9C) [14:07:09:201]: Note: 1: 1937 2: {F450DF1A-717D-4A02-AC0D-79B52B69CC2D} 3: 0x80131045 4: IAssemblyCacheItem 5: Commit 6: Microsoft.Interop.Mapi.Impl,Version="3.0.0.0",Culture="neutral",FileVersion="3.0.6912.0"
MSI (s) (68:9C) [14:07:09:201]: Product: Business Contact Manager for Outlook 2007 SP1 -- Error 1937.An error occurred during the installation of assembly 'Microsoft.Interop.Mapi.Impl,Version="3.0.0.0",Culture="neutral",FileVersion="3.0.6912.0"'. The signature or catalog could not be verified or is not valid. HRESULT: 0x80131045. assembly interface: IAssemblyCacheItem, function: Commit, component: {F450DF1A-717D-4A02-AC0D-79B52B69CC2D}

Error 1937.An error occurred during the installation of assembly 'Microsoft.Interop.Mapi.Impl,Version="3.0.0.0",Culture="neutral",FileVersion="3.0.6912.0"'. The signature or catalog could not be verified or is not valid. HRESULT: 0x80131045. assembly interface: IAssemblyCacheItem, function: Commit, component:

Sorry for requoting what you already quoted.
I had this window open for 2 hours and did not reload before posting.

LOL .. Yea MS is funny on the support.  If the software was just purchased recently, you think there is any chance of getting free support on the phone from them?  Notice how they have trained their consumers to attempt calling microsoft for support as a last resort, last ditch operation.  

Anyway man, thanks for the tips.  I was thinking about the .net framework possibly being an issue too.  I think I will start with uninstalling all related software, cleaning the reg, and rebuilding from the ground up.  Thanks again, and I will let you know how it turns out.  

Found the fix!

Updating to .net framework 3.0 fixed the issue!

Thanks again !

That final solution you left had the fix hidden within it.  I updated to .net framework 3.0 and the install was successful !! Thanks a million.  Jim

Glad to have been of help after all.