?
Solved

Errors installing Business Contact Manager

Posted on 2008-06-21
16
Medium Priority
?
1,258 Views
Last Modified: 2011-10-19
Having issues getting Business contact manager installed on XP SP2.  Office 2007 is installed and working.  Oringinally the install was failing with this is in the log:  

 ISSCRIPT_VERSION_MISSING = The InstallScript engine is missing from this machine.  If available, please run ISScript.msi, or contact your support personnel for further assistance.
Property(S): ISSCRIPT_VERSION_OLD = The InstallScript engine on this machine is older than the version required to run this setup.  If available, please install the latest version of ISScript.msi, or contact your support personnel for further assistance.
Property(S): ISVROOT_PORT_NO = 0

Then I went back and unistalled SQL 2005 to try getting a fresh start, and now the SQL portion will not even install when I go to reinstall Contact Manager.  Any Help would be greatly appreciated.  Thanks
0
Comment
Question by:jkockler
  • 10
  • 6
16 Comments
 
LVL 35

Expert Comment

by:torimar
ID: 21838019
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.
0
 
LVL 4

Author Comment

by:jkockler
ID: 21838094
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
0
 
LVL 4

Author Comment

by:jkockler
ID: 21838127
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.  
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
LVL 4

Author Comment

by:jkockler
ID: 21838143
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 !
0
 
LVL 4

Author Comment

by:jkockler
ID: 21838166
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 ?
0
 
LVL 35

Expert Comment

by:torimar
ID: 21838193
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?

0
 
LVL 35

Expert Comment

by:torimar
ID: 21838216
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.
0
 
LVL 4

Author Comment

by:jkockler
ID: 21838252
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
0
 
LVL 4

Author Comment

by:jkockler
ID: 21838966
Hello?  Anybody have any ideas on this?  Thanks!
0
 
LVL 4

Author Comment

by:jkockler
ID: 21840648
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:
0
 
LVL 35

Accepted Solution

by:
torimar earned 1500 total points
ID: 21840671
This is where the error occurs:

----------------------------------------
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: {F450DF1A-717D-4A02-AC0D-79B52B69CC2D}
MSI (s) (68:9C) [14:07:09:325]: User policy value 'DisableRollback' is 0
MSI (s) (68:9C) [14:07:09:325]: Machine policy value 'DisableRollback' is 0
Action ended 14:07:09: InstallFinalize. Return value 3.
-----------------------------------------------

Not much is known about this error, if anything at all.
After an extensive research I'd narrow the possible causes down to the following issues:

- corrupted installation media (again)
- digital signature mismatch (check for an updated version of the install files)
- .Net-Framework related problems

I'd suggest you uninstall all related products (Office, SQL, BCM etc.), run the Windows Installer Cleanup Utility (http://support.microsoft.com/kb/290301/en-us), run a CCleaner Registry clean (http://www.ccleaner.com), reboot, install the newest version of MSI (http://msdn.microsoft.com/en-us/library/aa372856(VS.85).aspx), get the latest version of .NET Framework, check for updated versions of your software. Reboot. Then reinstall.

Maybe the attached file can help you troubleshooting BCM, if errors continue to occur. But do consider contacting Microsoft Support.

I'm sorry I can't be of more help.
The impudence of Microsoft who send their paying customers through such minefields still leaves me speechless.



W09-Troubleshooting.pdf
0
 
LVL 35

Expert Comment

by:torimar
ID: 21840683
Sorry for requoting what you already quoted.
I had this window open for 2 hours and did not reload before posting.
0
 
LVL 4

Author Comment

by:jkockler
ID: 21840700
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.  
0
 
LVL 4

Author Comment

by:jkockler
ID: 21840882
Found the fix!

Updating to .net framework 3.0 fixed the issue!

Thanks again !
0
 
LVL 4

Author Closing Comment

by:jkockler
ID: 31469531
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
0
 
LVL 35

Expert Comment

by:torimar
ID: 21840993
Glad to have been of help after all.
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

New style of hardware planning for Microsoft Exchange server.
Windows Explorer let you handle zip folders nearly as any other folder: Copy, move, change, and delete, etc. In VBA you can also handle normal files and folders, but zip folders takes a little more - and that you'll find here.
The viewer will learn how to create two correlated normally distributed random variables in Excel, use a normal distribution to simulate the return on different levels of investment in each of the two funds over a period of ten years, and, create a …
Learn how to make your own table of contents in Microsoft Word using paragraph styles and the automatic table of contents tool. We'll be using the paragraph styles in Word’s Home toolbar to help you create a table of contents. Type out your initial …

829 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question