Flexera Community

Jul 21, 2011

Good day all,I have a problem, but I am not sure exactly when it started to manifest.For years our installer made environment variables by creating the keys and then calling SendMessageTimeout(...), and it worked fine.However, I discovered today that...

Sep 09, 2013

Hi Josh, Thanks for the information!I wrote a small executable that creates all the folders mentioned, and is run as the first CA in my installation. Now it works! 

Sep 05, 2013

I think my issue is different to yours.Probably, but from the (lack of) log file information (both exit at the 'Initializing Engine' stage), as well as the fact that ours also work in IS2012 spring but not in IS2013, it may well be related somehow.

Sep 05, 2013

We are also seeing this, but on all versions of Windows (7, XP)InstallShield 08:51:11: Setting script cmdline...InstallShield 08:51:11: ProductCode is {...}InstallShield 08:51:11: Initializing EngineCustomAction CheckProperties returned actual error ...

Jul 21, 2011

Solved it now by using SendMessageTimeoutA. I guess IS was calling the Unicode version, and I suspect my string parameter was not correct.The other option (need to verify) is to declare sParam as WSTRING.

Flexera Community

User Statistics

User Activity

SendMessageTimeout not working

Re: Custom Actions fail with Error 3 on Wnidows Core OS

Re: Custom Actions fail with Error 3 on Wnidows Core OS

Re: Custom Actions fail with Error 3 on Wnidows Core OS

Solution!