Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Install is stalled before custom action starts

74 views
Skip to first unread message

Kenneth Jonsson

unread,
Dec 14, 2005, 9:26:03 AM12/14/05
to
I have an installer with a custom actions. At one single machine the
installation never finished - it got stalled. It looked like a deadlock
situation, or perhaps an error within msiexec.
When repeating the installation with verbose logging it seems that the last
thing is "InstallFinalize. Return value 3." Normally the return value is
zero. A snippet from the logfile follows below. The custom action was never
called, it should have made an log entry in a file which never occured.

This behaviour appeared by itself, and vanished after we run the
installation from a network share!

Question: Is there any clue to what return value = 3 could mean?
Question: We got out of the situation by sheer luck. Does anyoue have a
sugestion to what we should have done to release the installer? If this
happens to an customer how could we guide him out of the dead lock?


MSI (s) (60:AC) [10:23:07:718]: Executing op:
RegSelfReg(File=WHSC30.dll,FileID=WHSC30.dll.B4D51E90_EB26_4963_BBD5_76E809E8FF98)
MSI (s) (60:AC) [10:23:07:765]: Executing op:
ActionStart(Name=_365909BA_B26B_438C_A460_467949FDBA1B.commit,,)
MSI (s) (60:AC) [10:23:07:765]: Executing op:
CustomActionSchedule(Action=_365909BA_B26B_438C_A460_467949FDBA1B.commit,ActionType=1537,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction
/action=commit /LogFile= "C:\Program\Multi 6.0\MultiCdInstaller.exe"
"C:\DOCUME~1\labuser\LOKALA~1\Temp\CFG141.tmp")
MSI (s) (60:AC) [10:23:07:765]: Executing op:
ActionStart(Name=_D4AE09B7_BEC2_41B0_BF54_A60FB5887DE7,,)
MSI (s) (60:AC) [10:23:07:765]: Executing op:
CustomActionSchedule(Action=_D4AE09B7_BEC2_41B0_BF54_A60FB5887DE7,ActionType=1554,Source=C:\Program\Multi
6.0\RegAsm.exe,Target="C:\Program\Multi 6.0\\MultiCdServer.dll" /nologo
/silent,)
MSI (s) (60:AC) [10:23:07:765]: Executing op:
ActionStart(Name=_8C39915E_7138_4FE8_AEB9_3988D0E5BDD5,,)
MSI (s) (60:AC) [10:23:07:765]: Executing op:
CustomActionSchedule(Action=_8C39915E_7138_4FE8_AEB9_3988D0E5BDD5,ActionType=1554,Source=C:\Program\Multi
6.0\SetAcl.exe,Target="C:\Documents and Settings\All Users\Application
Data\MultiCdView",)
MSI (s) (60:AC) [10:23:07:765]: Executing op:
ActionStart(Name=_91FA142F_991D_4797_AB5F_097E7CA38B8C.rollback,,)
MSI (s) (60:AC) [10:23:07:765]: Executing op:
CustomActionSchedule(Action=_91FA142F_991D_4797_AB5F_097E7CA38B8C.rollback,ActionType=1281,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction
/action=rollback /LogFile= /Operation=InstallData "C:\Program\Multi
6.0\MultiCdInstaller.exe" "C:\DOCUME~1\labuser\LOKALA~1\Temp\CFG141.tmp")
MSI (s) (60:AC) [10:23:07:765]: Executing op:
ActionStart(Name=_5967067E_E7D1_44B9_86C2_13A3D77B2BEB.install,,)
MSI (s) (60:AC) [10:23:07:765]: Executing op:
CustomActionSchedule(Action=_5967067E_E7D1_44B9_86C2_13A3D77B2BEB.install,ActionType=1025,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction
/action=install /LogFile= /CFG="C:\Documents and Settings\labuser\Mina
dokument\Multi.cfg" /TARGETDIR="C:\Program\Multi 6.0\\"
/ProductVersion=6.0.17 "C:\Program\Multi 6.0\MultiCdInstaller.exe"
"C:\DOCUME~1\labuser\LOKALA~1\Temp\CFG141.tmp")
MSI (s) (60:2C) [10:23:07:765]: Invoking remote custom action. DLL:
C:\WINDOWS09:48 2005-12-09\Installer\MSI145.tmp, Entrypoint: ManagedInstall
MSI (s) (60:AC) [10:23:07:921]: User policy value 'DisableRollback' is 0
MSI (s) (60:AC) [10:23:07:921]: Machine policy value 'DisableRollback' is 0
Action ended 10:23:07: InstallFinalize. Return value 3.

Stefan Krueger [MVP]

unread,
Dec 15, 2005, 4:23:25 AM12/15/05
to
Return code 3 means fatal error.
InstallFinalize is where deferred and commit custom actions (among other
things) get executed.
It tries to run
C:\Program\Multi 6.0\RegAsm.exe
with the command line

"C:\Program\Multi 6.0\\MultiCdServer.dll" /nologo
Note that both say C:\Program, not C:\Program Files. This may or may not be
a problem.
However the double backslash in the command line argumebnt is certainly
wrong, and may explain why it works on some drives and not on ithers
(depending on file system, network driver etc. it may ignore the double
backslash or fail).

--
Stefan Krueger
Microsoft Windows Installer MVP

Please post your questions in the newsgroup or vist one of these web sites:

Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de

InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)


"Kenneth Jonsson" <Kenneth...@discussions.microsoft.com> schrieb im
Newsbeitrag news:76259074-69EF-4C71...@microsoft.com...

Kenneth Jonsson

unread,
Dec 15, 2005, 5:54:02 AM12/15/05
to
Stefan,
Thank you for the answer. I will certainly correct the error.
I am however troubled by the fact that the installer never finished. We had
to kill two msiexec.exe processes to abort the installation.
Kenneth Jonsson

Stefan Krueger [MVP]

unread,
Dec 15, 2005, 3:31:04 PM12/15/05
to
That's not good. Maybe your custom action (launched with an invalid path)
"hangs"?

--
Stefan Krueger
Microsoft Windows Installer MVP

Please post your questions in the newsgroup or vist one of these web sites:

InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)
"Kenneth Jonsson" <Kenneth...@discussions.microsoft.com> schrieb im

Newsbeitrag news:2DD3BA2E-0331-4B04...@microsoft.com...

Kenneth Jonsson

unread,
Dec 23, 2005, 6:10:02 AM12/23/05
to
My custom action started RegAsm, although perhaps with an invalid path.
The extra backslash does not make a difference when running the action from
an DOS-prompt.

RegAsm may succed or fail, but it should never make the installer hang.

The error does not occure anymore on the failing computer and we hope it
never happens again.

Thank you for the help,

0 new messages