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 2731. Selection manager not installed.
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
‎Jul 01, 2010
02:52 PM
Error 2731. Selection manager not installed.
InstallScript MSI Project compiles without errors and warnings. When I try to run it crashes with error 2731 - Selection manager not initialized. Apparently
something is not correct in my project but InstallShield does not catch an exception.
I did not find any reference to this error in InstallShield Help.
Can anybody explain what this error mean and how to fix it?
something is not correct in my project but InstallShield does not catch an exception.
I did not find any reference to this error in InstallShield Help.
Can anybody explain what this error mean and how to fix it?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 01, 2010
05:11 PM
According to the MSI help:
The selection manager is responsible for determining component and feature states. It is initialized during the costing actions (CostInitialize action, FileCost action, and CostFinalize action). A standard action or custom action made a call to a function requiring the selection manager before the initialization of the selection manager. This action should be sequenced after the costing actions.Do you have any actions or conditions that change feature states, for example? Does performing MSI validation tell you anything more?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 05, 2010
11:06 AM
Thank you Robert!
I have moved a custom action to AfterFileCost and this error is gone.
I have moved a custom action to AfterFileCost and this error is gone.