Warning -9018: Custom Actions Ignored

AdminStudio 2022 | 23.0 | Automated Application Converter / App-V Assistant / ThinApp Assistant / Citrix Assistant

The following table documents this message:

Warning -9018: Custom Actions Ignored

Category

Description

Type:

Warning

Message:

Custom action 'CustomActionName' will be ignored.

Cause:

When converting a Windows Installer package to a Citrix profile, all custom actions are ignored. Any modifications to a target machine that a custom action in this Windows Installer package may create will not be propagated into the Citrix profile.

Note:When a custom action that does not modify the system or perform any part of the installation (such as an InstallShield Editor predefined custom action or a Type 19 custom action) is encountered, no message is generated. If a Type 51 custom action is encountered (which sets a property from a formatted text string), it is automatically resolved. If a Type 35 custom action is encountered, it is only resolved if it is referenced in the Directory table.

Resolution:

The resolution that you should perform depends upon the purpose of the custom action:

• If the custom action merely automatically enters a value or makes some other kind of minor modification, you can ignore this warning.
• If the custom action does something which could change the behavior of the installation (such as setting a Property), you may need to resolve this issue.

To resolve this issue, first attempt to launch the converted package on Citrix XenApp. If you receive any application errors, you need to repackage this application.

To repackage a Windows Installer package to capture custom action functionality:

1. Use the Repackaging Wizard to repackage this application. The Repackaging Wizard monitors system changes as an application is installed, and then that data is converted into a Repackager project.
2. Build the Repackager project to generate a revised Windows Installer package. This new Windows Installer package does not contain any custom actions, but (as a result of being repackaged) it will include the functionality performed by the original custom action.