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
- :
- Custom Action calling managed code return 1626
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
Nov 30, 2011
12:03 PM
Custom Action calling managed code return 1626
We have an InstallScript MSI project with a custom action that calls managed code from a selected dll. If calling the custom action using MsiDoAction within the OnResumeUIBefore event we get return code 1626 (believe this is ERROR_FUNCTION_NOT_ CALLED: Function could not be executed). This occurs on an upgrade.
If we call this same custom action still using MsiDoAction but druing a new install and from OnFirstUIBefore event we get a successful return value (ERROR_SUCCESS).
What is different about these two calls?
If we call this same custom action still using MsiDoAction but druing a new install and from OnFirstUIBefore event we get a successful return value (ERROR_SUCCESS).
What is different about these two calls?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 30, 2011
02:11 PM
It appears that others have come across similar problem: http://stackoverflow.com/questions/5101144/windows-installer-msidoaction-returns-error-function-not-called
The custom action fails during single install in OnBegin and OnResumeUIBefore, but succeeds at OnEnd.
Is this an ordering issue? Is it necessary to initialize something prior to the custom action call to the dll? Is there a restriction that prevents external calls to dll for this session?
The custom action fails during single install in OnBegin and OnResumeUIBefore, but succeeds at OnEnd.
Is this an ordering issue? Is it necessary to initialize something prior to the custom action call to the dll? Is there a restriction that prevents external calls to dll for this session?