Crystal Reports 12 merge module fails ICE validation during installation

[plokolp]

Hi there,

I am using the CR 2008 merge module that I downloaded from the SAP/BO site, and am using MSI Factory 2.0 to install my product. The ICE validation fails during the build with the following errors.

C:\v9.wxs(6680) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'INSTALLDIR' which cannot be merged from the merge module 'C:\Program Files\Common Files\Merge Modules\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
C:\v9.wxs(6680) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'ProgramMenuFolder' which cannot be merged from the merge module 'C:\Program Files\Common Files\Merge Modules\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
C:\v9.wxs(6680) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'CommonAppDataFolder' which cannot be merged from the merge module 'C:\Program Files\Common Files\Merge Modules\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
C:v9.wxs(6680) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'ProgramFilesFolder' which cannot be merged from the merge module 'C:\Program Files\Common Files\Merge Modules\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
light.exe : error LGHT0204 : ICE79: Feature 'CMS' referenced in column 'InstallExecuteSequence'.'Condition' of row 'CMSsetupConfiguration.9CED35E4_C9E6_11D3_9833_00A 0C9DA4FE9' is invalid.

Any ideas what this means?

Thanks,

Rod

[plokolp]

Can anyone help here? Many thanks, Rod

[fpci]

I get a similar error.

Were you able to figure this out ?


Linking compiled files together as 'C:\Documents and Settings\User\My Documents\MSI Factory\Output\Studio 4.0\FPS4_Installer_A.msi'
Microsoft (R) Windows Installer Xml Linker version 3.5.1030.0
Copyright (C) Microsoft Corporation. All rights reserved.

C:\Documents and Settings\User\My Documents\MSI Factory\Output\Studio 4.0\Build Files\FPS4_Installer_A.wxs(877) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'INSTALLDIR' which cannot be merged from the merge module 'C:\Program Files\MSI Factory Trial\Merge Modules\cr120_mm\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
C:\Documents and Settings\User\My Documents\MSI Factory\Output\Studio 4.0\Build Files\FPS4_Installer_A.wxs(877) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'DesktopFolder' which cannot be merged from the merge module 'C:\Program Files\MSI Factory Trial\Merge Modules\cr120_mm\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
C:\Documents and Settings\User\My Documents\MSI Factory\Output\Studio 4.0\Build Files\FPS4_Installer_A.wxs(877) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'ProgramMenuFolder' which cannot be merged from the merge module 'C:\Program Files\MSI Factory Trial\Merge Modules\cr120_mm\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
C:\Documents and Settings\User\My Documents\MSI Factory\Output\Studio 4.0\Build Files\FPS4_Installer_A.wxs(877) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'ProgramFilesFolder' which cannot be merged from the merge module 'C:\Program Files\MSI Factory Trial\Merge Modules\cr120_mm\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
light.exe : error LGHT0204 : ICE79: Feature 'CMS' referenced in column 'InstallExecuteSequence'.'Condition' of row 'CMSsetupConfiguration.9CED35E4_C9E6_11D3_9833_00A 0C9DA4FE9' is invalid.

Link successful - 'C:\Documents and Settings\User\My Documents\MSI Factory\Output\Studio 4.0\FPS4_Installer_A.msi' generated.
Error 5002: Validation Failed - 'FPS4_Installer_A.msi' was generated successfully but ICE validation errors occurred.
Deleting temporary files

Build FAILED! Error: 5002 - The setup (.msi) file was created but it did not pass ICE validation. See the individual ICE validation messages above for details.

[plokolp]

I ended up using the Crystal Reports .msi installer. I remember reading somewhere (sorry can't remember), that the CR merge modules are unreliable, and clunky. That may have even come from SAP themselves...

Anyway, using the CR.MSI got around this issue, and I think it makes a better install anyway.

Updates should be easier, and CR appears as part of the installed programs in Control Panel etc.

Hope this helps.

[fpci]

Yeah, I was able to get it going through the .msi as well, but the problem with that is I can't install the .msi on a win2k machine.

When we were using Installshield, the merge module didn't have any problems and we were able to get it on a win2k machine through the merge module.

Also, I noticed with the .msi that it would put a crystalreports12 folder in the root and in the business developments folder.

Are you using the CRRuntime_12_0_mlb.msi ?

[fpci]

I found something interesting.
I wrapped up the crystal merge module in it's own project.
The above errors were still created, but an .msi was still made.

When I run the .msi, it installs the crystal merge module correctly.

I found that the runtime wasn't installing to the installdir directory correctly for some reason and the msi would let me.

So far no problems with the crystal reports.