2 replies to this topic

[Evgeny Ushkalov]

Customer have problem with my installation package.
She send this MSI log file to support:

Quote

MSI © (44:B4): Doing action: ExecuteAction Action start 6:48:21: ExecuteAction. MSI © (44:B4): Grabbed execution mutex. MSI © (44:B4): Incrementing counter to disable shutdown. Counter after increment: 0 MSI © (44:B4): Switching to server: TARGETDIR="D:\" PATH_RUNDLL32="C:\WINNT\System32\RunDll32.exe" COMPANYNAME="Valued_Customer" INSTALLDIR="C:\Program Files\Common Files\Aelita Shared\Reporting Console\" USERNAME="User" HELP="C:\WINNT\HELP\" AELITA_SHA RED="C:\Program Files\Common Files\Aelita Shared\" WWWROOT="D:\" SECONDSEQUENCE="1" *** Log Line Missing *** MSI © (44:B4): Back from server. Return value: 1603 MSI © (44:B4): Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1 Action ended 6:48:21: ExecuteAction. Return value 3. MSI © (44:B4): Doing action: Fatal_Error Action start 6:48:21: Fatal_Error. Action 6:48:21: Fatal_Error. Dialog created Action ended 6:48:22: Fatal_Error. Return value 2. Action ended 6:48:22: INSTALL. Return value 3.

I dont known how to analyze this problem...
What MSI write "*** Log Line Missing ***"?

[Stefan Krueger]

Funny... never saw this before. It could be that a custom action was writing it to the log. However at least with a maximum verbose log (L*v) you should see the srating of that custom action before it writes the line to the log.
Or maybe your custom put the line in manually?

[Evgeny Ushkalov]

Its no custom action. I develop all custom actions and no have code to write this string.
And I see that no standard actions was executed at server side between start and end.
I thought, that the customer make it, but it is deprived sense and, likely, it would be laziness to do it...