#1261 MSM inclusion does not work (ICE83)
I want to integrate a merge module into an installer project.
I did:
<wix xmlns="http://schemas.microsoft.com/wix/2006/wi">
<product id="user-content-54cf7406-b6ca-41d0-b1ae-65aef65ad687" name="testproject" language="1033" version="1.0.0.0" manufacturer="testproject" upgradecode="d468d9df-3108-4cb4-b584-b3d2f4444733">
<package installerversion="200" compressed="yes"></package></product></wix>
<Media Id="1" Cabinet="testproject.cab" EmbedCab="yes" />
<Directory Id="TARGETDIR" Name="SourceDir">
<Directory Id="ProgramFilesFolder">
<Directory Id="INSTALLLOCATION" Name="testproject">
<Merge Id="DataStorage.msm.581A6797-0DA2-4ee8-987D-48C809EC96D3" Language="1033" DiskId="1"
SourceFile ="D:\wixtest\testproject\Merge.Ccis.DataStorage.msm">
</Merge>
</Directory>
</Directory>
</Directory>
<Feature Id="DataStorage" Title="DataStorage" Level="1" >
<MergeRef Id="DataStorage.msm.581A6797-0DA2-4ee8-987D-48C809EC96D3"/>
</Feature>
<UIRef Id="WixUI_Mondo"/>
I get the error message :
C:\Programme\Windows Installer XML v3\bin\candle.exe -dDebug -d"DevEnvDir=Undefined if not building from within Visual Studio" -d"SolutionDir=Undefined if not building a solution or within Visual Studio" -d"SolutionExt=Undefined if not building a solution or within Visual Studio" -d"SolutionFileName=Undefined if not building a solution or within Visual Studio" -d"SolutionName=Undefined if not building a solution or within Visual Studio" -d"SolutionPath=Undefined if not building a solution or within Visual Studio" -dConfiguration=Debug -dOutDir=bin\Debug\ -dPlatform=x86 -dProjectDir=d:\wixtest\testproject\ -dProjectExt=.wixproj -dProjectFileName=testproject.wixproj -dProjectName=testproject -dProjectPath=d:\wixtest\testproject\testproject.wixproj -dTargetDir=d:\wixtest\testproject\bin\Debug\ -dTargetExt=.msi -dTargetFileName=testproject.msi -dTargetName=testproject -dTargetPath=d:\wixtest\testproject\bin\Debug\testproject.msi -out obj\Debug\Product.wixobj -arch x86 Product.wxs
C:\Programme\Windows Installer XML v3\bin\Light.exe -out d:\wixtest\testproject\bin\Debug\testproject.msi -pdbout d:\wixtest\testproject\bin\Debug\testproject.wixpdb obj\Debug\Product.wixobj
d:\wixtest\testproject\Product.wxs(23,0)Error LGHT0094: Done building project "testproject.wixproj" -- FAILED.
Build FAILED.
I am using MVS 2005 for both wix and the generation of the msm module.
If I take files only into the msm, it works.
As soon as I include c# .net code I fail.
Any help?
Discussion
Logged In: YES
user_id=991639
Originator: NO
The core problem here is that the message for error 94 is getting cut off in VS2005. That is a known issue. To fix your specific problem, you need to resolve the missing symbol. Error 94 message: "Unresolved reference to symbol '{2}' in section '{0}:{1}'." If you run from the command-line you should get a full message that will help you resolve the problem. From a quick glance at your command-line it looks like you are forgetting to add the Extension for the WixUI.
Logged In: YES
user_id=1688544
Originator: YES
Many thanks.
The console output is:
D:\wixtest\testproject>"C:\Programme\Windows Installer XML v3\bin\candle.exe" -d
Debug -d"DevEnvDir=Undefined if not building from within Visual Studio" -d"Sol
utionDir=Undefined if not building a solution or within Visual Studio" -d"Solu
tionExt=Undefined if not building a solution or within Visual Studio" -d"Solut
ionFileName=Undefined if not building a solution or within Visual Studio" -d"S
olutionName=Undefined if not building a solution or within Visual Studio" -d"S
olutionPath=Undefined if not building a solution or within Visual Studio" -dCo
nfiguration=Debug -dOutDir=bin\Debug\ -dPlatform=x86 -dProjectDir=D:\wixtest\tes
tproject\ -dProjectExt=.wixproj -dProjectFileName=testproject.wixproj -dProjectN
ame=testproject -dProjectPath=D:\wixtest\testproject\testproject.wixproj -dTarge
tDir=D:\wixtest\testproject\bin\Debug\ -dTargetExt=.msi -dTargetFileName=testpro
ject.msi -dTargetName=testproject -dTargetPath=D:\wixtest\testproject\bin\Debug\
testproject.msi -out obj\Debug\Product.wixobj -arch x86 Product.wxs
Microsoft (R) Windows Installer Xml Compiler version 3.0.4227.0
Copyright (C) Microsoft Corporation. All rights reserved.
Product.wxs
D:\wixtest\testproject>"C:\Programme\Windows Installer XML v3\bin\Light.exe" -ou
t D:\wixtest\testproject\bin\Debug\testproject.msi -pdbout D:\wixtest\testprojec
t\bin\Debug\testproject.wixpdb obj\Debug\Product.wixobj
Microsoft (R) Windows Installer Xml Linker version 3.0.4227.0
Copyright (C) Microsoft Corporation. All rights reserved.
D:\wixtest\testproject\Product.wxs(23) : error LGHT0094 : Unresolved reference t
o symbol 'WixUI:WixUI_Mondo' in section 'Product:{54CF7406-B6CA-41D0-B1AE-65AEF6
5AD687}'.
which is hard to find out as WixUI_Mondo should be a well known symbol. I did a reinstallation without success.
Logged In: YES
user_id=26581
Originator: NO
As Rob mentioned, you need to add a reference to WixUIExtension; it's not force-loaded, so WixUI_Mondo isn't always available.
Logged In: YES
user_id=1688544
Originator: YES
I now have added the WixUIExtension, but I failed again.
D:\wixtest\testproject>"C:\Programme\Windows Installer XML v3\bin\candle.exe" -d
Debug -d"DevEnvDir=Undefined if not building from within Visual Studio" -d"Sol
utionDir=Undefined if not building a solution or within Visual Studio" -d"Solu
tionExt=Undefined if not building a solution or within Visual Studio" -d"Solut
ionFileName=Undefined if not building a solution or within Visual Studio" -d"S
olutionName=Undefined if not building a solution or within Visual Studio" -d"S
olutionPath=Undefined if not building a solution or within Visual Studio" -dCo
nfiguration=Debug -dOutDir=bin\Debug\ -dPlatform=x86 -dProjectDir=D:\wixtest\tes
tproject\ -dProjectExt=.wixproj -dProjectFileName=testproject.wixproj -dProjectN
ame=testproject -dProjectPath=D:\wixtest\testproject\testproject.wixproj -dTarge
tDir=D:\wixtest\testproject\bin\Debug\ -dTargetExt=.msi -dTargetFileName=testpro
ject.msi -dTargetName=testproject -dTargetPath=D:\wixtest\testproject\bin\Debug\
testproject.msi -out obj\Debug\Product.wixobj -arch x86 Product.wxs
Microsoft (R) Windows Installer Xml Compiler version 3.0.4227.0
Copyright (C) Microsoft Corporation. All rights reserved.
Product.wxs
D:\wixtest\testproject>"C:\Programme\Windows Installer XML v3\bin\Light.exe" -ou
t D:\wixtest\testproject\bin\Debug\testproject.msi -pdbout D:\wixtest\testprojec
t\bin\Debug\testproject.wixpdb -ext WixUIExtension -cultures:en-us obj\Debug\Pro
duct.wixobj
Microsoft (R) Windows Installer Xml Linker version 3.0.4227.0
Copyright (C) Microsoft Corporation. All rights reserved.
C:\Dokumente und Einstellungen\podien_wolfram\Lokale Einstellungen\Temp\rgo91cds
\testproject.msi : error LGHT0204 : ICE83: Both MsiPublishAssemblies AND MsiUnpu
blishAssemblies actions MUST be present in InstallExecuteSequence table.
C:\Dokumente und Einstellungen\podien_wolfram\Lokale Einstellungen\Temp\rgo91cds
\testproject.msi : error LGHT0204 : ICE83: The MsiPublishAssemblies action MUST
be present in AdvtExecuteSequence table.
I am puzzeled now as I think I did not do anything wrong. The wxs file did not change so far.
Logged In: YES
user_id=26581
Originator: NO
That's due to bugs in the merge module you're including. You need to get support from whoever's supplying the module.
Logged In: YES
user_id=1688544
Originator: YES
The merge module is build by Microsoft Visual Studio 2005 SP1!!!
I have build a test project - a hello world program. That does not work either.
I have added this project to this bugzilla.
If you try you have to copy the output from the merge module build to the testproject folder manually.
As it is only a c# hello world program I think it would occur with every merge module. So it worth looking at it!!!
File Added: wixtest.zip
Logged In: YES
user_id=991639
Originator: NO
Yes, the Visual Studio Setup projects do not create Merge Modules to spec. To work around their shortcomings, you can add the actions specified in the ICE38 error message to your InstallExecuteSequence.
Logged In: YES
user_id=1688544
Originator: YES
1) Do you mean ice38 or ice83 in your answer?
2) Is there any Microsoft Visual Studio known that works corretely?
3) Is there a more detailed description how to solve that bug?
Logged In: YES
user_id=1688544
Originator: YES
1) Do you mean ice38 or ice83 in your answer?
2) Is there any Microsoft Visual Studio known that works corretely?
3) Is there a more detailed description how to solve that bug?
4) Why does this bug not occur on WIX 2.0?
Logged In: YES
user_id=991639
Originator: NO
Bugs are not for conversations. Please follow up on wix-users@lists.sourceforge.net for discussion about how to correctly handle your scenario.