Hello everybody,
my IS8 Developer setup works well on the first installation of the product. But as soon as I relaunch the setup and go throug Maintenance Mode "Modify", I receive the "Error -1603 Fatal error during installation. Consult windows Installer Help (Msi.chm) or MSDN for more information" after the file-transfer has finished and MSI is about to clean up his saved files.
How can I find out what the error is about or how to prevent or repair it???
Thanks
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
MSI Error -1603
Started by
probsar
, Nov 27 2003 15:40
2 replies to this topic
Glytzhkof
-
- Moderators
- 1,447 posts
Posted 27 November 2003 - 19:36
First and foremost you should create a log file for your installation, the best is probably to enable the logging policy in the registry (per machine, system policy HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer). Look up the information in the SDK.
Do you have any immediate custom actions inserted after InstallFinalize where the "Ignore error" option isn't checked?
Do you have any immediate custom actions inserted after InstallFinalize where the "Ignore error" option isn't checked?
Regards
-Stein Åsmul
-Stein Åsmul
probsar
-
- Members
- 31 posts
Posted 28 November 2003 - 09:00
I allready got some information from the logfiles. The MSI Installer is going to initiate a reboot and gets back a -1 as result, wich meas he has to reboot (as I can read out of the logs). The option in IS8 in contrary says: Suspend reboot until finished.
Last Log entries MSI:
Last Log entries MSI:
| QUOTE |
Property(S): ACTION = INSTALL Property(S): ROOTDRIVE = c:\ Property(S): CostingComplete = 1 Property(S): OutOfDiskSpace = 0 Property(S): OutOfNoRbDiskSpace = 0 Property(S): PrimaryVolumeSpaceAvailable = 0 Property(S): PrimaryVolumeSpaceRequired = 0 Property(S): PrimaryVolumeSpaceRemaining = 0 Property(S): SOURCEDIR = c:\temp\_is2\ Property(S): SourcedirProduct = {790EC520-CCCC-4810-A0FE-061633204CE4} === Logging stopped: 26.11.2003 01:51:29 === MSI (s) (7C:88): Note: 1: 1707 MSI (s) (7C:88): Product: ISScript -- Installation operation completed successfully. MSI (s) (7C:88): Cleaning up uninstalled install packages, if any exist MSI (s) (7C:88): MainEngineThread is returning 0 MSI © (38:BC): Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI © (38:BC): MainEngineThread is returning 0 === Verbose logging stopped: 26.11.2003 01:51:29 === |
Last Log entries IS:
| QUOTE |
Property(S): ACTION = INSTALL Property(S): ISStartupEvent = E52670 === Protokollierung beendet: 26.11.2003 01:52:06 === MSI (s) (7C:44): Note: 1: 1729 MSI (s) (7C:44): Produkt: DoIt 2000 -- Die Konfiguration ist fehlgeschlagen. MSI (s) (7C:44): Cleaning up uninstalled install packages, if any exist MSI (s) (7C:44): MainEngineThread is returning 1603 MSI © (98:1C): Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI © (98:1C): MainEngineThread is returning 1603 === Verbose logging stopped: 26.11.2003 01:52:07 === === Verbose logging started: 26.11.2003 01:52:07 Build type: SHIP UNICODE 2.00.2600.02 Calling process: c:\Programme\Gemeinsame Dateien\InstallShield\Driver\8\Intel 32\IDriver.exe === === Protokollierung gestartet: 26.11.2003 01:52:07 === Aktion gestartet um 01:52:07: CostInitialize. Aktion beendet um 01:52:07: CostInitialize. Rückgabewert 1. Aktion gestartet um 01:52:07: FileCost. Aktion beendet um 01:52:07: FileCost. Rückgabewert 1. Aktion gestartet um 01:52:07: CostFinalize. Aktion beendet um 01:52:07: CostFinalize. Rückgabewert 1. 1: Installation aborts, ready for RPC shutting down. 1: Invoking __ResetMsiObject... === Verbose logging stopped: 26.11.2003 01:52:09 === |
I still don't know how to manage this. I have some skript actions after this, bu no own CUSTOM ACTIONS...
HE doesn't finish the "Removing backup/save files" as you can recognize in debug Mode of IS where he stops at about 80% of this task and starts one MSI-Engine after one other and NEVER RETURNS...
Thanks for help
