Don't call msiexec, that is not a clever way to do this from InstallAware. Instead, call the (Un)Install MSI Setup plug-in so you can capture the exact native progress of the installation and also interact with any error messages directly from the UI of your own setup wizard, while installing this external MSI setup!!!
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
Thanks but the same error appears, but instead of chinese char '?' appears.
Any other ideas?
One error in log is the following
MSI (s) (C0:58) [16:21:39:968]: Creating MSIHANDLE (13013) of type 790536 for thread 600
MSI (s) (C0:38) [16:21:40:000]: Invoking remote custom action. DLL: C:\\WINDOWS\\Installer\\MSI29F.tmp, Entrypoint: _DoVerifyUser@4
MSI (s) (C0:00) [16:21:40:046]: Generating random cookie.
MSI (s) (C0:00) [16:21:40:125]: Created Custom Action Server with PID 1944 (0x798).
MSI (s) (C0:58) [16:21:40:296]: Running as a service.
MSI (s) (C0:70) [16:21:40:328]: Hello, I'm your 32bit Elevated custom action server.
MSI (s) (C0!D4) [16:21:40:546]: Creating MSIHANDLE (13014) of type 790531 for thread 3540
Benutzerkonto ???????????s?????\\?????????r existiert nicht.
MSI (s) (C0!D4) [16:21:43:125]: Note: 1: 2205 2: 3: Error
MSI (s) (C0!D4) [16:21:43:140]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (C0!D4) [16:21:43:171]: Produkt: PostgreSQL 8.3 -- Benutzerkonto ???????????s?????\\?????????r existiert nicht.
Hi MichaelNesmith
thanks for your answer, but what do you mean with full path.
The only call what I did is C:\\tmp\\postgresql.msi
Thats a full path or which path do you mean?
Incorrect, the transform is a file that is applied to the MSI at runtime per your commandline and the transform is most probably failing due to an incomplete path specification - it cannot find the correct transform file. Otherwise, there's no reason why running msiexec from InstallAware can fail.
I think if you integrate the transform into the MSI file using Orca at build time then, you will probably be eliminating this source of failure.
You can also set the current directory in InstallAware before calling msiexec as an alternative solution.
But of course the proper way of solving this is by using the (Un)Install MSI Setup command with the full path to the transform file in the property.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/