We got verbose logs for this issue, from at least 3 different servers, and we have investigated that in depth, to not avail so far. Some info about the 1603 error code failure I have scoured the Microsoft and Flexera Knowledge Bases (and I am continuing my investigation), with no avail so far.ĭoes anyone knows if Microsoft or Flexera, or any other third party, have published an hotfix, or some further info, about this issue? I suppose upgrading the installer package to target Windows Installer 5 may solve the issue, but if possibile I would like to avoid it, and continuing to use InstallShield 2009 to author this specific package. It is awkward to ask customers to perform such a work around.as Microsoft released various version of Windows Installer 4.5, the location of the utility to uninstall that is not strictly the one given above.the user who uninstall Windows Installer 4.5 is prompted with a dialog listing all the various software products installed using that, and effectively the link between those products and Windows Installer 4.5 is lost after uninstalling that, even if we reinstall it after successfully installing our application.
So far, we found as a work around: if we manually uninstall Windows Installer 4.5 (running something like " C:\WINDOWS\$NtUninstallKB942288-v4$\spuninst\spuninst.exe"), we can then run our installer package successfully, but this has various drawbacks: Whenever Windows Installer 4.5 was installed by an installer package, our installer package is failing with 1603. Recently, we started to notice that sometime, when installing on some Windows 2003 R2 x86 based hosts, the installation fails, and the installer log report a 1603 error code (which by the way, doesn't really help much, as it means ERROR_INSTALL_FAILURE, that is a very generic " A fatal error occurred during installation.").Īs the installation is still working on some other hosts on that very same platform, after further investigation we found out it was happening on hosts where Sql Server 2008 R2 was already installed, which leaded us to find out the issue is really with Windows Installer 4.5. We have an installer package authored with InstallShield 2009, targeting Windows Installer 3.1.
0 kommentar(er)
