Jump to content


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.
Photo

Custom action execution fails after patch install


7 replies to this topic

prudhvi

prudhvi
  • Members
  • 13 posts

Posted 12 July 2006 - 16:26

Hi,


I am facing problem in upgrading an existing version of the application during full installation.


Probem in detail:

I have created an installation package for an application (say with version 1.2)

I have version 1.1 of the application existing on my system. Now, I want to upgrade it from 1.1 to 1.2.

But, the installation is getting interrupted and failed when upgrading the existing version.(From 1.1 to 1.2)

The following is the sequence executed during the upgradition.

step 1. A series of custom actions will be executed.
step 2. The patch will be executed to upgrade the application.
step 3. Again, some custom actions will be executed.


steps 1 and 2 are performed successfully.
While performing step 3, the installation is getting interrupted and finally fails.

Thanks in advance

Glytzhkof

Glytzhkof
  • Moderators
  • 1,447 posts

Posted 12 July 2006 - 16:28

There is no way to know anything about what is happening here without a verbose log file I am afraid.
Regards
-Stein Åsmul

prudhvi

prudhvi
  • Members
  • 13 posts

Posted 12 July 2006 - 16:36

I am sorry. Here is the log information.


MSI © (9C:40) [17:05:48:465]: Doing action: SEMigration
Action 17:05:48: SEMigration.
Action start 17:05:48: SEMigration.
MSI © (9C:24) [17:05:48:481]: Invoking remote custom action. DLL: C:\DOCUME~1\VARAPR~1\LOCALS~1\Temp\MSI3794.tmp, Entrypoint: f12
MSI © (9C!70) [17:05:49:793]: PROPERTY CHANGE: Adding Is_SEExists property. Its value is '1'.
Action ended 17:06:40: SEMigration. Return value 1.



SEMigration is a custom action which launches the patch "update.exe".


Action ended 17:06:55: CostFinalize. Return value 1.
MSI (s) (A0:24) [17:06:55:965]: Doing action: StoreOldProductVersion
Action 17:06:55: StoreOldProductVersion. Preparing old installation for upgrade
Action start 17:06:55: StoreOldProductVersion.
MSI (s) (A0:18) [17:06:55:981]: Invoking remote custom action. DLL: C:\WINNT\Installer\MSI37AA.tmp, Entrypoint: f10
Action ended 17:06:55: StoreOldProductVersion. Return value 3.
MSI (s) (A0:24) [17:06:55:981]: Doing action: ISCleanUpFatalExit
Action 17:06:55: ISCleanUpFatalExit.
Action start 17:06:55: ISCleanUpFatalExit.
MSI (s) (A0:18) [17:06:55:996]: Invoking remote custom action. DLL: C:\WINNT\Installer\MSI37AB.tmp, Entrypoint: CleanUp
1: Shutting down the PRC server...
1: RPC server shut down.
Action ended 17:06:56: ISCleanUpFatalExit. Return value 1.
Action ended 17:06:56: INSTALL. Return value 3.



While executing custom action "StoreOldProductVersion" the setup is getting interrupted.

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 13 July 2006 - 12:56

Are you trying to launch a patch from a custom action? That doesn't work. Only one msi setup can run in execute sequence at a time.

prudhvi

prudhvi
  • Members
  • 13 posts

Posted 14 July 2006 - 12:27

I am launching the patch from custom action but in UI Sequence. SEMigration is a custom action which launches the patch from UI sequence. StoreOldProductVersion is a custom action in Execute sequence.

I have one more doubt redarding the execution of patch.

In the log file of patch i have observed the below lines.

MSI © (B0:A4) [12:48:59:216]: Attempting to delete file C:\DOCUME~1\VARAPR~1\LOCALS~1\Temp\65ef063.msp
MSI © (B0:A4) [12:48:59:216]: Unable to delete the file. LastError = 32
MSI © (B0:A4) [12:48:59:231]: Grabbed execution mutex.
MSI © (B0:A4) [12:48:59:231]: Cleaning up uninstalled install packages, if any exist
MSI © (B0:A4) [12:48:59:231]: MainEngineThread is returning 0
=== Verbose logging stopped: 14.07.2006 12:48:59 ===


What does "Unable to delete the file. LastError = 32" means.

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 17 July 2006 - 19:55

32 means that the file is in use by another process.

prudhvi

prudhvi
  • Members
  • 13 posts

Posted 18 July 2006 - 13:22

Hi,

Thanks stefan

Is there any way to solve the Unable to delete the file. LastError = 32 error


Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 19 July 2006 - 08:31

I guess the patch is not finished yet when you try to delete the file.