PDA

View Full Version : error compiling IS Script CustomActions



Barbara
03-28-2006, 06:49 AM
I converted a IS 11.5 project with no errors to IS12. When compiling the IS 12 project I get a lot of errors, some of them deal with my InstallScript CustomActions:
CustomAction XXXX of type 1025 is not documented in table ISCustomActionReference.
CustomAction XXXX of type 1 is not documented in table ISCustomActionReference.
CustomAction XXXX of type 257 is not documented in table ISCustomActionReference.

I use InstallScript Custom Action with direct and deferred execution.
I deleted the CAs and added thmn again to the project, no change.
How should the ISCustomActionRefrence table be populated ?

Barbara

Barbara
03-28-2006, 09:15 AM
Some of my projects which contain InstallScript CustomActions compile without errors, but in the MSI logfile one can see that the actions can not executed at runtime
Aktion gestartet um 15:53:52: LaunchConditions.
Aktion beendet um 15:53:52: LaunchConditions. Rückgabewert 1.
MSI (c) (48:4C) [15:53:52:820]: Doing action: ReadProfileBat
Aktion 15:53:52: ReadProfileBat.
Aktion gestartet um 15:53:52: ReadProfileBat.
MSI (c) (48:C4) [15:53:52:898]: Invoking remote custom action. DLL: C:\DOCUME~1\bm\LOCALS~1\Temp\MSI54.tmp, Entrypoint: f20
1: Running InstallScript function f20
1: Installing engine...
1: IS: Using product language 0
1: IS: Extracting support file setup.inx to C:\DOCUME~1\bm\LOCALS~1\Temp\{872B06F0-400F-4E83-B43F-3EC394276FE0}\setup.inx
1: IS: Extracting support file ISRT.dll to C:\DOCUME~1\bm\LOCALS~1\Temp\{872B06F0-400F-4E83-B43F-3EC394276FE0}\ISRT.dll
1: IS: Extracting support file _isres0.dll to C:\DOCUME~1\bm\LOCALS~1\Temp\{872B06F0-400F-4E83-B43F-3EC394276FE0}\_isres.dll
1: IS: Failed to extract file _isres0.dll. Error = 0
1: Setting script cmdline...
1: ProductCode is {503952A5-00D2-41F3-A4BF-77474C4878C0}
1: Initializing Engine
1: Marshalling the , error = 0x80040155
1: Open Script operation failed, error is 0x80040155
1: Failed to shutdown script engine for script C:\DOCUME~1\bm\LOCALS~1\Temp\{872B06F0-400F-4E83-B43F-3EC394276FE0}\setup.inx, error is 0x80070057
1: Initialize() Failure, Failed to Initialize script support, Error = 0x80040155
Aktion beendet um 15:53:53: ReadProfileBat. Rückgabewert 1.
MSI (c) (48:4C) [15:53:53:038]: Doing action: SetupInitialization

Barbara

DebbieL
03-28-2006, 10:24 AM
Barbara,

The errors about specific custom actions not being documented are validation errors for validator ISICE10. Here's the information in the documentation about this validator:


The intended behavior of each custom action must be documented for the Windows Vista Quality Program. This is especially helpful if system administrators deploy your product to enterprise environments; they sometimes need to know what the custom actions do.


ISICE10 verifies that each custom action in your installation is documented by validating that each entry in the CustomAction table has a corresponding ISCustomActionReference table entry.

Corrective Action
To resolve this validation error, open the Custom Actions view, select the custom action that is mentioned in the error message, and use the Help File Path setting to specify a path to the document that describes the behavior of the custom action. When you specify a value in the Help File Path setting, InstallShield adds a row for that custom action in the ISCustomActionReference table if one has not already been created.

Note that if the custom action is a merge module that is consumed in your installation project, specify the path in the Custom Actions view of the merge module project and then rebuild the merge module.

Here is some additional information from the help topic called "Documenting the Behavior of Custom Actions":


To document the behavior of a custom action in your project:

1. Create a file that describes the intended behavior of the custom action. It does not matter what type of file that you use. Note that each custom action should have its own document.
2. In the View List, under Behavior and Logic, click Custom Actions.
3. In the Custom Actions explorer, click the action that you are documenting.
4. For the Help File Path setting, click the ellipsis button (...) to browse to the file that describes the behavior of the custom action. The file should be a text-based file such as a .txt, .htm, or .rtf file.

TIP: You can specify whether InstallShield should stream the contents of each of the custom action help files into the .msi file at build time. For more information, see the description of the Include Custom Action Help setting for a product configuration in the Releases view.

I hope that helps.
Debbie L.

Barbara
03-29-2006, 03:53 AM
After entering the help information the customactions are compiled without errors. But at runtime the setup is not able to execute the custom actions.
See logfile below:

Aktion beendet um 10:29:25: LaunchConditions. Rückgabewert 1.
MSI (c) (44:DC) [10:29:25:440]: Doing action: ReadProfileBat
Aktion 10:29:25: ReadProfileBat.
Aktion gestartet um 10:29:25: ReadProfileBat.
MSI (c) (44:00) [10:29:25:502]: Invoking remote custom action. DLL: C:\DOCUME~1\bm\LOCALS~1\Temp\MSI8.tmp, Entrypoint: f20
1: Running InstallScript function f20
1: Installing engine...
1: IS: Using product language 0
1: IS: Extracting support file setup.inx to C:\DOCUME~1\bm\LOCALS~1\Temp\{AAB1FB2E-87DC-4409-BA90-3CAA321842A5}\setup.inx
1: IS: Extracting support file ISRT.dll to C:\DOCUME~1\bm\LOCALS~1\Temp\{AAB1FB2E-87DC-4409-BA90-3CAA321842A5}\ISRT.dll
1: IS: Extracting support file _isres0.dll to C:\DOCUME~1\bm\LOCALS~1\Temp\{AAB1FB2E-87DC-4409-BA90-3CAA321842A5}\_isres.dll
1: IS: Failed to extract file _isres0.dll. Error = 0
1: Setting script cmdline...
1: ProductCode is {503952A5-00D2-41F3-A4BF-77474C4878C0}
1: Initializing Engine
1: Marshalling the , error = 0x80040155
1: Open Script operation failed, error is 0x80040155
1: Failed to shutdown script engine for script C:\DOCUME~1\bm\LOCALS~1\Temp\{AAB1FB2E-87DC-4409-BA90-3CAA321842A5}\setup.inx, error is 0x80070057
1: Initialize() Failure, Failed to Initialize script support, Error = 0x80040155
Aktion beendet um 10:29:25: ReadProfileBat. Rückgabewert 1.
MSI (c) (44:DC) [10:29:25:658]: Doing action: SetupInitialization

I will start a new thread for this.
Barbara