Summary
Warning -6558: The Custom Action [1] in the InstallExecuteSequence table is run from an installed file. To run the custom action successfully, you may need to have a condition that checks if the source file is installed locally.Symptoms
When building a project , the following warning may occur:
Warning -6558: The Custom Action [1] in the InstallExecuteSequence table is run from an installed file. To run the custom action successfully, you may need to have a condition that checks if the source file is installed locally.
[1] is a placeholder that contains the name of the custom action that does not have a condition.
Cause
This warning message occurs when a custom action depends on a file that is being installed with the setup, but the custom action does not contain a condition. If a condition is not placed in this custom action, there is a chance that the custom action will launch when the file is not yet available on the target machine. This results in the custom action failing because the file it depends on does not exist and causes a run-time error message. Therefore, this warning serves as advance notice that problems can occur if no conditions exist for this custom action.
Resolution
To successfully run a custom action that is run from an installed file, you must make sure that the file is installed locally using a conditional statement:
- If the custom action is sequenced before RemoveFiles?Run the action only if the component was installed locally. Therefore, the component should have a condition of ?ComponentName=3, where ComponentName is the name of your component.
- If the custom action is sequenced between RemoveFiles and InstallFiles?Run the action only if the component was installed locally. Do not run the action on an uninstallation. Therefore, the component should have a condition of (?ComponentName=3) AND NOT REMOVE=ALL, where ComponentName is the name of your component.
- If the custom action is sequenced after InstallFiles?Run the action only if the component will be installed locally. Therefore, the component should have a condition of $ComponentName=3, where ComponentName is the name of your component.
In the above examples, the component referenced should contain the file that the custom action needs to work correctly.
Additional Information
Additional information on the conditions mentioned above, such as the meanings of the $ and ? symbols, can be found in the msdn article Conditional Statement Syntax.
This error is briefly documented in the InstallShield Help Library topic Troubleshooting Build Errors and Warnings.
Related Articles
Build Warning -1027 Not Issued When Timestamp Not Generated 10Number of Views Build Warning -9564 6Number of Views Build Warning 3028 9Number of Views Build Warning -5032 10Number of Views Build Warning -1527 7Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago