I'm having trouble adding patches and making log files on applications. I'm using Wise Windows Installer Editor in script mode and I'm trying to do the: Call Custom DLL From Destination action. I'm trying to call several function from SystemFolder\Msi.dll, but none of them seem to enact. I'm calling the MsiApplyPatch and the Installer.EnableLog functions from Msi.dll. The Platform SDK help documents claim that these functions are in the Msi.dll but every time I try to run the installer, it gives me the message: "Error in custom action. The function xxxxxx could not be located in the library C:\WINDOWS\system32\Msi.dll" IT'S VERY FRUSTRATING! the text say the functions are supposed to be there! They only require W.I. 1.0 and I have ver. 3.1.

If anyone knows of an easier way to add patches or make log files in a specific location, I'd really like to know:) However, being the perfectionist that I am, I'd really, really like to know how to add a custom DLL function from Msi.dll. I'm beating myself up over it [>:].

As always, thanks for any help.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


many of those actions are only available during specific contexts.

one thing you would need to check is that when calling a dll Ca that it has access to the session object that vbs script does.

it is here where you will be able to access most of those methods you require.
Answered 04/18/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
Thanks for responding jmcfadyen,

So, do you know what kind of context MsiApplyPatch or Installer.EnableLog would be available to? And, if need be, how exactally in Windows Installer Editor would I grant my .msi access to the session object?
Answered 04/19/2007 by: nautic20
Senior Yellow Belt

Please log in to comment