cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
dekwas
Level 3

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?
Labels (1)
0 Kudos
1 Reply
dekwas
Level 3

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?
0 Kudos