ERROR FUNCTON NOT CALLED 1626 The function could not be executed

Asked By 80 points N/A Posted on -
qa-featured

ERROR FUNCTON NOT CALLED 1626 The function could not be executed.

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 and I believe this is ERROR_FUNCTION_NOT_ CALLED: Function could not be executed.

This follows on an upgrade. Doing the same custom action still using MsiDoAction but during a new install and from OnFirstUIBefore event we get a successful return value ERROR_SUCCESS.

What is different between these two calls?

SHARE
Answered By 0 points N/A #193179

ERROR FUNCTON NOT CALLED 1626 The function could not be executed

qa-featured

Hello Hall,

It is possible that the upgrade that you did is the one causing the issue that you are getting, and therefore I will suggest that you try the following workarounds:

  • First of all try downgrading to the previous version that you had and see if that will resolve the issue.
  • If you still get the issue, you might want to install CCleaner on your computer and then use it to clear all dll issues on your computer.

Regards,

Nicke

Login/Register to Answer

Related Questions