This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Error 2753 The File '[2]' is not marked for installation
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 30, 2010
03:26 PM
Error 2753 The File '[2]' is not marked for installation
Hi
I'm trying to run a custom action and I sometimes receive the following error:
Error 2753 The File '[2]' is not marked for installation
This only happens when the EXE needed to run the custom action has been put on by another install. I still want my custom action to run. My question is what condition do I need to make this happen? Does the component or custom action get this condition?
Thanks in advance
I'm trying to run a custom action and I sometimes receive the following error:
Error 2753 The File '[2]' is not marked for installation
This only happens when the EXE needed to run the custom action has been put on by another install. I still want my custom action to run. My question is what condition do I need to make this happen? Does the component or custom action get this condition?
Thanks in advance
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 01, 2010
11:24 AM
This sounds a lot like http://community.installshield.com/showthread.php?t=191915 to me. Could you try changing the custom action type like described on that thread?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 02, 2010
10:36 AM
Thanks for the reply. Using the Custom Action wizard, we modified the existing custom action from Launching an executable "Installed with the product" to "Stored in the Directory table". We are still testing but this appears to have worked.