Merging merge module 'I:\SGI\Bibliotecas\CRXI\CrystalReports11_RDC_Repo rtengine.msm'.Ĭ:\Documents and Settings\IsisSNA\Meus documentos\MSI Factory\Output\SGI-Estaticos\Build Files\Setup.wxs(660) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'ProgramFilesFolder' which cannot be merged from the merge module 'I:\SGI\Bibliotecas\CRXI\CrystalReports11_RDC_Repo rtengine.msm'. Opening merge module 'I:\SGI\Bibliotecas\CRXI\CrystalReports11_RDC_Repo rtengine.msm' with language '1033'. 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. 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.Ĭ:\Documents and Settings\IsisSNA\Meus documentos\MSI Factory\Output\SGI-Estaticos\Build Files\Setup.wxs(655) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'SystemFolder' which cannot be merged from the merge module 'I:\SGI\Bibliotecas\CRXI\CrystalReports11_RDC_Runt ime.msm'. Merging merge module 'I:\SGI\Bibliotecas\CRXI\CrystalReports11_RDC_Runt ime.msm'.Ĭ:\Documents and Settings\IsisSNA\Meus documentos\MSI Factory\Output\SGI-Estaticos\Build Files\Setup.wxs(655) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'ProgramFilesFolder' which cannot be merged from the merge module 'I:\SGI\Bibliotecas\CRXI\CrystalReports11_RDC_Runt ime.msm'. Opening merge module 'I:\SGI\Bibliotecas\CRXI\CrystalReports11_RDC_Runt ime.msm' with language '1033'. Merging merge module 'I:\SGI\Bibliotecas\VB\tabctl32.msm'. Opening merge module 'I:\SGI\Bibliotecas\VB\tabctl32.msm' with language '1033'. Merging merge module 'I:\SGI\Bibliotecas\VB\comdlg32.msm'. Opening merge module 'I:\SGI\Bibliotecas\VB\comdlg32.msm' with language '1033'. All rights reserved.Ĭreating cabinet 'C:\Documents and Settings\IsisSNA\Configura‡äes locais\Temp\pgu6fljl\#setup.cab'.
CRYSTAL REPORT 10 MERGE MODULE WINDOWS
Microsoft (R) Windows Installer Xml Compiler version. wxs file as 'C:\Documents and Settings\IsisSNA\Meus documentos\MSI Factory\Output\SGI-Estaticos\Setup.msi'Ĭompiling 'C:\Documents and Settings\IsisSNA\Meus documentos\MSI Factory\Output\SGI-Estaticos\Build Files\Setup.wxs' > Module: CR11_rdc_license (I:\SGI\Bibliotecas\CRXI\CrystalReports11_RDC_Lice nse.msm) > Module: CR11_rdc_reportengine (I:\SGI\Bibliotecas\CRXI\CrystalReports11_RDC_Repo rtengine.msm) > Module: CR11_rdc_runtime (I:\SGI\Bibliotecas\CRXI\CrystalReports11_RDC_Runt ime.msm) > Module: TABCT元2 (I:\SGI\Bibliotecas\VB\tabctl32.msm) > Module: MSWINSCK (I:\SGI\Bibliotecas\VB\mswinsck.msm) > Module: MSVBVM60 (I:\SGI\Bibliotecas\VB\msvbvm60.msm) > Module: MSSTDFMT (I:\SGI\Bibliotecas\VB\msstdfmt.msm) > Module: MSDATLST (I:\SGI\Bibliotecas\VB\msdatlst.msm) > Module: MSDATGRD (I:\SGI\Bibliotecas\VB\msdatgrd.msm) > Module: MSCOMCTL (I:\SGI\Bibliotecas\VB\mscomctl.msm) > Module: MSBIND (I:\SGI\Bibliotecas\VB\msbind.msm) > Module: MSADODC (I:\SGI\Bibliotecas\VB\msadodc.msm) > Module: OLEAUT32 (I:\SGI\Bibliotecas\VB\oleaut32.msm) > Module: COMCAT (I:\SGI\Bibliotecas\VB\comcat.msm) > Module: COMDLG32 (I:\SGI\Bibliotecas\VB\comdlg32.msm) adding file to build: C:\Documents and Settings\IsisSNA\Meus documentos\MSI Factory\Output\SGI-Estaticos\Build Files\msifactui.wxs generating main UI wxs file (msifactui.wxs) Setting language to English-US for this build.īuilding main setup. If I can't generate a package, I can not get the acquisition approval.
CRYSTAL REPORT 10 MERGE MODULE HOW TO
I looked for updated merge modules at SAP/BusinessObjects site, downloaded them, and even the new MSMs give the same errors.Ĭould someone give me some idea on how to solve it? It is interesting that with VSI we had no problems related to these MSMs. I added all the files to my MSI Factory project, but when I add the Crystal Reports XI merge modules, the MSI package is not built, due to some errors related to the CR XI MSMs. Until last year we were using Visual Studio Installer, but we were having some problems with it. I am from Brazil, and we are evaluating MSI Factory to deploy an apllication in VB6 we develop.