Hello everybody I still have the same problem. I now have 7 cases and the common point between all these customers is the processor: AMD Athlon XP (1500 + to 3000 +) and Sempron. Do you have any idea? Because at the moment the only solution we can offer them is to stay in the old version (built with IS2012) or change the server! Thanks. ... View more

Hi MickaelU, I'm not using InstallScript, and I have already tested with the SP. At the present moment, I haven't logs. If I can allocate time until next our product's version programmed for the end of november, i could open an incident with your support staff, but how ? I'm a beginner on this forum. To wait, you can read more details on http://community.flexerasoftware.com/showthread.php?206737-Custom-Actions-fail-with-Error-3-on-Wnidows-Core-OS Thanks, Claudine ... View more

Hi LanceRas, I have always the same problem : the install of my product builded with IS2013 failed, and not when it is builded with IS2012. But I have had this problem only on 3 servers ; on more than 1000, I haven't any problem. I post it in the thread "Custom Actions fail with Error 3 on Wnidows Core OS". I know I probably haven't posted it in the good thread, but it seems to be the same problem than yours. Thanks for your help. Claudine ... View more

Hi MichaelU : Thanks for your response. Yes, the log I quote is not a verbose log, but since, I have made a verbose log and I haven't more informations ! 1) I already have verified the values in the ISLockPermissions and CreateFolder tables, and all the values are OK. 2) I have modified my msi by suppressing all that are in relation with ISLockPermisson, and the install is not even OK : it stoppes after InstalleFiles, on the ISXmlInstall action, always without message, with the return code 1603 3) If I install the previous version of my product built with InstallShield 2012, the install is OK. But, if I build the same project (of this previous version) without any modification, with InstallShield 2013, the install is not OK. If I verify the two msi, with the InstallShield MSI Diff tool, there are not difference between the two, on the ISLockPermissions and CreateFolder tables. It seems to be a bug from InstallShield 2013, isn't it ? I'm waiting for others customer's log who have the same error. For many customers, the install is OK. If you have others ideas... ... View more

Same as: Custom Actions fail with Error 3 on Wnidows Core OS where I have added a post today because the solution is not OK for my msi. ... View more

Hi Josh, I have the same error without message on an Windows XP : [...] Action 12:03:37 : InstallValidate. Validation de l'installation Début de l'action 12:03:37 : InstallValidate. Fin de l'action 12:03:43 : InstallValidate. Valeur renvoyée : 1. Action 12:03:43 : ISLockPermissionsCost. Début de l'action 12:03:43 : ISLockPermissionsCost. Fin de l'action 12:03:44 : ISLockPermissionsCost. Valeur renvoyée : 3. Fin de l'action 12:03:44 : INSTALL. Valeur renvoyée : 3. Property(S): ... [...] === Fin de l'écriture dans le journal : 01/10/2013 12:03:54 === MSI (c) (D8:9C) [12:03:54:247]: Produit : XXX -- L'installation a échoué. MSI (c) (D8:9C) [12:03:54:247]: Windows Installer a installé le produit. Nom du produit : XXX. Version du produit : 4.50. Langue du produit : 1036. Réussite de l’installation ou état d’erreur : 1603. [...] My msi worked fine when built with IS2012, but not since it's build with IS2013. I have made a test with IS2013 SP1, but I have the same error. And I verify all folders you quote, but they are already all presents. Would you have an other solution ? Thanks. ... View more