iswix-llc
commented
7 years ago Has there been any research done on this? I haven't seen any DTF ca's failing to extract and fire up. Are you saying that if you build it on a win7 machine it works but it fails on a win 10? Do you have a CI/CD system where you build it on a clean CM controlled server?
Please provide answers to the following questions to help us narrow down, reproduce, and fix the problem. Fill out one section and delete the others.
Bugs
If this issue is a bug:
Which version of .NET are you building with?
If the problem occurs when installing your packages built with WiX, what is the version of Windows the package is running on?
Describe the problem and the steps to reproduce it.
I can successfully build a WiX .msi, but when try to install this .msi, the installer fails (on multiple computers). The failure seems to be due to a couple CustomActions. When I leave these CustomActions out, the installer proceeds without any problem.
Here is the relevant part of the log:
MSI (s) (AC:DC) [17:01:13:078]: Doing action: CheckForForeignLanguageAction Action 17:01:13: CheckForForeignLanguageAction. Action start 17:01:13: CheckForForeignLanguageAction. MSI (s) (AC:DC) [17:01:13:080]: Creating MSIHANDLE (392) of type 790542 for thread 9436 MSI (s) (AC:D8) [17:01:13:080]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSICAD0.tmp, Entrypoint: CheckForForeignLanguages MSI (s) (AC:8C) [17:01:13:080]: Generating random cookie. MSI (s) (AC:8C) [17:01:13:084]: Created Custom Action Server with PID 11756 (0x2DEC). MSI (s) (AC:30) [17:01:13:096]: Running as a service. MSI (s) (AC:30) [17:01:13:098]: Hello, I'm your 64bit Impersonated custom action server. MSI (s) (AC!58) [17:01:13:111]: Creating MSIHANDLE (393) of type 790531 for thread 9560 SFXCA: Extracting custom action to temporary directory: C:\WINDOWS\Installer\MSICAD0.tmp-\ MSI (s) (AC!58) [17:01:13:112]: Closing MSIHANDLE (393) of type 790531 for thread 9560 MSI (s) (AC!58) [17:01:13:114]: Creating MSIHANDLE (394) of type 790531 for thread 9560 SFXCA: Failed to extract to temporary directory. Cabinet error code 1. MSI (s) (AC!58) [17:01:13:114]: Closing MSIHANDLE (394) of type 790531 for thread 9560 CustomAction CheckForForeignLanguageAction returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) MSI (s) (AC:D8) [17:01:13:117]: Closing MSIHANDLE (392) of type 790542 for thread 9436 Action ended 17:01:13: CheckForForeignLanguageAction. Return value 3. Action ended 17:01:13: INSTALL. Return value 3.Any ideas why this might be happening on my machine? Any suggestions as to what I can try? My team member (who develops on a Windows 7 machine) can build the MSI and it works fine (this project is not a new one).