Bugs item #1588180, was opened at 2006-10-31 11:54
Message generated for change (Settings changed) made by pmarcu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1588180&group_id=105970

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: extensions
Group: v3.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jimmy Do (jimmydo_msft)
>Assigned to: pmarcu (pmarcu)
Summary: errors and warnings when trying to 'light' HxS installer

Initial Comment:
Trying to create an installer for installing a .hxs 
file into the Visual Studo 2005 help system produces 
various errors and warnings from 'light'.

= Steps to Reproduce =
1. Unpack the attached set of files
2. Provide these 2 help-related files in the same 
directory as MyInstaller.wxs:
        AppHelpFile.hxc
        AppHelpFile.hxs
        (I could not include my .hxc and .hxs files 
because they contain documentation for internal 
software.)
3. Run these commands:
        candle MyInstaller.wxs -ext WixVSExtension
        light MyInstaller.wixobj -ext WixVSExtension


= Expected result =
The .msi should have been produced with no errors.


= Actual result =
No .msi is produced, and these errors and warnings 
were reported:

light.exe : warning LGHT1076 : ICE03: String overflow 
(greater than length permitted in column); Table: 
File, Column: File, Key(s): 
FL_vsipccNamedURLs_hxk_86888________.3643236F_FC70_11D3
_A536_0090278A1BB8
light.exe : error LGHT0204 : ICE03: Not a valid 
foreign key; Table: HelpPlugin, Column: 
HelpNamespace_Parent, Key(s): MS_VSIPCC_v80.MS_VSCC_v80
light.exe : error LGHT0204 : ICE03: Not a valid 
foreign key; Table: HelpPlugin, Column: 
HelpNamespace_Parent, Key(s): 
MS_VSIPCC_v80.MS_VSExpressCC_v80
light.exe : warning LGHT1076 : ICE03: String overflow 
(greater than length permitted in column); Table: 
MsiFileHash, Column: File_, Key(s): 
FL_vsipccNamedURLs_hxk_86888________.3643236F_FC70_11D3
_A536_0090278A1BB8
light.exe : warning LGHT1076 : ICE03: String overflow 
(greater than length permitted in column); Table: 
Registry, Column: Registry, Key(s): 
_FldbVs8_RegFile_15039_________00000.3643236F_FC70_11D3
_A536_0090278A1BB8
light.exe : error LGHT0204 : ICE27: 'CreateShortcuts' 
Action in InstallExecuteSequence table in wrong place. 
Current: PostExecution, Correct: Execution
light.exe : error LGHT0204 : ICE77: 
CA_HxMerge_VSIPCC_VSCC.3643236F_FC70_11D3_A536_0090278A
1BB8 is a in-script custom action.  It must be 
sequenced in between the InstallInitialize action and 
the InstallFinalize action in the 
InstallExecuteSequence table
light.exe : error LGHT0204 : ICE77: 
CA_HxMerge_VSIPCC_VSExpCC.3643236F_FC70_11D3_A536_00902
78A1BB8 is a in-script custom action.  It must be 
sequenced in between the InstallInitialize action and 
the InstallFinalize action in the 
InstallExecuteSequence table
light.exe : warning LGHT1076 : ICE82: This action 
CommonFilesFolder.3643236F_FC70_11D3_A536_0090278A1BB8 
has duplicate sequence number 1 in the table 
InstallExecuteSequence
light.exe : warning LGHT1076 : ICE82: This action 
CommonFilesFolder.3643236F_FC70_11D3_A536_0090278A1BB8 
has duplicate sequence number 1 in the table 
InstallUISequence
light.exe : warning LGHT1076 : ICE82: This action 
CommonFilesFolder.3643236F_FC70_11D3_A536_0090278A1BB8 
has duplicate sequence number 1 in the table 
AdminExecuteSequence
light.exe : warning LGHT1076 : ICE82: This action 
CommonFilesFolder.3643236F_FC70_11D3_A536_0090278A1BB8 
has duplicate sequence number 1 in the table 
AdminUISequence
light.exe : warning LGHT1076 : ICE82: This action 
CommonFilesFolder.3643236F_FC70_11D3_A536_0090278A1BB8 
has duplicate sequence number 1 in the table 
AdvtExecuteSequence


= Additional Info =
* The VSIPCC_Collection_Files_RTL_---_---.msm merge 
module is from this directory:
C:\Program Files\Visual Studio 2005 SDK\2006.09
\VisualStudioIntegration\Redistributables
* I'm using Wix3.

----------------------------------------------------------------------

Comment By: iamhere2 (iamhere2)
Date: 2007-09-17 08:48

Message:
Logged In: YES 
user_id=1888651
Originator: NO

Well, what about fixing error in CVS/next build?

Now, to include Help registration to installer, i need to patch
WixVSExtension.dll via ildasm/ilasm !

Bug was open almost a year ago!


----------------------------------------------------------------------

Comment By: Sergey Koshcheyev (justme84)
Date: 2007-02-16 10:23

Message:
Logged In: YES 
user_id=1150490
Originator: NO

I modified ext\VSExtension\wixext\Data\tables.xml to remove
keyTable="File" keyColumn="1" from HelpNamespace_ and HelpNamespace_Parent
columns and recompiled Wix. The build ran fine (with some warnings though),
and the generated .msi registered the help collection successfully.

----------------------------------------------------------------------

Comment By: Sergey Koshcheyev (justme84)
Date: 2007-02-16 04:54

Message:
Logged In: YES 
user_id=1150490
Originator: NO

Only the last line in the InstallExecuteSequence is required, i.e.:

<InstallExecuteSequence>
    <InstallFinalize Sequence="7800" />
</InstallExecuteSequence>

Also, when I look into MSHelp2_RegTables__RTL_---_---.msm in Orca, the
_Validation table entry for table HelpPlugin, column HelpNamespace_ has
nothing in KeyTable and KeyColumn columns. From my limited experience it
looks that HelpNamespace_ column is not a foreign key to any other table.
However, the table schema embedded in WixVSExtension.dll indicates that
WixVSExtension.dll thinks that HelpNamespace_ column is a foreign key to
HelpNamespace table, which is apparently wrong.

The situation is the same with HelpPlugin.HelpNamespace_Parent column. I
wonder if recompiling WiX adjusting the schema will remove the ICE03 error,
I'm going to try it later today.

Hope that helps,
Sergey

----------------------------------------------------------------------

Comment By: Bob Arnson (barnson)
Date: 2006-11-12 22:02

Message:
Logged In: YES 
user_id=26581

I can reproduce with no problem. You can work around the
custom action errors with:

<InstallExecuteSequence>
    <ProcessComponents Sequence="2600" />
    <UnpublishComponents Sequence="2700" />
    <UnpublishFeatures Sequence="2800" />
    <StopServices Sequence="2900" />
    <RegisterComPlus Sequence="6700" />
    <CreateShortcuts Sequence="7590" />
    <InstallFinalize Sequence="7800" />
</InstallExecuteSequence>

Probably not all of those are required but I wasn't able to
narrow them down.

I haven't been able to work around the ICE03 errors. Try
-notidy and then running the resulting .msi. If it works,
you can use -sice to suppress the ICE validation. I suspect
the problem is that the HelpNamespace_Parent columns refer
to HelpNamespace rows that don't exist in the .msi. The Help
CAs require that DExplore registration is present on the
target machine so they don't fail at runtime.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1588180&group_id=105970

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs

Reply via email to