We have some machines on which installation intermittently hangs on AI_ExtractLzma action.
When this happens, we see something along those lines in the logs:
Code: Select all
MSI (s) (AC:6C) [13:14:29:944]: Executing op: ProductInfo(ProductKey={803E5985-2427-4FD7-9493-FB9630FBA850},ProductName=Poly Lens Control Service,PackageName=PolyLensControlService.msi,Language=1033,Version=17630174,Assignment=1,ObsoleteArg=0,ProductIcon=logo.exe,,PackageCode={A5718712-540E-4D69-817D-4F362AA52ED4},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (s) (AC:6C) [13:14:29:944]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (AC:6C) [13:14:29:944]: Executing op: DialogInfo(Type=1,Argument=Poly Lens Control Service)
MSI (s) (AC:6C) [13:14:29:960]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,,CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (AC:6C) [13:14:29:960]: Executing op: SetBaseline(Baseline=0,)
MSI (s) (AC:6C) [13:14:29:960]: Executing op: SetBaseline(Baseline=1,)
MSI (s) (AC:6C) [13:14:29:960]: Executing op: ActionStart(Name=AI_DeleteRLzma,Description=Deleting files extracted from archive,)
MSI (s) (AC:6C) [13:14:29:960]: Executing op: CustomActionSchedule(Action=AI_DeleteRLzma,ActionType=1281,Source=BinaryData,Target=DeleteLZMAFiles,)
MSI (s) (AC:6C) [13:14:29:960]: Executing op: ActionStart(Name=AI_ExtractLzma,Description=Extracting files from archive,)
MSI (s) (AC:6C) [13:14:29:960]: Executing op: CustomActionSchedule(Action=AI_ExtractLzma,ActionType=1025,Source=BinaryData,Target=ExtractLZMAFiles,)
MSI (s) (AC:F0) [13:14:29:969]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB27D.tmp, Entrypoint: ExtractLZMAFiles
MSI (s) (AC:FC) [15:40:36:135]: Running as a service.
MSI (s) (AC:FC) [15:40:36:529]: Running as a service.
MSI (s) (AC:FC) [15:40:36:906]: Running as a service.
MSI (s) (AC:FC) [15:40:37:299]: Running as a service.
MSI (s) (AC:FC) [15:40:37:677]: Running as a service.
MSI (s) (AC:FC) [15:40:38:075]: Running as a service.
MSI (s) (AC:FC) [15:40:38:447]: Running as a service.This happens on corporate machines that have a lot of antivirus and security software installed so we suspect that the problem might be caused by some of this software. Unfortunately, we don't have a way to diagnose the root cause.
So I would like to know if there is anything we can do to pinpoint the issue? Currently logs are not very useful as the action itself doesn't seem to log anything. Is there any way to enable logging in this custom action so that we can find out what it's waiting for or what's blocking it?
Thanks for help.
FOLLOW US
Get the latest news in Application Packaging