|
|
#1 (permalink) |
|
Guest
Posts: n/a
|
We have an installer which fails on one particular customer computer, which
appears to occur during running a custom action found in one of Microsoft vc 90 run-time library merge modules (we install the following vc 90 merge modules: microsoft_vc90_crt_x86.msm, policy_9_0_Microsoft_VC90_CRT_x86.msm, microsoft_vc90_mfc_x86.msm, & policy_9_0_Microsoft_VC90_MFC_x86.msm). Here is a chunk of the verbose Log leading to the first Return Value 3. Does anyone have any suggestions on how to track this down further from here? -----------start of log excerpt -------------- .... MSI (s) (2C:88) [13:02:29:500]: Doing action: InstallInitialize MSI (s) (2C:88) [13:02:29:500]: Note: 1: 2205 2: 3: ActionText Action 13:02:29: InstallInitialize. Action start 13:02:29: InstallInitialize. MSI (s) (2C:88) [13:02:29:500]: Machine policy value 'AlwaysInstallElevated' is 0 MSI (s) (2C:88) [13:02:29:500]: User policy value 'AlwaysInstallElevated' is 0 MSI (s) (2C:88) [13:02:29:500]: BeginTransaction: Locking Server MSI (s) (2C:88) [13:02:29:500]: Machine policy value 'LimitSystemRestoreCheckpointing' is 0 MSI (s) (2C:88) [13:02:29:500]: Note: 1: 1715 2: CCU 2.4.2 MSI (s) (2C:88) [13:02:29:500]: Note: 1: 2205 2: 3: Error MSI (s) (2C:88) [13:02:29:500]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1715 MSI (s) (2C:88) [13:02:29:500]: Calling SRSetRestorePoint API. dwRestorePtType: 0, dwEventType: 102, llSequenceNumber: 0, szDescription: "Installed CCU 2.4.2". MSI (s) (2C:88) [13:02:33:593]: The call to SRSetRestorePoint API succeeded. Returned status: 0, llSequenceNumber: 904. MSI (s) (2C:88) [13:02:33:593]: Server not locked: locking for product {E67C9725-A794-4BD2-B0EA-986AC036158B} Action ended 13:02:33: InstallInitialize. Return value 1. MSI (s) (2C:88) [13:02:33:640]: Doing action: SxsInstallCA MSI (s) (2C:88) [13:02:33:640]: Note: 1: 2205 2: 3: ActionText Action 13:02:33: SxsInstallCA. Action start 13:02:33: SxsInstallCA. MSI (s) (2C:88) [13:02:33:640]: Creating MSIHANDLE (14) of type 790542 for thread 3720 MSI (s) (2C:40) [13:02:33:640]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI1C.tmp, Entrypoint: CustomAction_SxsMsmInstall MSI (s) (2C:40) [13:02:33:671]: Closing MSIHANDLE (14) of type 790542 for thread 3720 Action ended 13:02:33: SxsInstallCA. Return value 3. -----------end of log excerpt -------------- |
|
|
|
#2 (permalink) |
|
Guest
Posts: n/a
|
It turns out that this particular .MSI file on the end users computer was in
fact corrupted right at the end of the file (it was too short by 6k ...). It must have been damaged during a download. "EdG" wrote: > We have an installer which fails on one particular customer computer, which > appears to occur during running a custom action found in one of Microsoft vc > 90 run-time library merge modules (we install the following vc 90 merge > modules: > microsoft_vc90_crt_x86.msm, policy_9_0_Microsoft_VC90_CRT_x86.msm, > microsoft_vc90_mfc_x86.msm, & policy_9_0_Microsoft_VC90_MFC_x86.msm). > > Here is a chunk of the verbose Log leading to the first Return Value 3. > Does anyone have any suggestions on how to track this down further from here? > .... |
|